Weekdone - SAML Relying Party Configuration - RSA Ready Implementation Guide
Originally Published: 2021-09-07
Last Modified: 2024-08-12
This article describes how to integrate RSA with Weekdone using SAML Relying Party.
Configure RSA Cloud Authentication Service
Perform these steps to configure RSA Cloud Authentication Service as Relying Party to Weekdone.Procedure
- Sign in to the RSA Cloud Administration Console.
- Navigate to the Authentication Clients menu, and from the dropdown, select Relying Parties.
- In the Relying Party Catalog, select Add a Relying Party and click Add for Service Provider SAML.
- On the Basic Information page, enter a name for the application in the Name field and click Next Step.
- In the Authentication tab, select SecurID manages all authentication.
- Select the Primary Authentication Method and Access Policy as required and click Next Step.
- Provide the Service Provider details in the following format:
- Assertion Consumer Service (ACS) URL: https://weekdone.com/a/<SAML name>.
- Service Provider Entity ID: https://weekdone.com/a/<SAML name>/metadata.
Refer to the Weekdone Configuration section to obtain SAML name.
- In the SAML Response Protection section, select IdP signs assertion within response, and download the certificate by clicking Download Certificate.
- Under the User Identity section, select Show Advanced Configuration, then configure Identifier Type and Property as follows:
- Identifier Type: Auto Detect
- Property: Auto Detect
- Click Save and Finish.
- On the My Relying Parties page, click Edit dropdown and select Metadata option to download the metadata.
- Click Publish Changes to save your settings. After publishing, your application will be enabled for SSO.
Configure Weekdone
Perform these steps to configure Weekdone.Procedure
- Log in to Weekdone as an administrator.
- Click the profile icon at the top right corner, then select Company Settings from the dropdown menu.
- Click Single-sign-on (SAML2).
- Provide the following details and click Upgrade.
- SAML name: Enter a unique name used for configuration in the RSA platform. For example, use 'rsa' as the name.
- SAML SSO URL: The value of SingleSignOnService, obtainable from the metadata file downloaded from the RSA platform.
- SAML Logout URL: The value of SingleLogoutService, Obtainable from the metadata file downloaded from the RSA platform.
- X509 certificate: Upload the certificate downloaded from the RSA platform.
- Members must log in via SAML: Select the radio button to enable SAML SSO.
The configuration is complete.
Return to Weekdone - RSA Ready Implementation Guide
Related Articles
Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide 718Number of Views Palo Alto NGFW Global Protect - SAML Relying Party Configuration - RSA Ready Implementation Guide 145Number of Views Microsoft Entra ID Custom Controls - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide 247Number of Views Cisco ISE - SAML Relying Party Configuration - RSA Ready Implementation Guide 2Number of Views FortiGate Firewall - SAML Relying Party Configuration Using SSL VPN - RSA Ready Implementation Guide 63Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Reporting on RSA Authentication Manager 8.x users with On-Demand Token, a fixed passcode or a hardware/software token assi… How to Download OTP Token Seed Files from myRSA Anomalix idGenius - SAML Relying Party Configuration - RSA Ready Implementation Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?