RevocationEndpoint not configured #101
-
Affected componentDuende.AccessTokenManagement Version3.2.0 Describe the bugI am experiencing the RevocationEndpoint not configured error. I have found this issue in the archived repo and the soon to be deleted IS4 repro which mentions this page Following the steps it mentions I do not see a conflict in the package versions. I am using AccessTokenManagement 3.2.0 and .NET 9 dotnet list package --include-transitive | sls "Microsoft.IdentityModel|System.IdentityModel"
I have also tried forcing these packages to update to the latest 8.6.0, with the same results. Typically I don't reference any package in my client directly (even Microsoft.AspNetCore.Authentication.OpenIdConnect) because I just let it come in from the AccessTokenManagement package. Any ideas? Steps to reproduce.AddCookie(CookieAuthenticationDefaults.AuthenticationScheme, options => Expected behaviorNo error? :) Additional contextNo response |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 3 replies
-
Hi, I've tried to reproduce this issue, with the same assemblies, but have been unable to do so. Would you be able to create a minimal reproduction? |
Beta Was this translation helpful? Give feedback.
-
Ok, it appears to be in my IOpenIdConnectConfigurationService it's trying to get it from
That's pulling null suddenly. Is this supposed to come from IS? Perhaps my IdentityServer project being updated is what caused it? |
Beta Was this translation helpful? Give feedback.
-
My AdditionalData only has backchannel_logout_supported and backchannel_logout_session_supported. How many things should be in there? Where should this be coming from. I am getting this object from options. This is the whole class that accesses this... an awful lot of code to just inject the tenant name into the token endpoint :D
|
Beta Was this translation helpful? Give feedback.
-
Hmm... shoot. It's in there. There must be something new going on down stream with the multi-tenancy stuff I guess? Very strange. I will have to do some digging! Thank you for your insight @RolandGuijt, very helpful!!! |
Beta Was this translation helpful? Give feedback.
-
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 8.0.1. |
Beta Was this translation helpful? Give feedback.
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…