openiddict-core: Can't get request caching to work in dockerized container
Confirm you’ve already contributed to this project or that you sponsor it
- I confirm I’m a sponsor or a contributor
Version
3.x
Question
I have an OpenIddict identity server that works fine when deployed as an azure app service, but if i try to deploy it as a dockerized container and validate using it (through B2C) i get an error that ‘The specified ‘request_id’ is invalid’. The url that it’s using is something like https://|my site|/connect/authorize?request_id=KloxbYfo4KZ7n-I7UBB7jfCK0KEsMHhqiqcUJkiZY1s
I don’t see any errors, and the only logs i see from the server are:
2022-02-12T16:01:12.947404065Z {"EventId":0,"LogLevel":"Information","Category":"OpenIddict.Server.OpenIddictServerDispatcher","Message":"The request address matched a server endpoint: Configuration.","State":{"Message":"The request address matched a server endpoint: Configuration.","Endpoint":"Configuration","{OriginalFormat}":"The request address matched a server endpoint: {Endpoint}."}}
2022-02-12T16:01:12.948095274Z {"EventId":0,"LogLevel":"Information","Category":"OpenIddict.Server.OpenIddictServerDispatcher","Message":"The configuration request was successfully extracted: {}.","State":{"Message":"The configuration request was successfully extracted: {}.","Request":"{}","{OriginalFormat}":"The configuration request was successfully extracted: {Request}."}}
2022-02-12T16:01:12.949852198Z {"EventId":0,"LogLevel":"Information","Category":"OpenIddict.Server.OpenIddictServerDispatcher","Message":"The configuration request was successfully validated.","State":{"Message":"The configuration request was successfully validated.","{OriginalFormat}":"The configuration request was successfully validated."}}
2022-02-12T16:01:12.966884823Z {"EventId":0,"LogLevel":"Information","Category":"OpenIddict.Server.OpenIddictServerDispatcher","Message":"The response was successfully returned as a JSON document: ....
2022-02-12T16:01:13.247721845Z {"EventId":0,"LogLevel":"Information","Category":"OpenIddict.Server.OpenIddictServerDispatcher","Message":"The request address matched a server endpoint: Cryptography.","State":{"Message":"The request address matched a server endpoint: Cryptography.","Endpoint":"Cryptography","{OriginalFormat}":"The request address matched a server endpoint: {Endpoint}."}}
2022-02-12T16:01:13.263200650Z {"EventId":0,"LogLevel":"Information","Category":"OpenIddict.Server.OpenIddictServerDispatcher","Message":"The cryptography request was successfully extracted: {}.","State":{"Message":"The cryptography request was successfully extracted: {}.","Request":"{}","{OriginalFormat}":"The cryptography request was successfully extracted: {Request}."}}
2022-02-12T16:01:13.271657862Z {"EventId":0,"LogLevel":"Information","Category":"OpenIddict.Server.OpenIddictServerDispatcher","Message":"The cryptography request was successfully validated.","State":{"Message":"The cryptography request was successfully validated.","{OriginalFormat}":"The cryptography request was successfully validated."}}
2022-02-12T16:01:13.355147869Z {"EventId":0,"LogLevel":"Information","Category":"OpenIddict.Server.OpenIddictServerDispatcher","Message":"The response was successfully returned as a JSON document: ....
2022-02-12T16:01:13.549556945Z {"EventId":0,"LogLevel":"Information","Category":"OpenIddict.Server.OpenIddictServerDispatcher","Message":"The request address matched a server endpoint: Authorization.","State":{"Message":"The request address matched a server endpoint: Authorization.","Endpoint":"Authorization","{OriginalFormat}":"The request address matched a server endpoint: {Endpoint}."}}
which don’t seem like they show any issues at all. Any ideas on where i should be looking to fix this issue? The dockerfile is just:
FROM mcr.microsoft.com/dotnet/aspnet:6.0 AS base
EXPOSE 80
EXPOSE 8081
COPY bin/Release/net6/ App/
WORKDIR /App
ENTRYPOINT ["dotnet", "IdentityManager.dll"]
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 17 (8 by maintainers)
yep, that was it thank you. Instead of redis, for now i just reduced the instance count to 1 and everything worked. Thank you!
Then I’m out of ideas 😄 Did you try to lower the log level to Debug/Trace to see if there’s anything interesting?
I’ll try to reproduce that on my end when I have a moment.