tppalani/cg-uaa-release

DEPRECIATED / NEVER USED IN PRODUCTION. You probably want cg-cf-release

UAA release

See docs in bosh-micro-cli.

Export Warning

This fork of the UAA release includes > 128-bit encryption. The software may be subject to import or export regulations outside the United States.

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

1. Generate your private key with any passphrase

openssl genrsa -aes256 -out server.key 1024

2. Remove passphrase from key

openssl rsa -in server.key -out server.key

3. Generate certificate signing request for CA

openssl req -x509 -sha256 -new -key server.key -out server.csr

4. Generate self-signed certificate with 365 days expiry-time

openssl x509 -sha256 -days 365 -in server.csr -signkey server.key -out selfsigned.crt

Notes

• The property uaa.port can't be set to 8989 because this port is used by BOSH to monitor the server.

Contributing to uaa-release

General workflow

1. Fork the repository and make a local clone

2. Create a feature branch from the development branch

   cd uaa-release
   git checkout develop
   git submodule update
   git checkout -b my_branch

3. Make changes on your branch

4. Deploy your version of uaa-release to test the changes

5. Push to your fork (git push origin my_branch) and submit a pull request selecting develop as the target branch