Seq Okta Integration (email_verified) #1620
-
|
After correcting some network issues, after attempting to do an Okta authentication I got the following message. [22:23:24 WRN] Identity successfully authenticated, but the OpenID Connect provider did not supply the Is this setting within okta? or is there a way to set this within seq? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 13 replies
-
|
Hi @specialagentsoftware, thanks for getting in touch. Seq currently requires the Is it possible to confirm with Okta support that there's no way to have that claim included? Having Okta supply the claim would be the fastest way to get unblocked. If that turns out to be impossible, we'd be open to adding an "ignore Hope this helps, |
Beta Was this translation helpful? Give feedback.
-
|
@nblumhardt Thanks for the info. I tried the above config change and then started a new browser session and I encountered the same error. I will send an email to the address you shared so that you can send me a patch build link there. Thank you. |
Beta Was this translation helpful? Give feedback.
-
|
@nblumhardt Email sent. |
Beta Was this translation helpful? Give feedback.
-
|
Received! Thank you 👍 |
Beta Was this translation helpful? Give feedback.
-
|
@nblumhardt I had seen this issue as well. #1154.. it was related to not being able to get email in the initial token for IdentityServer4... would enabling that allow extra info to be collected from Okta? I am totally fine with getting a build that allows us to disable the email_verified claim. Just thought I would mention it. We are currently running 2022.1.7929. It appears this was already done and looks like it would have been included already in a build. I will leave this here just in case I have misunderstood. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the note; yes, this is already enabled in 2022.1.7929 👍 |
Beta Was this translation helpful? Give feedback.
Hi @specialagentsoftware, thanks for getting in touch. Seq currently requires the
email_verifiedclaim when matching accounts by email address; it's a standard field in theemailOIDC scope, but it appears to be unsupported by Okta.Is it possible to confirm with Okta support that there's no way to have that claim included? Having Okta supply the claim would be the fastest way to get unblocked.
If that turns out to be impossible, we'd be open to adding an "ignore
email_verifiedclaim" option in our next maintenance release, but the timeline for that is not set, currently (our last maintenance release was just a few days ago).Hope this helps,
Nick