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
n proxy mode we can specify a header that will be filled with the validated email address from the JWT token. The value will only contain the email address, eg: [email protected]:
A better feature request would be to have the injected headers customizable using JMESPath like Grafana did in its jwt auth. This will make injected response headers (when running gcp-iap-auth in server mode for nginx auth_request) and request headers (when running in reverse proxy mode) use anything from the jwt token as value.
n proxy mode we can specify a header that will be filled with the validated email address from the JWT token. The value will only contain the email address, eg: [email protected]:
Can we have another header just to provide username? eg:
name
from[email protected]
using --name-header=X-WEBAUTH-NAMEThe text was updated successfully, but these errors were encountered: