New auth method type aws-iam not visible on the UI
- Dominant language
- Go
- Stars
- 30.1k
- Forks
- 4.6k
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 39
Description
Hello i made a fresh install of consul (with ACLs enabled) on AWS EKS with the official helm chart.
Everything works fine, i am trying now to create a new auth method.
I did :
```
consul acl auth-method create -type aws-iam \
-name iam-role-login \
-config='{
"BoundIAMPrincipalARNs": ["arn:aws:iam::123456789012:role/MyRoleName"],
"EnableIAMEntityDetails": true,
"IAMEntityTags": ["consul-namespace"],
"ServerIDHeaderValue": "consul.mydomain.com",
"MaxRetries": 3,
"IAMEndpoint": "https://iam.amazonaws.com/",
"STSEndpoint": "https://sts.us-east-1.amazonaws.com/",
"AllowedSTSHeaderValues": ["X-Extra-Header"]
}'
```
And after i did a binding rules :
```
consul acl binding-rule create -method 'iam-role-login' \
-description 'Binding Rule for consul-consul-client' \
-bind-type 'role' \
-bind-name 'consul-consul-client-acl-role' \
-selector 'entity_name=="myRoleName"'
```
After that when i try to Log In via the UI i don't see the auth method that i created i just the Log in with token method, do you know how to see the new auth method from the UI so i can use it ?
Thanks a lot !
Contributor guide
Research direction
Start by reproducing the reported setup with the `consul acl auth-method create` and `consul acl binding-rule create` commands, then inspect the Consul UI login entry point. Verify whether the created `aws-iam` method is discovered and rendered alongside token login; done means the cause of its absence is identified and the method is available in the UI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, helm, kubernetes
- Domain
- authentication, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100