cancel
Showing results for 
Search instead for 
Did you mean: 

REST API stopped working after upgrade to 7.1

dbeavon
Contributor

In the prior version of onestream we had configured AAD authentication, and we had a service principal that would be used to process REST API requests (aka the onestream "web api").  This service principal was simply to make all the requests for gettting data (cubeviews, adapters).

However since we upgraded to 7.1, the REST API has stopped working.  Whenever we present the onestream-web-api with the access token from AAD, it simply generates a bogus error: No Supported Authorization Provider Configured.

 

The reason the error seems bogus is because the AAD authentication provider is working for all interactive users.  It is only this particular AAD service principal that fails (the one associated with this REST api).

We noticed that the release notes for 7.1.0 says:

Microsoft is ending support for Azure Active Directory Authentication Library (ADAL) in December 2022. As a result, we have migrated to the Microsoft Authentication Library (MSAL) for authentication and authorization.

 

Based on this, I'm guessing there was a breaking change in the way that the REST API must be configured.  The upgrade did change the xml config, to some degree, but not in relation to this web API. 

Can someone please tell me where to find additional information that supports the unhelpful message that is sent to API clients: "No Supported Authorization Provider Configured"?  There has to be a log somewhere with the actual exception that is triggering this message.  The message is clearly not accurate as it stands.  We do have AAD identities working everywhere except in the web API.

 

Any help would be greatly appreciated.  I would guess that the developer(s) who worked on the migration from ADAL to MSAL would be able to help interpret this error message.

0 REPLIES 0