It looks like my Auth Client screen is different than what is in the docs.
I do not have the âSecretâ field included on my screen and because of that I am unable to utilize the rest endpoints for corteza.
Has anyone else experienced this? How did you get the Secret for your auth client if itâs not on the screen?
Admin Area â Auth Clients
Corteza version: 2023.3.0
I created the new Auth Client and am logged in as a user with the Super administrator, administrator etc. roles.
Thank you.
References:
1 Like
I see the older documentation here that shows me how to generate the auth token for a user, command below, but Iâm hoping to figure out why the âSecretâ field isnât showing up on the Auth Client screen
./corteza-server auth jwt automationUser@tester.com --auth-client 338547059328414211
References:
Steps I used to generate valid JWT
- Create user with required permissions for whatever actions you want to perform
- Create auth client - select - Will be used to authenticate users (grant type = authorization_code)
- Selected all options when creating auth client
- Allow client access to userâs profile
- Allow client access to Corteza API on behalf of user
- Allow client to use OIDC and verify the userâs identity
- Allow client access to Corteza Discovery API on behalf of user
- Trusted
- Enabled
- ssh into server hosting Corteza
- Login to docker container running Corteza server - sudo docker exec -it 123456789a1b /bin/bash
- cd /corteza/bin
- ./corteza-server auth jwt 338546712354013955 --auth-client 338544564328414211 --duration 999999h0m0s
- Grab the generated jwt to use as the auth bearer token in api calls
Being able to generate the secret from the auth client screen is still much preferable since we could use an endpoint to grab the jwt rather than logging into the server but at least there is a path forward.
Sharing all of this in case anyone else experiences this challenge.
1 Like
