
VovN.86756 (Customer) asked a question.
Hi everyone,
I’m working with an OIDC integration where I need access to the email_verified claim inside the ID token. I’ve confirmed that:
- email_verified is available from the /userinfo endpoint when the email scope is requested.
- email_verified is available in the implicit flow.
- It does not appear in ID tokens when using the Authorization Code + PKCE flow.
- Creating a custom claim doesn’t solve the problem, since custom claims can only pull values from the Okta User profile (and email_verified is not a core profile attribute, but an internal Okta verification state).
We can't use the implicit flow or calling the /userinfo endpoint due to some security constrain.
For our use case, it would be ideal if Okta could include the standard email_verified claim in ID tokens, alongside email, when the email scope is requested.
Is it possible for Okta Support to enable this behavior for our org, or is there an alternative configuration we should use to have email_verified reliably emitted in ID tokens?

Hi @VovN.86756 (Customer) , Thank you for reaching out to the Okta Community!
As far as I've been able to find information on the topic, this does not seem to be supported.
This question is more appropriate for our dedicated Okta Developer Forum.
My advice would be to reach out via devforum.okta.com to take advantage of their expertise.
While we'll do our best to answer all of your questions here, this medium is more inclined towards Okta core products and features (non-custom/developer work).
If you have an account with us, you can also open a case to discuss the matter with a dedicated resource to go over your implementation in detail.
Regards.
--
Help others in the community by liking or hitting Select as Best if this response helped you.
Collect them all. Learn a new skill and earn a new Okta Learning badge.
Just released: More Okta Community badges just added
Join the discussion for our Ask Me Anything on September 29, 2025: Device Assurance. Ask our expert questions.
Hi @Mihai Negoita - Okta (Okta, Inc.) . Thank you for your prompt response.
I'll try out the options that you provided.
Unfortunately this is one of those claims that isnt available in the thin tokens and is only accessible in your scenario by calling by to userinfo endpoint