I am working on setting up a web services connector to the Microsoft Graph API. I am currently only able to get the test connection to succeed if I manually set the header values to be:
Authorization Bearer
I’ve attempted using $application.accesstoken$ and $application.access_token$ and my test connection returns a 401. Does anyone have experience with this type of set up?
The $application.accesstoken$ is only created and set as part of using Custom Authentication (see Configuration for No / Custom Authentication), in which case you would need to also define the Custom Authentication connector operation.
If you’re able to successfully access the API with a Bearer token, you should be able to configure the connector’s Authentication settings to use that token for you automatically by using the API Token authentication type.
I’m curious to what the reason is for configuring a connector to the MS Graph API via the Web Services Connector instead of using the OOB AzureAD connector (Integrating SailPoint with Azure Active Directory)
I’ll check that out, thank you!
I’m attempting this method specifically as a Sailpoint rep mentioned we would need web services connector to manage Azure AD App Roles.
Azure Web Services Config Example.docx (661.2 KB)
We use Microsoft API no issues with Web Services I took screenshots of the setup so you can see. One call out is our client ID and secret where encrypted using the API and we reference $application.clientsecret_CA$
Good luck
@tranetechnologies Thank you! Your screenshots helped immensely. After seeing this example, it makes a ton of sense, as this is how I request a token in PowerShell with a client id/secret.
I appreciate all of the help!