Issue in access token

[Abhishek Akant]

Hello,

I was trying to get a token using postman by following steps from the documentation.
Post url =  https://authorization.cerner.com/tenants/ec2458f2-1e24-41c8-b71b-0e701af7583d/protocols/oauth2/profiles/smart-v1/token

In authorization type, I have used basic auth and gave username and password as account id, or client id, and secret from system account.

Headers = Accept: application/json Content-Type: application/x-www-form-urlencoded

Body = grant_type=client_credentials&scope=system%2FObservation.read%20system%2FPatient.read

I am getting an error invalid client. 

{

    "error": "invalid_client",

    "error_uri": "https://authorization.cerner.com/errors/urn%3Acerner%3Aerror%3Aauthorization-server%3Aoauth2%3Atoken%3Ainvalid-client-credentials/instances/cb05939b-36b2-43cc-9636-1a28c56d6f37?client=unknown&tenant=ec2458f2-1e24-41c8-b71b-0e701af7583d"

}

Cerner-Correlation-ID: cb05939b-36b2-43cc-9636-1a28c56d6f37

Can anyone help me to solve this issue. I really appreciate any help. Also some document for further steps that need to complete the authorization process.

Thanks 

[paresh pradhan]

What is the response status in postman - 401?

Thanks,

Paresh

[Abhishek Akant]

Yes

[paresh pradhan]

I feel something wrong with your system account or password. It is working for me.

[Fenil Desani (Cerner)]

Hello Abhishek,

Can you please provide the clientID you are sending in?

Thanks,
Fenil

[Abhishek Akant]

Client id =  9e2f84ba-568a-e9a6-4dfb-b6413ee595a8    system app

CLIENT ID = Ec1b1e82-3ddf-4717-9f02-a2b356b45e3e   patient app

[Fenil Desani (Cerner)]

There are two steps to registering a System App.

• First, create a System Account
• Second, Register a System App using the above System Account

In you case, you completed the first step of registering a System Account and got an Account with SystemAccount ID: f58a******

In the second step, you registered the System App but not with SystemAccount ID: f58a******. Instead you used the ID: 9e2f84ba-568a-e9a6-4dfb-b6413ee595a8 which does not correspond to a System App, and hence the failure.

To make the App work correctly, you need to register a new System App and when asked to input the GUID, enter f58a******

Once done, while testing used the credentials from SystemAccount ID: f58a******

Thanks,

Fenil