Note: The following article was designed for users of our free, one app edition -- Okta Cloud Connect. The steps below will guide you through the basic configuration between your directory, app of choice, and Okta. Paid Okta customers should also review the Exploring the Okta Application Network article.If you don't see your Application listed in one of the playbooks, don't worry - the steps are still the same.
There are three steps to implementing any application with OCC
Step 1: Deploy the Okta AD Agent
Note: If you are using the LDAP Agent - Please click here for more Information
There are five basic steps to deploying the Okta AD agent. Please refer to Okta AD Agent article for these steps. For a detailed Deployment Guide that explains everything there is to know please refer to Installing and Configuring the Active Directory Agent
Step 2: Configure the application in Okta
This video shows the steps for configuring Box with Okta - which gives you the steps not matter your application
Step 3: Deploy the Desktop SSO Agent (Optional)
Configuring the Desktop SSO agent is an optional step, that end users love. It allows them to not to re-enter their AD credentials when accessing the application. Okta uses Microsoft Integrated Web Authentication to check their kerboros ticket, if the ticket is valid and authenticate, then access to granted to the application and the user never sees the log in page.
To deploy the Desktop SSO agent refer to the following guide: Configuring Desktop SSO
While the Okta configuration is generally straightforward, the Okta team is here to help: