Actions: How do I *set* an event.user.nickname?

[edent]

I have this action:

exports.onExecutePostLogin = async (event, api) => {
  // Put the user screen_name as the nickname
  // for Twitter connections
  if (event.connection.name === 'twitter' && event.user.screen_name) {
    event.user.nickname = event.user.screen_name;
  } 
};

This doesn’t set the user’s nickname.

I can do this: api.user.setUserMetadata("nickname", "event.user.screen_name");
But that only adds it to the metadata.

I need the user’s object to contain the data.

Is there any way to set the nickname using an action?

[edent]

Incidentally, this is a workaround for a bug that’s now 5 years old…

Twitter nickname is not the same as screen_name

My Twitter handle is @edent. If I login with Auth0, I see: 'nickname' => 'Terence Eden', 'name' => 'Terence Eden', I would expect my “nickname” to be the same as my screen_name. If I log in with GitHub (Where I am also @edent) I get: 'nickname' => 'edent', 'name' => 'Terence Eden', I’m using the PHP library, if that makes a difference? use Auth0\SDK\Auth0; $auth0 = new Auth0([ 'domain' => AUTH0_DOMAIN, 'client_id' => AUTH0_CLIENT_ID, 'client_secret' => AUTH0_CLIENT_…

[gparascandolo]

hey @edent

I can’t speak much regarding the bug you mention from 5 years ago, but if you need to update something other than user_metadata or app_metadata on user profiles in Auth0 Actions, you will have to use the Management API.

See this FAQ for more info on how to set it up

How can I use the Management API in Actions?

Question: How can I use the Management API in Actions? Answer: There are plans to expand functionality in Actions even more in the future. Currently, the only built-in method for using the Management API from within Actions is for updating user metadata. You can use the api object to update user metadata in a pre-user-registration or post-login action: api.user.setUserMetadata(name, value) api.user.setAppMetadata(name, value) If you need to use the Management API for something other than upda…

Also, as noted in the FAQ above, the Management API updates are rate limited, so be sure to also add a check that the user’s event.user.nickname doesn’t already match event.user.screen_name before making the Management API request.

Hope this helps

EDIT:
Something I forgot to mention, if you need to update nickname on social users, please note the following from this doc Configure Identity Provider Connection for User Profile Updates

By default, user profile attributes provided by identity providers other than Auth0 (such as Google, Facebook, Twitter) are not directly editable because they are updated from the identity provider each time the user logs in.

To be able to edit the name, nickname, given_name, family_name, or picture root attributes on the normalized user profile, you must configure your connection sync with Auth0 so that user attributes will be updated from the identity provider only on user profile creation.

[edent]

Wait, I have to set up and configure another application, to call an API, to fix a bug, all because Auth0 have decided to deprecate something that worked?

Can I just pay someone at Okta to fix this bug?

Seriously, gang, I’ve got £5 here for any employee of Auth0 who wants to make this right.

[gparascandolo]

Hey @edent

I took a closer look at the older post you made, are you looking to just temporarily override the nickname field for the ID Token on the frontend or the Access Token for the /userinfo endpoint?

I haven’t tested this, but try setting the nickname via the built-in api setCustomClaim functions.

exports.onExecutePostLogin = async (event, api) => {
  // Put the user screen_name as the nickname
  // for Twitter connections
  if (event.connection.name === 'twitter' && event.user.screen_name) {
    api.idToken.setCustomClaim('nickname', event.user.screen_name);
    api.accessToken.setCustomClaim('nickname', event.user.screen_name);
  } 
};

Generally you would create a custom claim in the tokens with a namespace you own, but give this a try and see if this will resolve your issue.

[edent]

That seems to work! Thank you.

Nevertheless, I think it’s time for me to move away from Auth0 if I can. It’s quite clear that they’ve no interest in fixing bugs and would rather spend their time changing their logo.