...
Client ID
The client_id is a common parameter in the payload of a JWT, particularly in tokens issued as part of OAuth 2.0 or OpenID Connect flows.
https://www.keycloak.org/docs-api/latest/rest-api/index.html#ApplicationRepresentation
Curl Examples:
Getting Admin Token
| Code Block | ||||
|---|---|---|---|---|
| ||||
curl -k -sS |
...
--request POST \ |
...
--url "http://$KEYCLOAK_HOST/auth/realms/$REALM_NAME/protocol/openid-connect/token" \ |
...
--data client_id=$CLIENT_ID \ |
...
--data username=$USERNAME \ |
...
--data password=$PASSWORD \ |
...
--data grant_type=password \ |
...
--data scope=openid |
Getting Client Secret
| Code Block | ||||
|---|---|---|---|---|
| ||||
curl -k -sS |
...
-X GET "http://$KEYCLOAK_HOST/auth/admin/realms/$REALM_NAME/clients/$CLIENT_ID/client-secret" \ |
...
-H "Content-Type: application/json" \ |
...
-H "Authorization: Bearer $ACCESS_TOKEN" |
TODO and topic to follow
- Evaluate the necessity of optional fields: Determine if certain optional fields can be removed or if their use can be better documented to avoid dead data.
- Consider adopting more specific schemas for critical operations: This can improve both the documentation and the generated code quality. Leverage OpenAPI Features: Use OpenAPI's advanced features like `allOf`,
- Prepare for code adaptations: Implement patterns like Adapter/Builder/Transformer to handle translations between similar objects, facilitating easier maintenance and adaptation to specification changes.
- Regular compliance checks.
...