Closed yuri-potatoq closed 2 months ago
Since you can already do comparisons after providing the insecure issuer option, I don't think we need another hook.
Hey, thank you to reply. That sounds suitable enough. But my point is about to centralize OIDC configuration stuff into the provider library, can be helpful to when the users has serveral microservices which share the same validation behavior and then package such logic to be reusable.
It's was just to clarify my intentions, if still not the library goal, i'm ok.
I really want to thank you for the helpful project. It is very useful for OIDC auth validations.
Unfortunately i have the same problem solved by InsecureIssuerURLContext , with Keycloak OIDC discovery hostnames.
When i used the custom context to figure out it, i was wondering if a new feature to customize the issuers validation on Provider creation should fit in the project design. The goal is to accept trusted internal hosts at the issuer validation.
I make this PR to make a simple solution. I've designed in that way to avoid break changes. Could u tell me if that could fit as a offical PR?