Need accessToken in Action to make additional Social calls to set app_metadata?

[tyf]

Hey there @2vYEjLFtkUPpbDR sorry for the delayed response!

@2vYEjLFtkUPpbDR

This makes me ask, what is the point of a Custom Social Connection if you can’t save additional custom user/app data from that Custom Social Connection. Any valuable third party login and API will have protected routes that need an accessToken to retrieve scope/claims data. There is currently no way to save this data?

You’re correct in that the access token won’t be available until the login flow (and action(s)) is complete, but you will have access to the token in the user’s identities array. I don’t see why you couldn’t use the access token available on the user to get those details and add them to metadata outside the scope of an action.

Identity Provider Access Tokens

In terms of then getting that on login once set, you’d probably want to add metadata as a custom claim:

How do I get User Metadata in the Login

Hey @solid, The reason you didn’t receive the user’s metadata is because metadata is not a standard claim so it will not be included in ID Tokens by default. To include it, you must write a Rule to copy user_metadata properties to the ID token. This is explained in detail here: Add custom claims to a token. I hope this helps. More information:

Let us know if this helps!