Hi,
I have recently taken over work for our Cis2 authentication implementation and it seems that our request to receive the Id token is only returning an access token.
I’m making the call to https://int.api.service.nhs.uk/oauth-mock/token using the client secret and prior to this I authenticate using User UID 656005750108 on the Cis2 Mock Int log in screen. I’m returned a 200 ok response from the token request that only contains the access token.
Please advise whether this might be a config issue (if it is what might be missing) or if I’m using the wrong URI.
Hello! I’ve got windows hello set up now but I’m still facing some issues. Firstly for the initial connection after authenticating using windows hello is the “code” returned the auth code that I use in acquiring the ID token? I’m given:
{code, xxxx}
{iss, yyyy}
{state, zzzz}
{client_id, iiii}
Secondly on the token request I’m the error “Invalid client or Invalid client credentials”. I’m unsure if this may be due to using the wrong client id, auth code, secret or url. Is there any way that we could start a private chat to discuss this in more detail?
I’m now under the assumption that the URI i’m calling for the token endpoint may be incorrect as I’ve tried with both private key jwt (which looks correctly formed) and with client secret, both are getting the same invalid client credentials error.
Hi @sgroom, you appear to be mixing the real INT environment and the mock CIS2 Auth endpoints. You would need to make the id_token request to the same service as the initial auth was made. Please reach out to the onboarding team and they can either offer guidance or reach out to myself or the technical team if you have any further questions