You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See docs taken from bosh-micro-cli circa mid-2015.
Configuring required properties for UAA start-up
The properties below need to be generated explicitly per deployment of UAA release and are required for proper start-up and functioning of UAA. These are standard artifacts which can be generated using openssl. Please refer the topic below on how to generate a self signed cert.
SAML Service Provider Configuration
login.saml.serviceProviderCertificate:
description: "UAA SAML Service provider certificate. This is used for signing outgoing SAML Authentication Requests"
login.saml.serviceProviderKey:
description: "Private key for the service provider certificate."
JWT Signing Keys(verification key needn't be set as we derive it from the private key)
uaa.jwt.policy.keys:
description: "Map of key IDs and signing keys, each defined with a property `signingKey`"
example:
key-1:
signingKey
uaa.jwt.policy.active_key_id:
description: "The ID of the JWT signing key to be used when signing tokens."
example: "key-1"
Configuring UAA to run on https with SSL
By default UAA is configured to use SSL with a self-signed certificate and will be started on port 8443.
Using your own certificate
Add the following properties to your manifest:
uaa.sslCertificate: Specifies your SSL certificate
uaa.sslPrivateKey: Specifies your private key. The key must be a passphrase-less key.