Getting error "User not Authenticated" when trying to make REST calls using OAuth 2.0 with okta

[rajkumar5]

1) I have created new application in okta .Attached screenshot in below :

2) And i've created OIDC Provider configuration in servicenow instance and configured client id and secret which is copied from Okta.

 And enabled "User Provisioning"

And in the OIDC Provider Configuration User Claim "email" is mapped to sys_user field (Email).

I've also created a user, where the Email field contains the value of my Okta user email value. I've also added some roles(include admin,security admin,api access ) to the user.

I have got the access token from Okta but when i send this to inbound table API GET method, i'm getting error message

"error": {
"message": "User Not Authenticated",
"detail": "Required to provide Auth information"
},
"status": "failure"
}

Could you please help me on this issue?

Thanks!

[rajkumar5]

@raghav and @Goran, Issue not resolved... Still looking for best answer 😐

[Goran WitchDoc]

Just so I get this clear. You want to use this for login but it doesn't work. And if you use it with postman it doesn't work either? Or are you using this to reach an endpoint on an instance where you are authentication through okta (OAuth)?

//Göran
Feel free to connect:
LinkedIn
Subscribe to my YouTube Channel
or look at my Book: The Witch Doctor's Guide To ServiceNow

[hammad ul aziz2]

Hi, @mageshkumar 

i implemented the whole process the problem is that the user in servicenow needs to have the same password as okta profile only then it will grant access to that API.

and make sure that user has a rest_service role granted.

please mark this correct and helpful if this helped you in any way.

thanks

hammad

[RaghavSh]

@mageshkumar follow below steps:

1. Request new token and copy "id_token" not "access_token" it is below the "access token",

2. Set the authentication to "inherit from parent".

3. In the "headers" pass authentication as Bearer <space> <id_token from step1>

[Goran WitchDoc]

I think Raghav is on the right track here. you seem to use the access token instead of the id token.

//Göran
Feel free to connect:
LinkedIn
Subscribe to my YouTube Channel
or look at my Book: The Witch Doctor's Guide To ServiceNow