OAuth2 Deployment for Multiple integration

(0) Share

Report

Posted on by Dixonsamuel

Hi everyone,

I've got a scenario here.

I've got a customer that will having around 7-10 integrations.

As everyone is aware, basic authentication is going to be deprecated in BC Wave1 2022.

Therefore, the issue we have is, we are looking at around 3-5 vendors doing the integration for various applications.

From what I've tried, The OAuth2 account needs to have a BC license for the authentication to work properly, on top of that, the account is tagged to an OTP which is linked to a mobile number.

As anyone might be aware, if all the vendors share one single login, the OTP will need to be retrieved from that single mobile number.

It won't be ideal to purchase additional licenses for vendor just to perform integration. Which the refresh token from OAuth2 is valid for a fixed duration only.

Does anyone have an idea what is the best practice? How did you all fix your multiple integration logins for different vendors with OAuth2?

Appreciate any response.

All responses (2)

Answers (1)

Suggested answer

Dixonsamuel 60 on at

Like (0)

Report

RE: OAuth2 Deployment for Multiple integration

Hi Steven,

thanks, client credentials does seem like a good alternative.

We did not encounter the OTP account.

Almost similar to a basic authenticaton.

Will say this will suffice.
Verified answer

steveendow 2,281 on at

Like (0)

Report

RE: OAuth2 Deployment for Multiple integration

Hi,

Have you looked into the Device Code or Client Credentials flows?

https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-device-code

https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-client-creds-grant-flow