OpenID Configuration using Azure gives Bad Credentials

[sumantafinarb]

I tried configuration open ai confifuration using azure service principal it alaways gives me bad credentials.

Below is the sample setting I am using
SECURITY_AUTH_OPENID_ENABLED=“true”

SECURITY_OID_CLIENTID=“xxxx-be11-4a2e-xxxx-xxxxxxxx”

SECURITY_OID_APISECRET=“xxxxx~W-xxxxxxxx~4qw8.xxxxxxxxxx”

SECURITY_OID_URL=“https://sts.windows.net/xxxxx-xxx-babd-xx/”

SECURITY_OID_LOGOUTURL=“https://login.microsoftonline.com/xxxxx-c08a-xxxxx-babd-868d05984b80/oauth2/logout”

SECURITY_OID_EXTRASCOPES=“openid profile email offline_access”

SECURITY_OID_REDIRECTURL=“https://localhost/atlas/”

[uih8883 (Mark)]

@sumantafinarb Did you ever figure this out? We are trying to do something very similar with no luck so far. I will mention that we have an app registration and not a service principle in our case, but no matter what settings we use, as soon as switch from DisabledSecurity to AtlasRegularSecurity, the Atlas front end always loses connection to WebAPI and can no longer initialize.