...
app store id — 1547225480
team id — AD5M8U9NQL
This The above is a very important step because Google has strict limits and each client is only eligible for one mobile app and mobile platform at a time.
After two clients are successfully created, please provide us with the below info from each of the clients separately. This data can be downloaded as a text file directly from the client's window in the GCP console (there is a special button for this called "download plist" for iOS and "download json" for Android). These files will contain info such as client_id, auth_uri, token_uri, reverse identifier ( for iOS), etc. We need this to set up our app to communicate with these specific clients.
...
Specific to Okta
If you don't already have the Okta mobile client set up in Okta IDP, please follow steps 1-5 to help set create it up. Please note that the Okta web client is not suitable for mobile apps, you have to create a they require the native client.
App integration: You need to create
Create a native client for the Smarter Suite mobile application in the Okta console with the following parameters:
...
6.1 Client ID: This can be found in the "General" section of the native Okta client.
6.2 Okta Issuer (can be found in the "Sign On" section, should be in the following format: "https://xxx-1234567.okta.com")
6.2.1 It's important to ensure that the client ID on the General tab matches the "Audience" token in the Sign On section. A parameter mismatch indicates an error while creating the client.
6.3. If you opted to use the client secret — the client secret from the "General" tab
6.4. Last but not least, the custom API URL of the authorisation server (if applicable). It can be found by navigating to Security => API. By default, it looks similar to https://xxx-12345.okta.com/oauth2/default, but if it’s different, we need this information as well.
Please let us know if you have any issues with providing the data for points 6.1-6.4.
FINAL STEP: Chemwatch Web App Configuration for Smarter Suite Users
...