happy-kangaroo-57071
10/26/2022, 8:06 PMurls.login
is configured in the Hydra deployment, which seems like something the Ory servers should handle
• and in any case, i don't see an obvious place in the settings to change it
am i missing something here? bug in the cloud deployment?happy-kangaroo-57071
10/26/2022, 8:07 PMhappy-kangaroo-57071
10/26/2022, 8:11 PMory get oauth2-config
, there is an entry for urls.login
happy-kangaroo-57071
10/26/2022, 8:16 PMory perform authorization-code
as suggested in the documentationhappy-kangaroo-57071
10/26/2022, 8:19 PMhappy-kangaroo-57071
10/26/2022, 8:19 PMwonderful-lamp-2357
10/27/2022, 7:15 AMhigh-optician-2097
happy-kangaroo-57071
10/27/2022, 1:48 PMhappy-kangaroo-57071
10/27/2022, 2:13 PMory create oauth2-client
• ory perform authorization-code
• Get a sign in / sign up page, completes authz flow, as expectedhigh-optician-2097
happy-kangaroo-57071
10/27/2022, 2:42 PMhappy-kangaroo-57071
10/27/2022, 2:43 PMhigh-optician-2097
happy-kangaroo-57071
10/27/2022, 3:51 PMlocal claims = std.extVar('claims');
{
identity: {
traits: {
email: claims.email,
},
},
}
• Ory successfully talks to the enterprise OIDC provider, but then reports that it did not get an "email" claim (500 "Field does not exist: email")
• I confirmed that the enterprise provider provides an "email" claim in UserInfo by running my own OIDC client with the same parameters as I gave Oryhappy-kangaroo-57071
10/27/2022, 5:30 PMhigh-optician-2097
as a general comment, debugging the Jsonnet layer is challenging. it doesn’t look like there’s a way to see its input, which means you’re kind of feeling around in the dark.That is true 😞 do you have an ID Token from the enterprise provider I could take a look into? For debugging you could also do:
{
identity: { matadata_admin: { oidc_claims: claims } }
}
which will put the data into the metadata fields