Unable to fetch Access Token (Secret Token) using SCIM Oauth user Provisioning

[Bharath Kumar A]

Hello Team,

I have a issue with one of our client Azure User Provisioning, when selected as "Automatic" provisiong.

It is asking for Tenant URL and Secret Token

I have installed SCIM plugin and modified the SCIM API Application Regitry and generated authorization token.

I am getting error when i am executing following url to get access token to fetch secret token from that.

"https://<instance-name>.service-now.com/oauth_token.do?grant_type=authorization_code&code=Vpf40iSI4kxxxxxxxxxxx&client_id=54xxxxxxxxxxxxxxxxx&client_secret=a1b2c3xxxxxxxxxxxxxxxq&redirect_uri=https://<instance-name>.service-now.com/login.do&scope=useraccount"

Can you please help me to correct it.

[Matthew Billy]

Hi @Bharath Kumar A 

I found this dev blog article (SCIM Provisioning from Microsoft Entra ID) to be helpful, you'll find the instructions near the middle of the document under the section "Generate and retrieve the Bearer Token (Secret Token)"

The basics of the process are:

1. Goto All -> System Oauth -> Application Registry.
2. Open the "SCIM API" record.
   
   
3. Take note of the "Client ID".
4. Update the "Client Secret" to a known value.  I recommend you select a complex 40-character secret; noting that you can only use alphanumeric characters.  Make sure you record the value.
5. Consider your "Access Token Lifespan" & "Refresh Token Lifespan". The Access Token Lifespan in particular will determine how often you need to reenter the Secret Token into Entra ID.
6. Update the record.  
7. Next we need to use the OAuth Token retrieval process to retrieve the Bearer Token.
8. Generate the Authorisation Code

You'll want to continue the steps from that document.

Basically, you need to provide a SECRET, which is alphanumeric upto 40 characters.

Upvote and mark helpful if this applies.

Regards,
Matthew Billy