-
Notifications
You must be signed in to change notification settings - Fork 3
auth config.yml
Janek Laudan edited this page Oct 18, 2018
·
2 revisions
# This is a dropwizard configuration for the server. Check out their manual
server:
applicationConnectors:
- type: https
port: 3000
keyStorePath: /path/to/your/keystore.jks
keyStorePassword: 123456
adminConnectors:
- type: https
port: 3001
keyStorePath: /path/to/your/keystore.jkskeystore.jks
keyStorePassword: 123456
# this should be the uri the auth-server is available at. Will be put into tokens as 'iss' claim
hostURI: "https://localhost:3000"
# interval in hours by which token signing keys are regenerated
keyRenewalInterval: 24
# currently the only way to create users for the application is to put them into the configuration file
# NOTE: passwords must be at least 10 characters long.
# id may be ommited
users:
- username: [email protected]
password: longpassword
id: test-user-id
# all clients that my fetch acces tokens and/or id tokens can be configured here
clients:
- name: test-client
id: local-client-id
secret: test-client-secret
redirectUris:
- http://localhost:8080/authentication
scopes:
- openid
- user-client
- name: token-client
id: token-client-id
secret: token-client-secret
redirectUris:
- http://localhost:2999/callback
scopes:
- openid
- service-client
# all resources which accept access tokens from clients can be configured here
protectedResources:
- name: file-server
secret: file-server-secret
id: file-server-id
scopes:
- relying-party
- name: frame-animation-service
secret: frame-animation-service-secret
id: frame-animation-service-id
scopes:
- service-client