If I pass in the following scope : oidcConformant: true, allowedConnections: 'Username-Password-Authentication'], auth: { redirectUrl: myConfig.callbackURL + 'pages/dashboard', responseType: 'token id_token', audience: `https://${myConfig.domain}/userinfo`, …

With OIDC conforment clients, the way to add scope in rules have changed slightly; we now allow the user to define scopes in the API & OpenID, and custom claims are now name spaced. Therefore, you’ll need to pass this information to your token via another rule. There are 3 scenarios are as follows. …

Scope not working for newer Clients/Lock (OIDC Conformant)?

Get Help

Topic		Replies	Views
Getting Roles & Groups Get Help oidc , roles , authorization-extens , aspnet-core , groups	5	6664	March 2, 2018
Group scope in OIDC? Get Help	9	22030	August 29, 2019
Auth0-lock v11.2 sso is not working Get Help sso , sso-integrations , sso-integration , auth-lock	2	4707	August 27, 2019
Auth0 getUserInfo does not return all user data Get Help userinfo , oidc , oidc-conformant	6	10564	March 2, 2018
Additional scopes when Authenticating via OIDC Get Help scopes	7	5342	December 20, 2018

Scope not working for newer Clients/Lock (OIDC Conformant)?

Related topics