social sign-in using REST API

[nelyaklyusa]

Hello everyone
i am trying to implement social sign in using REST API and i am really confused about the flow
so i have google button and clicking on which i make request POST /self-service/login?flow=${flowId}. in body i provide csrf_token, provider, method: 'oidc',

after i give consent in google, i get redirected to registration page /signup?flow=${flowId} where i need to fill missing data and provide password
so i make GET request /self-service/registration?flow=${flowId} where i get traits

after i fill all data and provide password, how do i finish social registration?
do i make POST /self-service/login?registration=${flowId}. in body i provide csrf_token, provider, method: 'oidc', traits
or do i finish like a normal registration with method: 'password'

Would really appreciate all the help i can get,
Thank you!

[vinckr]

hello @nelyaklyusa

You correctly start by initiating a login flow and then submitting with the OIDC method.
After Google authentication and consent, you're redirected to the registration page because Ory detected that this is a new user. This is expected behavior.

When you get redirected to the registration page with a new flow ID, you correctly fetch the registration flow data:
GET /self-service/registration?flow=${flowId}
For the final step to complete the social registration, you should submit to the registration endpoint with the OIDC method, not the password method:

POST /self-service/registration?flow=${flowId}
{
  "csrf_token": "your-csrf-token",
  "provider": "google",
  "method": "oidc",
  "traits": {
    // Include any required traits that weren't provided by Google
  }
}

The key point is that you should continue using the oidc method for the final registration step, not switch to the password method. This is because you're completing a social sign-in flow.

If your identity schema requires additional traits that weren't provided by Google, you'll need to include those in the final request. This is why you're seeing the registration form - to collect any missing required information, see also Social Sign-in Troubleshooting.

If you encounter a redirect loop after successful registration, it might be because some identity traits couldn't be mapped from the social provider data and require manual input, but the UI isn't showing the input fields properly.