Workday - SAML Relying Party Configuration - RSA Ready Implementation Guide
Last Modified: 2026-02-23
This article describes how to integrate Cloud Access Service (CAS) with Workday using SAML Relying Party.
Configure CAS
Perform these steps to configure CAS as Relying Party to Workday
Procedure
- Sign in to RSA Cloud Administration Console.
- Navigate to Authentication Clients > Relying Parties.
- On the My Relying Parties page, click Add a Relying Party.
- From the Relying Party Catalog, click Add next to Service Provider SAML.
- On the Basic Information page, enter a name for the application in the Name field, then click Next Step.
- On the Authentication page, select RSA manages all authentication.
- From the 2.0 Access Policy for Authentication dropdown list, select a policy that was previously configured, then select Next Step.
- In the Data Input Method section, choose Enter Manually.
- In the Service Provider section, enter the following values:
- Assertion Consumer Service (ACS) URL: https://<WORKDAY-domain>/<tenant>/login-saml.htmld
- Service Provider Entity ID: Enter the same Service Provider Entity ID entered in the format http://<WORKDAY-domain>/<tenant>/
- In the Message Protection section, choose IdP signs entire SAML response.
- In the User Identity section, select the following values:
- Identifier Type > unspecified
- Property > sAMAccountname
- Click Save and Finish.
- Click Publish Changes and wait for the operation to be completed.
- After publishing, your application is now enabled for SSO.
- On the My Relying Parties page, navigate to the newly created application and choose Metadata from the dropdown list.
Configure WORKDAY
Perform these steps to configure WORKDAY SIP
Procedure
- Log in to WORKDAY tenant with an Administrator account.
- Navigate to Account Administration > Edit Tenant Setup – Security.
- Click the + icon under Redirection URLs to add a row.
- In the Redirect URLs section, enter the Login Redirect URL for your tenant. This should match the ACS URL in the RSA configuration.
- Use the scroll bar to continue filling the SAML Identity Provider fields.
- In the SAML Setup section, Enable the Enable SAML Authentication checkbox, then click the + icon under SAML Identity Providers.
- Click Import Identity Provider, select the meta data file downloaded from RSA.
- Configure the fields in the SAML Identity Provider table, select the following values:
- Enter a unique value for the Service Provider ID.
- Enable the Enable SP Initiated SAML Authentication.
- Enable the Do Not Deflate SP-initiated Authentication Request.
- Enable the Always Require IDP Authentication.
- Select ForceAuthn Only.
- Click OK.
The configuration is complete.
Related Articles
Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide 739Number of Views FortiGate Firewall - SAML Relying Party Configuration Using SSL VPN - RSA Ready Implementation Guide 65Number of Views Okta - SAML Relying Party Configuration - RSA Ready Implementation Guide 48Number of Views Fortinet IPsec VPN - SAML Relying Party Configuration – RSA Ready Implementation Guide 13Number of Views Google Cloud Workforce Identity - SAML Relying Party Configuration – RSA Ready Implementation Guide 38Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA-2026-24: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities IDR SSO - Step 3: Deploy the Identity Router RSA Authentication Manager 8.9 Setup and Configuration Guide
Don't see what you're looking for?