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.
Generating a self-signed certificate
- Generate your private key with any passphrase
openssl genrsa -aes256 -out server.key 1024
- Remove passphrase from key
openssl rsa -in server.key -out server.key
- Generate certificate signing request for CA
openssl req -x509 -sha256 -new -key server.key -out server.csr
- Generate self-signed certificate with 365 days expiry-time
openssl x509 -sha256 -days 365 -in server.csr -signkey server.key -out selfsigned.crt
Contributing to uaa-release
Create a feature branch from the development branch
cd uaa-release git checkout develop git submodule update git checkout -b my_branch
Make changes on your branch
Deploy your version of uaa-release to test the changes
Push to your fork (
git push origin my_branch) and submit a pull request selecting
developas the target branch
Java Runtime Environments
Java Runtime Environments are gracefully supplied by the Cloud Foundry Java Buildpack Team
- We'd like to extend a thank you to all our users, contributors and supporters!