Skip to content

RevocationEndpoint not configured #101

Answered by natelaff
natelaff asked this question in Open Source
Discussion options

You must be logged in to vote

Ok, so I started digging and looked more, convinced the issue was somewhere when I was calling into GetConfigurationAsync() which was what is loading that discovery document. But even so, all looked correct.

What I found though is that OpenIdConnectCOnfiguration has a RevocationEndpoint (which was properly set). So I just get it from there now, instead of trying to get it from AdditionalData as I was doing before, and everything is back to working!

So, somewhere something changed where that thing is no longer in additionlData but strongly typed? Not sure what package that got updated in or what controls any of that . Presumably the update to Microsoft.IdentityModel.Protocols.OpenIdConnect…

Replies: 5 comments 3 replies

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
1 reply
@RolandGuijt
Comment options

Comment options

You must be logged in to vote
1 reply
@RolandGuijt
Comment options

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
1 reply
@AndersAbel
Comment options

Answer selected by maartenba
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
4 participants
Converted from issue

This discussion was converted from issue #100 on March 07, 2025 14:19.