To remove the need for the

hd

claim when logging in via Google, you need to modify the data mapping in your Ory Identity configuration. In the Jsonnet code snippet that maps the Google claims to the Ory Identity schema, you can remove or comment out the line that maps the

hd

claim. Here is the original Jsonnet code snippet:

jsonnet local claims = {    email_verified: false,   } + std.extVar('claims');      {    identity: {    traits: {    [if 'email' in claims && claims.email_verified then 'email' else null]: claims.email,    first_name: claims.given_name,    last_name: claims.family_name,    [if 'hd' in claims && claims.email_verified then 'hd' else null]: claims.hd,    },    },   }

You can modify it to look like this:

jsonnet local claims = {    email_verified: false,   } + std.extVar('claims');      {    identity: {    traits: {    [if 'email' in claims && claims.email_verified then 'email' else null]: claims.email,    first_name: claims.given_name,    last_name: claims.family_name,    // [if 'hd' in claims && claims.email_verified then 'hd' else null]: claims.hd,    },    },   }

After modifying the Jsonnet code snippet, you need to encode it with Base64 or host it under a URL accessible to Ory Network. Then, you need to update the Ory Identities configuration using the Ory CLI:

bash ory update identity-config {project-id} --file identity-config.yaml

Please note that

{project-id}

should be replaced with your actual project ID and

identity-config.yaml

should be replaced with the path to your updated identity configuration file. For more information, please refer to the [Ory documentation](https://www.ory.sh/docs/kratos/social-signin/google#data-mapping).

Based on the information provided in the extracts, it's not clear why your registration is failing. The error message "Registration failed" is quite generic and doesn't provide specific details about the issue. However, there are a few common reasons why registration might fail in Ory: 1. Validation Errors: If the Identity Schema JSON includes a field which is required but wasn't provided by the upstream identity provider (for example Google), the end-user's browser is returned to the registration screen with the form validation errors. [source](https://www.ory.sh/docs/kratos/self-service/flows/user-registration#registration-with-google-facebook-github--openid-connect--oauth-20-1) 2. Redirect Loops: If the Jsonnet configuration for the social sign-in provider is incorrect and Ory can't map the data correctly, the user sees no input fields and the registration page gets stuck in a redirect loop. [source](https://www.ory.sh/docs/troubleshooting/troubleshooting-social-sign-in#redirect-loops-after-successful-registration) 3. API Errors: If the API endpoint

/self-service/registration

is called with incorrect parameters or in the wrong context, it could return various error codes like 400 (Bad Request), 410 (Gone), or 422 (Unprocessable Entity). [source](https://www.ory.sh/docs/kratos/reference/api) To troubleshoot the issue, you could check the browser's network tab to see the exact API call that's failing and the error message it's returning. You could also check the server logs for any error messages. If you're still having trouble, you might find it helpful to refer to the [Ory Kratos documentation](https://www.ory.sh/docs/kratos/) or the [Ory Community](https://community.ory.sh/) for more help.