Please note that the advice provided here is general in nature and does not account for the specific set-up of your Active Directory instance. Digistorm can only provide general advice on these systems.
Before you start
Depending on the specific configuration of your app and external systems, there could be some additional considerations outside of what we have documented here.
To start this process, please reach out to your Customer Success Manager or our Support team via live chat.
They will also be able to provide you with access to the App Config Portal mentioned below.
Set up in Active Directory
NOTE: OAuth is only supported in ADFS 2016 or greater.
To enable OAuth via ADFS, we will require you to set up an OAuth application within your AD instance.
Instructions from Microsoft on setting up an OAuth Application in your Active Directory instance can be found here:
You will need to use the following details from the Digistorm App Config portal:
Redirect URI - do not use https://localhost:44326 - use the callback URL
This will look similar to https://app-oauth.digistorm.io/UUID/callback
You will need to load the following details into the Digistorm App Config portal:
Client ID - enter the Client Identifier value from step 3
Client Secret - enter the Secret value from #4
Base URL - the URL of your ADFS instance
for example https://adfs.dscollege.edu/adfs/
In addition to the details above, your Digistorm content may ask for a test user to provide to Apple and Google for their review of the app and to keep on file for any support items.
Integration specific considerations
If your app has a Schoolbox integration, we will also need you to set up these details within Schoolbox. Details on this process can be found here.