For the complete documentation index, see llms.txt. This page is also available as Markdown.

Authentication - Staff Portal

Modules Accessed via Staff Portal

After login, users may access the following modules (based on roles):

  • Registry

  • PBMS

  • G2PBridge

  • SPAR

  • Rancher

  • Superset Dashboard

  • Keycloak Admin Console

  • MinIO

  • ODK

Authentication Flow – Staff Portal Login

Overview

The Staff Portal delegates authentication to the IAM service.

Instead of directly interacting with Keycloak or handling OAuth flows, the portal:

  • Calls an IAM endpoint

  • Receives a redirect URL

  • Redirects the user to continue authentication

This ensures that all authentication logic, token exchange, and session handling are centralized in IAM.

Step-by-Step

1. User Accesses Staff Portal

  • User opens:

2. Staff Portal Initiates Authentication

The portal calls its internal API:

This triggers:

With:

  • id → Login provider ID (e.g., Keycloak)

  • redirect_uri → Where user should return after login

3. IAM

IAM responds with:

4. Redirect to Keycloak

  • Staff Portal redirects user to:

  • User authenticates on Keycloak UI

5. Full OAuth Flow Happens Inside IAM

After login:

  • Keycloak → returns authorization code to IAM

  • IAM → exchanges code for tokens:

    • Access Token

    • ID Token

6. Redirect Back to Staff Portal

IAM redirects user back to:

With session/cookies already established.

7. User Gets Access

  • Staff Portal now detects valid session

  • Displays application cards

Last updated

Was this helpful?