The Active Directory integration will allow you to authenticate the users of your app against your own existing Active Directory user pool.
OneBlink’s Active Directory integration uses SAML 2.0.
To use Active Directory you must have an Active Directory App configured. In the example below we are using the Enterprise application and choosing the "Integrate any other application you doin't find in the gallery (Non-gallery)" option.
Login to the console and go to the My Apps menu, click manage on your app and navigate to the User tab. User can be added manually on this screen, for more on users and adding users check out this article. Instead of using the out of the box user pool you can instead choose in integrate with your existing SAML SSO provide.
Note: You will need 'Business User' level permissions or higher to manage app users.
Once enabled follow along with the Active Directory set up steps.
OneBlink uses SAML 2.0 to communicate with your Active Directory. To configure the connection, on the App Users page, after you’ve enabled AD, you will see a guide with the steps involved.
OneBlink will give you an Identifier (Entity ID) and Reply URL (Assertion Consumer Service URL) that you will use in your Single Sign On application configuration.
It will also ask you to add your App Federation Metadata URL to the console. Once you save this configuration, you can now view your PWA to test it out.
If you have any questions or need any assistance, please create a support ticket above, or contact us at email@example.com.