PDC JWT Token
Understanding the WHO & WHAT ..
JWT Token
We're going to implement enterprise-grade identity federation where Keycloak manages WHO people are (identity + organizational structure) and PDC manages WHAT data they can access (Communities + data governance).
This separation of WHO & WHAT is how enterprises scale data governance across thousands of users.
Examine the PDC JWT Login token
We need to confirm that PDC can authenticate users through Keycloak and receive role information via JWT tokens.
Log into Data Catalog:
Username: [email protected]
Password: Welcome123!
Verify successful return to PDC with user context.
JWT Token
JSON Web Token (JWT) is a compact, URL-safe means of representing claims to be transferred between two parties. The claims in a JWT are encoded as a JSON object that is used as the payload of a JSON Web Signature (JWS) structure or as the plaintext of a JSON Web Encryption (JWE) structure, enabling the claims to be digitally signed or integrity-protected with a Message Authentication Code (MAC) and/or encrypted.
In a terminal enter the following command:
curl -k -L -X POST 'https://pdc.pentaho.lab/keycloak/realms/pdc/protocol/openid-connect/token' \
-H 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'client_id=pdc-client' \
--data-urlencode 'grant_type=password' \
--data-urlencode '[email protected]' \
--data-urlencode 'password=Welcome123!' | jq -r '.access_token'
Copy the
access_tokenvalue in the token_response.json to: https://jwt.io to decode it.
The scope parameter directly controls what information Keycloak includes in the JWT token.
The JWT token essentially will become the bridge between Adventure Works' organizational hierarchy and PDC's data governance model, enabling seamless, automated, and secure data access control.
Last updated
Was this helpful?