Hi!
We are trying to move forward the keycloak social provider for twitter to v2. The main limitation right now is that as it is a social login provider it needs access to the account information and the email is vital. Currently v1 is used and verifyCredentials is executed to retrieve the email. There are some previous threads about this topic (for example this one or one that requests adding it to the /users/me endpoint).
I have also read a comment that OpenID Connect was going to solve the limitation in a future release.
Any news about this?
Thanks in advance!