You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
My work is using AWS cognito, and we have a large number of client ids / audiences / app ids. Imagine a business with large business customers, that ended up having their own client ids.
For OTEL, we do not care what the audience is, we just want requests to be authenticated with the user pool.
Describe the solution you'd like
go-oidc has a SkipClientIdCheck property, that we would like to use through the collector.
Describe alternatives you've considered
The alternative with the collector at the moment seems like listening on a different port for each audience. The application would need to know which audience it was in, and which port to send to. This is not very feasible.
Or another alternative is not using the oidc extension and handling oidc authentication with like a reverse proxy or something before the collector.
The text was updated successfully, but these errors were encountered:
zeck-ops
changed the title
[extension/oidcauthextension] oidc extension skip client id check
[extension/oidcauthextension] Fixes oidc extension skip client id check
Nov 27, 2024
Component(s)
extension/oidcauthextension
Is your feature request related to a problem? Please describe.
My work is using AWS cognito, and we have a large number of client ids / audiences / app ids. Imagine a business with large business customers, that ended up having their own client ids.
For OTEL, we do not care what the audience is, we just want requests to be authenticated with the user pool.
Describe the solution you'd like
go-oidc has a SkipClientIdCheck property, that we would like to use through the collector.
Describe alternatives you've considered
The alternative with the collector at the moment seems like listening on a different port for each audience. The application would need to know which audience it was in, and which port to send to. This is not very feasible.
Or another alternative is not using the oidc extension and handling oidc authentication with like a reverse proxy or something before the collector.
The text was updated successfully, but these errors were encountered: