Conversation
|
@eslerm is attempting to deploy a commit to the Chainguard Team on Vercel. A member of the Team first needs to authorize it. |
✅ Deploy Preview for ornate-narwhal-088216 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
eslerm
force-pushed
the
eslerm/custom-idp-email-claim
branch
from
October 1, 2026 00:06
b4f51e8 to
6e65485
Compare
|
Should the "Send a usable email claim" text be added to the Ping and/or Keycloak pages as well, if we're already doing Okta and Entra? |
eslerm
marked this pull request as ready for review
October 1, 2026 23:14
matthewhelmke
approved these changes
Oct 2, 2026
matthewhelmke
left a comment
matthewhelmke
left a comment
Collaborator
There was a problem hiding this comment.
LGTM, thank you for writing this up!
matthewhelmke
force-pushed
the
eslerm/custom-idp-email-claim
branch
from
October 2, 2026 11:57
6e65485 to
0b0627f
Compare
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
…roubleshooting The setup requirements listed the email scope but not that the issued token must carry a populated standard email claim. Providers that source email from a non-standard directory attribute (e.g. LDAP mail) pass sign-in but hand Chainguard an empty email, so the identity is created without one and email-dependent features such as the support portal stop working. Chainguard reads only the standard claim, so the fix is a customer-side attribute mapping. - Add a "Required token claims" section and a requirements bullet to the custom IdP overview. - Add a per-provider "Send a usable email claim" note to the Okta, Microsoft Entra ID, Ping Identity, and Keycloak guides. - Add a troubleshooting entry for the support-portal redirect failure.
matthewhelmke
force-pushed
the
eslerm/custom-idp-email-claim
branch
from
October 2, 2026 19:10
0b0627f to
6cd43f6
Compare
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
emailclaim — not just the requestedemailscope — and how to map a directory attribute to it.Why
The setup requirements listed the
emailscope but not the requirement that the issued token actually carry a populatedemailclaim. Providers that source email from a non-standard directory attribute (e.g. LDAPmail) pass sign-in but hand Chainguard an empty email, so the identity is created without one and email-dependent features such as the support portal stop working. Chainguard reads only the standard claim, so the fix is a customer-side attribute mapping — now documented, with a per-provider note and a troubleshooting entry tying the symptom to the cause.