Does Azure AD support custom HTTP Headers for SCIM User provisioning?

Question

I am doing SCIM User Provisioning. For that I have developed SCIM APIs which supports client credentials authorization mode as well as long lived token in the form of API Key. When I was testing Azure AD SCIM Provisioning, I can see Azure supports long lived token only with Bearer prefix. And since my application was not onboarded, I was not able to test client credentials flow.

Is there a way we can use custom HTTP Header for SCIM user provisioning? Eg. Rather than Bearer prefix, does Azure support anyother custom prefix?

And is there a way I can test client credentials authorization flow without making my application a gallery app on Azure?

Answer 1

Hi @SHIVANK AGARWAL ,

The SCIM validator only accepts bearer tokens, and that the token value provided will be passed as the value for the HTTP Authorization header. I don't believe what you are asking for is supported, though I have reached out to a colleague on the provisioning team to share this feedback and see if they can add additional insights.

You can also leave feedback in the feedback portal. https://feedback.azure.com/

If the information helped you, please Accept the answer. This will help us as well as others in the community who may be researching similar questions.

Answer 2

Thanks @Marilee Turscak-MSFT

I believe you are referring to the point of passing custom HTTP Header prefix apart from "Bearer" prefix. Any idea if this can be supported or already in pipeline?

Also, can you please specify if there is a way I can test client credentials grant flow for my application which is a non gallery app?