Skip to content

Update Custom-Id-Tokens-in-AD-FS.md #7059

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update Custom-Id-Tokens-in-AD-FS.md #7059

wants to merge 1 commit into from
+3 −1

Conversation

mistermik
Copy link
Contributor

Without adding the client identifier in the WebAPI the customized token will never be emitted. This is a key step in the configuration which is missing. I spent a few hours to figure this out.

@mistermik
Update Custom-Id-Tokens-in-AD-FS.md
f29ebca 
Without adding the client identifier in the WebAPI the customized token will never be emitted. This is a key step in the configuration which is missing. I spent a few hours to figure this out.
@prmerger-automator
Copy link
Contributor

@mistermik : Thanks for your contribution! The author(s) have been notified to review your proposed change. @anandyadavMSFT

@prmerger-automator
Copy link
Contributor

@mistermik : Thanks for your contribution! The author(s) have been notified to review your proposed change. @anandyadavMSFT

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit f29ebca:

✅ Validation status: passed

File Status Preview URL Details
WindowsServerDocs/identity/ad-fs/development/Custom-Id-Tokens-in-AD-FS.md ✅Succeeded

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

@prmerger-automator
Copy link
Contributor

@mistermik : Thanks for your contribution! The author(s) have been notified to review your proposed change. @anandyadavMSFT

@Court72
Copy link
Contributor

Court72 commented Feb 17, 2023

@robinharwood, @Xelu86

Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Feb 17, 2023
@prmerger-automator
Copy link
Contributor

@mistermik : Thanks for your contribution! The author(s) have been notified to review your proposed change. @anandyadavMSFT

@prmerger-automator
Copy link
Contributor

@mistermik : Thanks for your contribution! The author(s) have been notified to review your proposed change. @anandyadavMSFT

1 similar comment
@prmerger-automator
Copy link
Contributor

@mistermik : Thanks for your contribution! The author(s) have been notified to review your proposed change. @anandyadavMSFT

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@robinharwood robinharwood Awaiting requested review from robinharwood

@Xelu86 Xelu86 Awaiting requested review from Xelu86

Assignees

@robinharwood robinharwood

@Xelu86 Xelu86

Labels
ad-fs/tech aq-pr-triaged tracking label for the PR review team Change sent to author do-not-merge qualifies-for-auto-merge windows-server/prod
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@mistermik @Court72 @robinharwood @Xelu86