This 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.
There are three steps to implementing Workday with OCC
Step 1: Deploy the Okta AD Agent
Note: If you are using the Okta Java LDAP agent, 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 more details, see Installing and Configuring the Active Directory Agent.
Step 2: Configure the Workday application in Okta
This video shows the steps for configuring Workday with Okta.
Step 3: Deploy the Desktop SSO Agent (Optional)
Configuring the Desktop SSO agent is an optional step that end users love. It frees them from having to re-enter their AD credentials when accessing the application. Okta uses Microsoft Integrated Web Authentication to check Kerboros tickets. If tickets are valid and authentication is successful, access is granted to the application and users never see the log in page.
To deploy the Desktop SSO agent, see Configuring Desktop SSO.
While the Okta configuration is generally straightforward, the Okta team is here to help: