To debug data mapping in social sign-in with Ory, you need to understand how Ory handles the OIDC registration flow. Here are the steps: 1. Redirect to the social sign-in provider. 2. Redirect back to Ory with a

code

query parameter. 3. Ory exchanges the

code

for an access token and retrieves the user information. 4. Ory maps the user information to the [Identity Schema traits](https://www.ory.sh/docs/kratos/manage-identities/identity-schema). 5. (optional) Ory redirects back to the registration page, requiring the user to provide the values for the missing traits. If Ory gets stuck in a redirect loop, it's likely that step 4 is failing. This happens when the Jsonnet configuration for the social sign-in provider is incorrect and Ory can't map the data correctly. To fix the redirect loop, adjust the Jsonnet configuration for the social sign-in provider so that the data from the provider gets mapped correctly to the Identity Schema. You can learn more about how to map and merge profile data [here](https://www.ory.sh/docs/kratos/social-signin/data-mapping). Remember, don't save secrets such as API keys, credentials, or personal data directly in Jsonnet code snippets. Jsonnet code snippets used for data mapping aren't stored in an encrypted format in Ory Network. Here is an example of a Jsonnet code snippet for data mapping:

jsonnet local claims = {     email_verified: false,   } + std.extVar('claims');      {     identity: {       traits: {         // Allowing unverified email addresses enables account         // enumeration attacks,  if the value is used for         // verification or as a password login identifier.         //         // Therefore we only return the email if it (a) exists and (b) is marked verified.         [if 'email' in claims && claims.email_verified then 'email' else null]: claims.email,       },     },   }

You can find more examples of data mapping for different social sign-in providers in the Ory documentation. Source: [Ory Documentation](https://www.ory.sh/docs/troubleshooting/troubleshooting-social-sign-in#redirect-loops-after-successful-registration)

I'm sorry, but the provided knowledge sources do not contain information on how to access a log of the providers returned claims in Ory. It's recommended to refer to the official Ory documentation or the specific provider's documentation for more details on logging and debugging.