Forum Discussion

Vasanth's avatar
Vasanth
New Contributor II
3 years ago
Solved

Issue with REST API connectivity to OS

Hi, We are trying to setup REST API by following the OS documentation. Here we are using Azure as external authentication provider. We are able to get the token successfully, but passing back to th...
Data Integration
REST Api
  • Vasanth's avatar
    Vasanth
    3 years ago

    All,

    I was able to get it fixed by connecting with OneStream support. Basically, there are some information missed in the Rest API documentation.

    After all the setup is done as per the documentation, we need to add a native user and, in the authentication, select as external user (Azure or Okta etc whatever you have for external AD). And in the external user name you need to provide the client ID as setup at the Azure or Okta. 

    Then in your rest API connection you need to use this native user name and the client secrets as the password.

    Hope this helps!

    Thanks,

    Vasanth

ChrisLoran's avatar
ChrisLoran
Icon for OneStream Employee rankOneStream Employee
3 years ago

Hello,
I would raise a support ticket.  The mention of Azure suggests this is a cloud/SAAS implementation, so might need the cloud team to investigate.

What do you mean by "OS documentation"?  The REST API guide? Server Configuration documents?

I assume there is not a problem with Azure AD users logging in to the application through the normal OS client, and it's only coming up with an error for your REST API client (Postman)?
By the look at that error I suspect this might have something to do with an incorrect Client ID (OneStream Web Api ClientID in the configuration file) may not match the ClientID in the REST API header. 

(Don't forget to restart IIS if server config changes are made).