Skip to content

client credential flow#1252

Draft
MahirAbbas wants to merge 29 commits intomainfrom
ma/k6-secrets
Draft

client credential flow#1252
MahirAbbas wants to merge 29 commits intomainfrom
ma/k6-secrets

Conversation

@MahirAbbas
Copy link
Copy Markdown
Contributor

No description provided.

name: graph-proxy-k6-auth
key: KEYCLOAK_CLIENT_SECRET
- name: KEYCLOAK_TOKEN_URL
value: https://identity.diamond.ac.uk/realms/dls/protocol/openid-connect/token
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FYI the initial token that you were given in https://jira.diamond.ac.uk/servicedesk/customer/portal/5/UASHD-4191
was for
https://identity-test.diamond.ac.uk/realms/dls

There are three Keycloak servers at Diamond: identity-test, identity-dev, identity (production). You need to use one that matches the client that you were given.

Note the workflows staging cluster only works with the identity servers listed here:

If you want your system to work with identity-test then the staging cluster needs to be modified to accept that server as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants