This application recreates the invite functionality that previously existed in UAA by using the /invite_users API endpoint.

You'll need to know where the app is going to be hosted, so you can tell UAA about it in the next step.

For example, if you'll be deploying into Cloudfoundry on BOSH-lite your url would probably be http://invite.bosh-lite.com/

This application uses oauth to perform actions on your behalf in UAA. To add a new oauth client in UAA, run the following command:

uaac client add uaa_extras_app --name "UAA Extras" --scope "scim.invite,password.write,cloud_controller.read" --authorized_grant_types "client_credentials,authorization_code" --authorities "scim.read,uaa.admin,password.write" --redirect_uri [url-from-step-one]/oauth/login -s [your-client-secret]

Remember the client-secret, you'll need it in step four.

If you are doing this within an already existing cloudfoundry deployment, you might want to create the user by editing your cf deployment with an opsfile like https://github.com/18F/cg-deploy-cf/blob/master/bosh/opsfiles/clients.yml

Either create a locally running version of Redis, or create a service instance in Cloud Foundry if the app will be deployed there.

EX:

cf create-service redis32 standard-ha redis-accounts

The configuration is entirely read from environment variables. Edit the manifest.yml files and update your settings as neccessary. Download a copy of https://raw.githubusercontent.com/GSA/data/master/dotgov-domains/current-federal.csv and place into uaaextras/static

This app was designed to deploy in Cloud Foundry:

cf push

Common development tasks are automated via the dev script.

1. Ensure you have pyenv and tox installed in isolated environments (e.g. install them with pipx)
2. Run ./dev venv to bootstrap your virtualenvironment
3. Run tests with ./dev test

Run tests with ./dev test

This project uses pip-tools for dependency management.

Abstract requirements live in pip-tools/requirements.in and pip-tools/requirements-dev.in. Concrete requirements live in requirements.txt and requirements-dev.txt.

To add new requirements or pin versions, edit pip-tools/requirements.in and/or pip-tools/requirements-dev.in then run ./dev update-requirements

To bump versions, run ./dev upgrade-requirements

After changing dependencies, you probably want to run ./dev clean, which will recreate your virtuanenvironment and clear your tox cache.

If you run into an issue with psycopg2 and you're working on a Mac running Catalina or higher, make sure you've done the following:

• brew install postgresql@12 and add the location to your path
• brew install openssl@1.1 and add the location to your path

Note that psycopg2 currently doesn't support PostgreSQL 13.x (https://www.psycopg.org/docs/install.html#prerequisites), and PostgreSQL 13.x isn't available in AWS GovCloud yet, either.

Then export two environment variables in your current shell session:

• export LDFLAGS="-L/usr/local/opt/openssl/lib"
• export CPPFLAGS="-I/usr/local/opt/openssl/include"

To get a local server up, run the following command. Make sure you properly setup the environment variables mentioned above in the documentation.

./debug.py

Because of the redirect that occurs for setting up cloud.gov multi-factor authentication, the IDP_PROVIDER_URL must match what is coming from the UAA login screen under cloud.gov.

The /first-login route is used to redirect users with an origin of cloud.gov to the cloud.gov IdP provider. This route is used to set the user's origin to cloud.gov and the externalId to their userName. On a successful update of the user, cg-uaa-extras will redirect to the IDP_PROVIDER_URL to complete the user's authentication and TOTP token creation. This is why the URL from the screenshot above is necessary for the IDP_PROVIDER_URL.

Tests are run using tox and flake8.

pip install tox

To run the tests, simply run tox from the root of the repository. If you run into the same psycopg2 setup issue as noted above in local development, make sure you've followed the same steps and add the following line to each env setting in the tox.ini file:

setenv = LDFLAGS = "-L/usr/local/opt/openssl/lib"

This repository leverages Concourse. The configuration files all reside in the ci/ directory. All pull requests should have staging as a base branch which will automatically trigger a deployment for the staging job. Once development is stable on staging, create a new pull request promoting all the changes on staging to master to deploy the application in the production environment.