Reference

Demo Credentials

Platform Access

Service Username Password Notes

OpenShift Console

admin

(from RHDP provisioning email)

Open

ArgoCD

—

—

Log in via "Log in via OpenShift" button using the OpenShift admin credentials above

Gitea (Git repository)

gitea

openshift

Open

To retrieve the ArgoCD admin password directly:

oc get secret openshift-gitops-cluster -n openshift-gitops -o jsonpath='{.data.admin\.password}' | base64 -d && echo

Application Users

Role Username Password Used For

TechPulse Admin

admin@techpulse.demo

admin

Course Manager UI

DataForge Admin

admin@dataforge.demo

admin

Course Manager UI

NeuralPath Admin

admin@neuralpath.demo

admin

Course Manager UI

TechPulse Student

student01@techpulse.demo

student

Cert Portal (transcript)

DataForge Student

student03@dataforge.demo

student

Cert Portal (transcript)

NeuralPath Student

student05@neuralpath.demo

student

Cert Portal (transcript)

Infrastructure

Service Username Password Used For

CouchDB (per-org)

admin

adminpw

State database (accessible via oc exec)

PostgreSQL (per-org)

keycloak

keycloak

Keycloak database

Environment URLs

User-Facing Applications

Component URL

Cert Portal (public verification)

Open

TechPulse Course Manager

Open

DataForge Course Manager

Open

NeuralPath Course Manager

Open

Platform & Infrastructure

Component URL

OpenShift Console

Open

ArgoCD Dashboard

Open

Grafana Dashboards

Open

Gitea (Git Repository)

Open

Keycloak Identity Providers

Realm URL

Central (identity brokering)

Open

TechPulse

Open

DataForge

Open

NeuralPath

Open

Keycloak admin console credentials: admin / admin for all realms.

API Endpoints

API Base URL

TechPulse cert-admin-api

https://

DataForge cert-admin-api

https://

NeuralPath cert-admin-api

https://

verify-api (central)

https://

OpenShift CLI Access

To run oc commands from the Terminal tab, first log in to the cluster:

oc login https://:6443 -u admin

If you are running this demo on RHDP, the password is provided in your lab provisioning email. For BYO clusters, use the password you set during installation.

Verify the CertChain namespaces are healthy:

for ns in certchain certchain-techpulse certchain-dataforge certchain-neuralpath; do
  echo "=== $ns ==="
  oc get pods -n $ns --no-headers | grep -v Completed | awk '{print $1, $2, $3}'
done

API Reference

cert-admin-api (per-org, requires org-admin role)

Method Path Description

POST

/api/v1/certificates

Issue a new certificate

GET

/api/v1/certificates?page=0&size=20

List org certificates (paginated)

GET

/api/v1/certificates/{certId}

Get single certificate

PUT

/api/v1/certificates/{certId}

Update mutable fields

PUT

/api/v1/certificates/{certId}/revoke

Revoke (irreversible)

GET

/api/v1/courses

List course catalog

GET

/api/v1/dashboard/stats

Certificate stats

verify-api (central, public + JWT)

Method Path Auth Description

GET

/api/v1/verify/{certId}

Public

Verify certificate status

GET

/api/v1/verify/{certId}/qr

Public

Generate QR code (PNG)

GET

/api/v1/verify/batch?ids=X,Y

Public

Batch verify

GET

/api/v1/transcript

JWT

Student’s certificates

GET

/api/v1/transcript/{certId}

JWT

Single certificate

Namespace Layout

Namespace Contents

certchain

Fabric CA, orderer0, cert-portal, verify-api, central Keycloak, Postgres, Grafana, Gitea

certchain-techpulse

Peer, orderer, CouchDB, certcontract (CcaaS), Postgres, org Keycloak, cert-admin-api, course-manager-ui

certchain-dataforge

Same as techpulse

certchain-neuralpath

Same as techpulse

showroom

Antora lab guide