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
Describe the bug
When using the Okta auth method, policies attached to a group are not listed on entities.
To Reproduce
Steps to reproduce the behavior:
Run vault write auth/okta/groups/scientists policies=nuclear-reactor
Ensure the user user1 is in the scientists group within Okta
Run vault login -method=okta username=user1
Unable to see policy nuclear-reactor attached to entity with alias user1
Expected behavior
The nuclear-reactor policy should be visible in the UI against the entity with corresponding Okta alias user1.
Environment:
Vault Server Version: 1.1.2
Vault CLI Version: 1.1.2
Server Operating System/Architecture: Ubuntu 16.04 LTS
Additional context
This may be closely related to #6067 but IMO this is actually a bug - as an Admin I would like to be able to see which policies have been granted to a user within Vault and AFAICT there is no way to see this unless I have used some form of configuration as code (e.g. Terraform)
The text was updated successfully, but these errors were encountered:
Describe the bug
When using the Okta auth method, policies attached to a group are not listed on entities.
To Reproduce
Steps to reproduce the behavior:
vault write auth/okta/groups/scientists policies=nuclear-reactor
user1
is in thescientists
group within Oktavault login -method=okta username=user1
nuclear-reactor
attached to entity with aliasuser1
Expected behavior
The
nuclear-reactor
policy should be visible in the UI against the entity with corresponding Okta aliasuser1
.Environment:
Additional context
This may be closely related to #6067 but IMO this is actually a bug - as an Admin I would like to be able to see which policies have been granted to a user within Vault and AFAICT there is no way to see this unless I have used some form of configuration as code (e.g. Terraform)
The text was updated successfully, but these errors were encountered: