Client List

💡 Continue from Keycloak Client Creation.
The following is the list of Keycloak Clients that require certain configuration unique to the client.
| Tool/Instrument | Client Name | Backchannel logout session required | Backchannel logout revoke offline sessions | Full scope allowed | Exclude Issuer From Authentication Response |
|---|---|---|---|---|---|
| ArgoCD | argocd | ✅ Yes | ✅ Yes | ✅ Yes | ❌ No |
| DefectDojo | defectdojo | ✅ Yes | ❌ No | ❌ No | ❌ No |
| SonarQube | sonarqube | ✅ Yes | ❌ No | ✅ Yes | ❌ No |
| GitLab | gitlab | ✅ Yes | ❌ No | ✅ Yes | ❌ No |
| Harbor | harbor | ✅ Yes | ✅ Yes | ✅ Yes | ❌ No |
| Grafana | grafana | ✅ Yes | ❌ No | ✅ Yes | ❌ No |
| Kubernetes API | kubernetes | ✅ Yes | ❌ No | ✅ Yes | ❌ No |
| Vault | vault | ✅ Yes | ✅ Yes | ✅ Yes | ❌ No |
| Opstella | opstella | ✅ Yes | ❌ No | ✅ Yes | ✅ Yes |
Go to Clients Panel > Click one of the client (Same name as Client Name) by Client ID column
Client List

Selected a Client

Select a Client
Go to Logout settings section > Make the switches on/off follow to the table: ✅ Yes: On / ❌ No: Off

| Client Name | Logout session required | Revoke offline sessions |
|---|---|---|
argocd | ✅ Yes | ✅ Yes |
defectdojo | ✅ Yes | ❌ No |
sonarqube | ✅ Yes | ❌ No |
gitlab | ✅ Yes | ❌ No |
harbor | ✅ Yes | ✅ Yes |
grafana | ✅ Yes | ❌ No |
kubernetes | ✅ Yes | ❌ No |
vault | ✅ Yes | ✅ Yes |
opstella | ✅ Yes | ❌ No |
💡 By default, Full scope allowed settings is ✅ Yes: On. Adjust accordingly if necessary.
Select a Client that require attention for Full scope allowed
Go to Client scopes Tab > selection XYZ-dedicated; where XYZ is the name of client

Go to Scopes Tab > Make the switches on/off follow to the table: ✅ Yes: On / ❌ No: Off

| Client Name | Full scope allowed |
|---|---|
argocd | ✅ Yes |
defectdojo | ❌ No |
sonarqube | ✅ Yes |
gitlab | ✅ Yes |
harbor | ✅ Yes |
grafana | ✅ Yes |
kubernetes | ✅ Yes |
vault | ✅ Yes |
opstella | ✅ Yes |
💡 By default, Exclude Issuer From Authentication Response settings is ❌ No: Off. Adjust accordingly if necessary.
Select a Client that require attention for Full scope allowed
Go to Advanced Tab > Go to OpenID Connect Compatibility Modes
Make the switches on/off follow to the table: ✅ Yes: On / ❌ No: Off

| Client Name | Exclude Issuer From Authentication Response |
|---|---|
argocd | ❌ No |
defectdojo | ❌ No |
sonarqube | ❌ No |
gitlab | ❌ No |
harbor | ❌ No |
grafana | ❌ No |
kubernetes | ❌ No |
vault | ❌ No |
opstella | ✅ Yes |
For Keycloak to provide application the permissions of a user correctly, this requires Mapper to be configured.
The following is the list of Keycloak Clients that each section will be its Mapper type.
Associate EACH client with Group Membership as groups Token Claim
Select a Client that require attention for Full scope allowed
Go to Client scopes Tab > selection XYZ-dedicated; where XYZ is the name of client

Click Add mapper > Click By configuration

Choose Group Membership

Configure as follow

| Tool/Instrument | Included Client Audience | Add to ID Token | Add to Access Token |
|---|---|---|---|
| DefectDojo | defectdojo | ❌ No | ✅ Yes |
Select a Client that require attention for Full scope allowed
Go to Client scopes Tab > selection XYZ-dedicated; where XYZ is the name of client

Click Add mapper > Click By configuration

Choose Audience

Configure as follow
XYZ ; Adjust accordingly.
Use the below navigation to proceed