Deployment configuration samples

This section displays some examples of a deployment.yaml file for ADS, with the essential properties configured . You can copy these and use them as a starting point for custom adaptations.

note

It is recommended to use environment variables to substitute any sensitive information, such as passwords, so that sensitive information can be managed and protected using generic mechanisms, external to the deployment file.

Minimum deployment configuration

The sample below contains the minimum necessary configuration that ADS requires in order to run:

## Access Decision Service part of configuration. See Axiomatics documentation

#### Path to license file
license: file:<path_to_file>/axiomatics_PDP.license

#### Path to domain configuration file
domain: file:<path_to_file>/domain.yaml

Extended deployment configuration

The sample below contains some enhanced configuration properties for leveraging ADS functionality:

## Access Decision Service part of configuration. See Axiomatics documentation

#### Path to license file
license: file:<path_to_file>/axiomatics_PDP.license

#### Path to domain configuration file
domain: file:<path_to_file>/domain.yaml

### Authentication
authentication:
  type: Basic
  user:
    username: ads-user
    hashPassword: <sha-256 hash password>
    
## Dropwizard part of configuration. 
### See https://www.dropwizard.io/en/release-2.0.x/manual/configuration.html
server:
  applicationConnectors:
    - type: http
      port: 8080
  adminConnectors:
    - type: http
      port: 8081
logging:
  level: WARN
  #loggers:
  #  "com.axiomatics.audit": INFO
  appenders:
    - type: console
      target: stdout
      timeZone: system
      
identity:
  constant: <string>