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
Service clients using bearer tokens should be able to refresh those tokens without requiring a process restart. We support this today for mutual TLS so we should be able to do something similar for bearer token usage.
The easiest solution (IMO) would be to add a new services[_].credentials.bearer.path configuration field (name TBD) that specifies the path of a file containing the bearer token to read. OPA would re-read the file like it does with TLS certs/keys.
This change updates the bearer token config to allow clients to specify
a path to the token. With this refreshing tokens becomes easier as OPA
will now reload the token from file.
Fixesopen-policy-agent#2241
Signed-off-by: Ashutosh Narkar <anarkar4387@gmail.com>
This change updates the bearer token config to allow clients to specify
a path to the token. With this refreshing tokens becomes easier as OPA
will now reload the token from file.
Fixes#2241
Signed-off-by: Ashutosh Narkar <anarkar4387@gmail.com>
Service clients using bearer tokens should be able to refresh those tokens without requiring a process restart. We support this today for mutual TLS so we should be able to do something similar for bearer token usage.
The easiest solution (IMO) would be to add a new
services[_].credentials.bearer.path
configuration field (name TBD) that specifies the path of a file containing the bearer token to read. OPA would re-read the file like it does with TLS certs/keys.@patrick-east what do you think?
The text was updated successfully, but these errors were encountered: