adaptive content and OIDC (descope) authentication provider #1058
Unanswered
sulrich-nexthop
asked this question in
1. How to
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
hello -
i'm trying to setup adaptive content to work in conjunction with descope (using the OIDC integration).
visitor.claims.*
for various bits of customization and audience control.github-visitor-token-XXXXXX
cookie that shows that it's been originated by descope the custom claims don't seem be accessible (i've also configured these claims to match in the adaptive content schema).is there something special that needs to be done in order to have the custom claims accessible in the session for the user?
Beta Was this translation helpful? Give feedback.
All reactions