Returned Twitter nickname is not same as user's actual Twitter handle

[nileshtrivedi]

Description

I found a thread in forum about the same issue with no resolution: https://community.auth0.com/t/twitter-nickname-is-not-the-same-as-screen-name/17297

Unlike every other social login provider, Twitter strategy returns request.env['omniauth.auth']['info']['nickname'] value which is NOT the user's Twitter handle.

The workaround of adding this rule in Auth0 dashboard does work:

function (user, context, callback) {
  // Put the user's screen_name as the nickname
  // for Twitter connections
  if (context.connection === 'twitter' && user.screen_name) {
    user.nickname = user.screen_name;
  }
  callback(null, user, context);
}

Prerequisites

• [x] I have read the Auth0 contribution guidelines
• [x] I have read the Auth0 Code of Conduct
• [x] Did you check the documentation?
• [x] Did you check Auth0 Community?
• [x] Are you reporting this to the correct repository? This strategy relies on OmniAuth and the OmniAuth OAuth2 strategy.
• [x] Are there any related or duplicate Issues or PRs for this issue?

Environment

• OmniAuth-Auth0 version: 2.2.0
• Ruby version: 2.6.3
• Rails veresion: 5.2.3

[albertoperdomo]

Hello @nileshtrivedi,

thanks for taking the time to report issues. The issue you are experiencing is not a specific issue with omniauth-auth0, but an issue with the Twitter connection itself. We are aware of this issue and have an item in our backlog to address this.

In the meantime, the workaround of using that rule should still be valid, AFAIK. Closing this issue as it can not be addressed in this library.