-
Notifications
You must be signed in to change notification settings - Fork 4
/
config.yaml.example
33 lines (31 loc) · 1.48 KB
/
config.yaml.example
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
onelogin:
clientID: clientID of API credential with "Authentication only"
clientSecret: client Secret of API credential
accountName: onelogin account name
accounts:
- name: myapp-prod
appID: onelogin app id (e.g. 123456)
accountID: AWS account ID
profileName: AWS IAM profile to store credentials in (in ~/.aws/credentials)
- name: myapp-dev
appIDsByRole: # optional, if you use different OneLogin apps for different roles
iam-role-1: onelogin app id (e.g. 123456)
iam-role-2: onelogin app id (e.g. 123456)
accountID: AWS account ID
profileName: AWS IAM profile to store credentials in (in ~/.aws/credentials)
roles:
- iam-role-1 # role that is configured in onelogin and IAM to use with the onelogin identity provider
- iam-role-2
defaultRegion: us-east-1
# Credentials can be specified in the YAML config file, but it is not recommended
# because it will store the credentials in plain text on your disk.
# It is better to use the environment variables EMAIL, PASSWORD and OTP.
credentials:
# it can be overridden by the EMAIL environment variable
email: email of user to use for authentication
# it makes no sense to use this option in the YAML config file,
# but it can be overridden by the PASSWORD environment variable
password: password of user to use for authentication
# it makes no sense to use this option in the YAML config file,
# but it can be overridden by the OTP environment variable
otp: otpToken of user to use for authentication