The OneStream Community is temporarily frozen until June 29th due to the ongoing maintenance. Please read the blog post here to learn more.
Forum Discussion
Solved
Okta Bearer Token for API call
Hi Community,
We are trying to set up Rest API call to execute Data Management (OneStream v8.1) call from external system (e.g. Postman)
I followed the document for REST_API_Implementation_Guide....
I've only used Azure so don't have an example. A quick google didn't seem to be super helpful but it looks like there are a few video tutorials about it.
Basically you create a new request which connects to Okta and will retrieve a new bearer token. On the test tab of that request you have your set variable command which you tried above. Most likely this bearer token will have a timelimit of say 60 minutes so you will need to run it every time you want to test things, prior to running your OneStream request.
Then on your OneStream request you will populate your bearer token variable into the bearer token field.
Are you using OneStream Identity Server? I believe it is required for v8+ in the cloud.
If so, you will need to create personal access tokens in OneStream and place them directly in the authorization tab in Postman.
https://documentation.onestream.com/1375907/Content/IDM/Access%20the%20Manage%20Personal%20Access%20Tokens%20Page.html
It is a two steps process once the Okta has been configured correctly:
1. We were able to get the bearer token using the correct Okta link and save it into a variable (Postman)
2. USed that vairable in the bearer token (Authentication tab) to call OS API to execute DM job
Per this documentation, I believe that all customers v8 and above will use OIS, which no longer has the steps of getting the bearer token and uses the personal access token. If you are able to get bearer tokens to work on v8+, then I would be interested to know about it as this would be a deviation from my understanding.
OneStream Identity Server (OIS) Content - OneStream Community (onestreamsoftware.com)
Yes you right for OIS, that implementation was for version 7.1.1 on-premises