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
==> Vault server configuration:
Cgo: disabled
Listener 1: tcp (addr: "0.0.0.0:8200", cluster address: "0.0.0.0:8201", tls: "enabled")
Log Level: info
Mlock: supported: true, enabled: true
Storage: file
Version: Vault v0.9.5
Version Sha: 36edb4d42380d89a897e7f633046423240b710d9
==> Vault server started! Log data will stream in below:
Expected Behavior:
After enabling and configuring Okta auth backend with max_ttl different than zero, without changing the default_lease_ttl and the max_lease_ttl, any successfully authenticated user should get a token with a duration <= max_ttl.
Actual Behavior:
Successfully authenticated users get a token with duration = 768h, although Okta backend was configured with max_ttl=1h.
Steps to Reproduce:
Enable Okta auth backend
Configure Okta auth backend with max_ttl=1h
Authenticate to Vault through Okta
Look for the token_duration line in Vault's output
Important Factoids:
If Okta auth backend is configured with both max_ttl=1handttl=1h then token's duration is limited to 1h.
The text was updated successfully, but these errors were encountered:
After b3c9358 now Okta respects max_ttl=1h, but I get the following weird warning after a successful login (using Vault 0.9.6):
WARNING! The following warnings were returned from Vault:
* Effective TTL of '1h0m0s' exceeded the effective max_ttl of '1h0m0s'; TTL
value is capped accordingly
Configuration is still the same like explained in the ticket, i.e.:
Environment:
Vault Config File:
Startup Log Output:
Expected Behavior:
After enabling and configuring Okta auth backend with
max_ttl
different than zero, without changing the default_lease_ttl and the max_lease_ttl, any successfully authenticated user should get a token with a duration <=max_ttl
.Actual Behavior:
Successfully authenticated users get a token with duration = 768h, although Okta backend was configured with
max_ttl=1h
.Steps to Reproduce:
max_ttl=1h
token_duration
line in Vault's outputImportant Factoids:
If Okta auth backend is configured with both
max_ttl=1h
andttl=1h
then token's duration is limited to 1h.The text was updated successfully, but these errors were encountered: