Hi everyone. Thanks for reporting this, we’ve found the issue that is causing this behavioral change and a fix is on the way.
I’d suggest the following workaround for now:
function (user, context, callback) {
// set default values for name and nickname
user.name = user.name || user.email || "";
if (!user.nickname) {
user.nickname = user.email ? user.email.split('@')[0] : user.name;
}
callback(null, user, context);
}
The above rule won’t permanently write the values in the user profile, but it modifies the claims that applications get in the ID Token or in the user profile from the /userinfo
endpoint.