add a signer claim to the aws alb auth provider
Signed-off-by: Fredrik Adelöw <freben@gmail.com>
This commit is contained in:
@@ -11,14 +11,18 @@ and get the user seamlessly authenticated.
|
||||
## Configuration
|
||||
|
||||
The provider configuration can be added to your `app-config.yaml` under the root
|
||||
`auth` configuration:
|
||||
`auth` configuration, similar to the following example:
|
||||
|
||||
```yaml title="app-config.yaml"
|
||||
auth:
|
||||
providers:
|
||||
awsalb:
|
||||
issuer: 'https://example.okta.com/oauth2/default' # optional
|
||||
region: 'us-west-2' # required, use your actual region here
|
||||
# this is the URL of the IdP you configured
|
||||
issuer: 'https://example.okta.com/oauth2/default'
|
||||
# this is the ARN of your ALB instance
|
||||
signer: 'arn:aws:elasticloadbalancing:us-east-2:123456789012:loadbalancer/app/my-load-balancer/1234567890123456'
|
||||
# this is the region where your ALB instance resides
|
||||
region: 'us-west-2'
|
||||
signIn:
|
||||
resolvers:
|
||||
# typically you would pick one of these
|
||||
@@ -26,6 +30,8 @@ auth:
|
||||
- resolver: emailLocalPartMatchingUserEntityName
|
||||
```
|
||||
|
||||
Ensure that you have set the signer correctly. It is also recommended that you restrict your target groups' security policy to only accept connections from that ALB.
|
||||
|
||||
### Resolvers
|
||||
|
||||
This provider includes several resolvers out of the box that you can use:
|
||||
|
||||
Reference in New Issue
Block a user