Hey there @LLXP,
Thanks for continuing the conversation here. Before I get into all the details about how to set up the API Service Integration in the OIN, I encourage you to sign up for the 2nd day of DevDay where these sorts of topics will be covered (link below). If you and your team are in the bay area, you’re also welcome to attend in person.
https://devday23sf.splashthat.com/
In your scenario, which is to create an OIN, you’ll want to create an API service that connects to your OIN application. It seems a little counterintuitive, but you’ll first want to start an OIN submission process (but you won’t complete the submission).
- Navigate to the OIN Manager to start the submission
- Sign in using your Okta account
- Press Add New Submission > API Service tab
- Enable support for the API service, and press Test in Okta
This creates an API Service Integration connected to your org so you can test it. This application is found in the Okta Admin console in Applications > API Service Integrations. I also added pics just in case it adds further clarity.
Clicking on the integration listing takes you to details about the application. On the General tab, you’ll see the Client ID and Okta Domain to use for requesting tokens.
On the Okta API Scopes, you’ll see the scope you requested as part of the OIN submission step.
When you implement your integration, the domain and Client ID will be unique for each of your customers who add your integration to their org, so providing that info to you will be part of their onboarding process with you.
Let us know how that works for you!