Azure Provisioning Oauth Setup

[Ben Hook]

Hello,

I'm trying to set up Azure provisioning users into ServiceNow, which recently changed from user/password auth to Oauth. Following these 2 sets of directions 

https://docs.servicenow.com/bundle/tokyo-platform-security/page/administer/security/task/t_CreateEnd...

https://learn.microsoft.com/en-us/azure/active-directory/saas-apps/servicenow-provisioning-tutorial

However, some portions are still unclear to me:

-In the azure section "

• Authorization Endpoint: https://InsertInstanceName.service-now.com/oauth_auth.do?response_type=code&client_id=InsertClientID&state=1&scope=useraccount&redirect_uri=https%3A%2F%2Fportal.azure.com%2FTokenAuthorize"

What is the Client id? Is this the sys-id of the oauth entry in SN? Because as of now this is the error I receive when trying to test the connection from Azure

unauthorized_client: The client credentials provided (those of the service you are using) are either not valid or not trusted

[Tom Brown]

Today, a year and a half later, it appears that they have disallowed basic auth again.  We're trying to set up a different instance with EntraID/Azure, but the only appears to allow a Tenant URL and a Secret Token.

I was directed to this blog post when I was about to open a ticket with SN:  SCIM Provisioning from Microsoft Entra ID - ServiceNow Community .  I run into a brick wall when I get to the part about CURL and getting the "access token".  access denied, server error.

Any new developments that you've seen?  I noticed that there is a new token-based authentication available starting in the Washington release:  API Key and HMAC Authentication for inbound REST APIs (servicenow.com).