Hello All,
Set up SSO for a workday tenant and pretty straightforward SAML setup instructions provided by Okta. triple checked URLs, issuer ID, certificate on workday side so it cant be that. Assigned a group of test users to the app in Okta and they all receive the error above. Is this an attribute issue where user name attribute sent by Okta does not match any user name in Workday?
Wondering what other companies that have their HR system integrated with Okta do in this situation -
We use Workday to manage our employees and at the time of the Workday record creation, the HR team issues the new hire a username and a password to go upload their paperwork into Workday, typically days or weeks ahead of the actual start date.
Fast forward to start date, IT uses the same Workday username BUT issues a different password via Okta, that can now be used as the global credentials for everything, Workday included as that is now behind SSO.
HR wants to better the onboarding experience (and lessen their password reset requests) and give the user only one password to rule them all, at the moment when the Workday record is created.
On Security end, we are not super keen with the idea of giving people access to their apps ahead of the start date, and we use RBAC which means they get all their apps at once.
How is your company approaching this scenario?
Do you know why with SSO you still need to enter Microsoft credentials rather than accessing Workday the way Outlook or other applications with SSO are being accessed? Is it a Workday restriction (something that could be changed in the Tenant Setup) or if it's a configuration on the SSO Microsoft side?