https://www.ory.com/ logo
Join Slack
Powered by
<@U04UQ68083H> Error ```{ "id": "3883e4b3-270...
# ory-copilot
c
@chilly-king-10285 Error
Copy code
{
    "id": "3883e4b3-2701-42ba-81e0-09c0366f61d6",
    "error": {
        "code": 500,
        "status": "Internal Server Error",
        "message": "jsonnetsecure: ERROR: RUNTIME ERROR: Field does not exist: given_name\n\<tbase64://bG9jYWwgY2xhaW1zID0gewogIGVtYWlsX3ZlcmlmaWVkOiBmYWxzZSwKfSArIHN>0ZC5leHRWYXIoJ2NsYWltcycpOwoKc3RkLnRyYWNlKCJjbGFpbXM6ICVzIiAlIFtjbGFpbXNdLCBjbGFpbXMpCgp7CiAgaWRlbnRpdHk6IHsKICAgIG1ldGFkYXRhX3B1YmxpYzogewogICAgICAgW2lmICdwaWN0dXJlJyBpbiBjbGFpbXMgdGhlbiAncGljdHVyZScgZWxzZSBudWxsXTogY2xhaW1zLnBpY3R1cmUKICAgIH0sCiAgICB0cmFpdHM6IHsKICAgICAgW2lmICdlbWFpbCcgaW4gY2xhaW1zICYmIGNsYWltcy5lbWFpbF92ZXJpZmllZCB0aGVuICdlbWFpbCcgZWxzZSBudWxsXTogY2xhaW1zLmVtYWlsLAogICAgICBmaXJzdF9uYW1lOiBjbGFpbXMuZ2l2ZW5fbmFtZSwKICAgICAgW2lmICdmYW1pbHlfbmFtZScgaW4gY2xhaW1zIHRoZW4gJ2xhc3RfbmFtZScgZWxzZSBudWxsXTogY2xhaW1zLmZhbWlseV9uYW1lLAogICAgICBbaWYgJ2hkJyBpbiBjbGFpbXMgJiYgY2xhaW1zLmVtYWlsX3ZlcmlmaWVkIHRoZW4gJ2hkJyBlbHNlIG51bGxdOiBjbGFpbXMuaGQKICAgIH0sCiAgfSwKfQo=:14:19-36\tobject \u003canonymous\u003e\n\tField \"first_name\"\t\n\tField \"traits\"\t\n\tField \"identity\"\t\n\tDuring manifestation\t\n"
    },
    "created_at": "2024-07-26T17:33:08.936788Z",
    "updated_at": "2024-07-26T17:33:08.936788Z"
}
c
A message from kapa.ai
The error message indicates that there's a problem with your Jsonnet configuration for the social sign-in provider. Specifically, it's trying to access a field named 
given_name
that doesn't exist in the data returned by the provider. To fix this, you need to adjust your Jsonnet configuration to correctly map the data from the provider to the Identity Schema. Make sure that the fields you're trying to access in your Jsonnet script (
given_name
in this case) are actually included in the data returned by your social sign-in provider. Here's a brief overview of how Ory handles the OIDC registration flow: 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. 5. (optional) Ory redirects back to the registration page, requiring the user to provide the values for the missing traits. If step 4 fails (as it did in your case), Ory becomes stuck in a redirect loop. Adjusting your Jsonnet configuration should fix this issue. For more information on how to map and merge profile data, you can refer to the [Ory documentation](https://www.ory.sh/docs/kratos/social-signin/data-mapping). If the issue persists, it might be helpful to check the [troubleshooting guide](https://www.ory.sh/docs/troubleshooting/troubleshooting-social-sign-in#redirect-loops-after-successful-registration) for redirect loops after successful registration.
7 Views
Open in Slack
PreviousNext
Powered by