User access to RSP:UK

The following describes the process of providing access to a user when deploying the RSP:

If deploying the RSP for the first time, we have to:

• Create a Github Organization Example Github Org: https://github.com/organizations/LSP-UK/settings/profile

• Create an OAuth Application for this org Example OAuth App: https://github.com/organizations/LSP-UK/settings/applications/1452049

• Create a Client secret & Push to Vault Generate Secrets & Push Secrets location: https://github.com/stvoutsin/lsp-deploy/blob/master/installer/ Generate secret Example: https://github.com/organizations/LSP-UK/settings/applications/1452049/client_secret

• Create a Team within the Github Org: Example Team: https://github.com/orgs/LSP-UK/teams/dev

• Deploy the RSP, after modifying our environment to whitelist this newly created team: https://github.com/stvoutsin/lsp-deploy/blob/master/services/gafaelfawr/values-roe.yaml#L18

Once these are already setup and the RSP deploy is configured to use them, if a new user requests access we have to:

• Add them to the Github Org & Team we created. (They need to accept membership before they are able to access the RSP)
• They accept access to Github OAuth App. (Appears when trying to access Nublado or Firefly)