Skip to content

Commit

Permalink
Update docs for post-deploy manual steps
Browse files Browse the repository at this point in the history
  • Loading branch information
rconway committed Dec 13, 2023
1 parent fa90a56 commit 40859bc
Show file tree
Hide file tree
Showing 2 changed files with 18 additions and 6 deletions.
5 changes: 4 additions & 1 deletion docs/eoepca/application-hub.md
Original file line number Diff line number Diff line change
Expand Up @@ -156,12 +156,15 @@ data:
The deployment of the Application Hub has been designed, as far as possible, to automate the configuration. However, there remain some steps that must be performed manually after the scripted deployment has completed...
* [Configure OIDC Client](#oidc-client)
* [Configure Groups and Users](#groups-and-users)
### OIDC Client
The client that is created by the script `./deploy/bin/register-client` (as per above) needs to be manually adjusted using the Web UI of the Login Service...

* In a browser, navigate to the Login Service (Gluu) - https://auth.192-168-49-2.nip.io/ - and login as the `admin` user
* Open `OpenID Connection -> Clients` and search for the client created earlier - `Application Hub`
* Open `OpenID Connect -> Clients` and search for the client created earlier - `Application Hub`
* Fix the setting `Authentication method for the Token Endpoint` for the `ApplicationHub` - `client_secret_post` -> `client_secret_basic`
* Save the update

Expand Down
19 changes: 14 additions & 5 deletions docs/quickstart/scripted-deployment.md
Original file line number Diff line number Diff line change
Expand Up @@ -109,6 +109,16 @@ kubectl get pods -A

The deployment is ready once all pods are either `Running` or `Completed`. This can be further confirmed by accessing the login-service web interface at `https://auth.<domain>/` and logging in as user `admin` using the credentials configured via `LOGIN_SERVICE_ADMIN_PASSWORD`.

## Post-deployment Manual Steps

The scripted deployment has been designed, as far as possible, to automate the configuration of the deployed components. However, there remain some steps that must be performed manually after the scripted deployment has completed.<br>
See the building block specific pages...

* **Login Service:** [Post-deployment Manual Steps](../../eoepca/login-service/#post-deployment-manual-steps)

!!! note
See also [Post-protection Manual Steps](#post-protection-manual-steps) for additional interventions to be performed later in the process.

## Default Credentials

### Login Service
Expand Down Expand Up @@ -171,13 +181,12 @@ _Ensure that the script is executed with the environment variables and command-l
./deploy/eoepca/eoepca-protection.sh apply "<eric-id>" "<bob-id>" "<public-ip>" "<domain>"
```

## Post-deploy Manual Steps
## Post-protection Manual Steps

The scripted deployment has been designed, as far as possible, to automate the configuration of the deployed components. However, there remain some steps that must be performed manually after the scripted deployment has completed...
The scripted deployment has been designed, as far as possible, to automate the configuration of the deployed components. However, there remain some steps that must be performed manually after the scripted deployment has completed.<br>
See the building block specific pages...

* Login Service: [UMA Resource Lifetime](../../eoepca/login-service/#uma-resource-lifetime)
* Application Hub: [OIDC Client](../../eoepca/application-hub/#oidc-client)
* Application Hub: [Groups and Users](../../eoepca/application-hub/#groups-and-users)
* **Application Hub:** [Post-deployment Manual Steps](../../eoepca/application-hub/#post-deployment-manual-steps)

## Create User Workspaces

Expand Down

0 comments on commit 40859bc

Please sign in to comment.