JobAdder: How to Create & Send Document Template with Secured Signing You can create document templates within Secured Signing, using JobAdder data. For example, create template for employment contracts, terms of business and much more. Watch the video below to learn more.
ADFS 2.0: Configuring Single Sign On for Secured Signing using Active Directory Federation Services Setting up active directory federation services for use with Secured Signing will allow the nominated users within your domain to use the Secured Signing service using their network credentials. When the single sign on option is enabled in Secured Signing, logged in users will not need to enter their username and password in Secured Signing. The configuration process requires:Activation and configuration of federations services within Active DirectoryAdd Secured Signing as a relying party trust in ADFSConfiguration of your Secured Signing membership to accept authentication against Active Directory using federation services. Install and Configure ADFS 2.0 If not already installed, download & install ADFS 2.0. The software is available through here.NOTE: Don’t install the ADFS role from server managementIf you are using Windows Server 2008 R2, you will need to apply the ADFS 2.0 hot fix. Download it from this link.Prepare a valid ssl certificate (.pfx file, with private key). This certificate will be used by the ADFS federation service website, so it should be valid with your ADFS website domain name.2Import this certificate to IISOpen IIS, click server node, double click Server Certificates, then click Import at the right action panel Configure the ADFS 2.0 Federation serviceRun ADFS 2.0 Management Console as domain administrator. Run Create new federation service wizard. Use the certificate imported above to finish the configuration.In IIS manager, go to the Default Web Site/adfs/ls application,. Double click Authentication, enable Windows Authentication. In the advanced settings window, select Extended Protection to Off On IIS manager, add https bindings with above certificate to Default Web Site.Don’t change other default settings in IISIn ADFS 2.0 Management Console, find metadata xml path from right panel of “ADFS 2.0/Service/Endpoints”. It should be in the format https://your.domain.com/FederationMetadata/2007-06/FederationMetadata.xmlVerify the ADFS service is running by accessing the server: https://your.domain.com /adfs/ls/IdpInitiatedSignon.aspxEnable CROS for ADFS websiteAdd below lines to the web.config under Default Web Site/adfs/ls application directory <system.webServer> <httpProtocol> <customHeaders> <add name=”Access-Control-Allow-Origin” value=”*” /> </customHeaders> </httpProtocol> </system.webServer> Optional: set token caching time in the power shell console: > Set-ADFSProperties -SSOLifetime 5 > Set-ADFSRelyingPartyTrust -TargetName adfs.dsx.co.nz -TokenLifeTime 5 > Set-ADFSProperties -ReplayCacheExpirationInterval 5 > Set-ADFSProperties -SamlMessageDeliveryWindow 5 Restart the ADFS 2.0 service and IIS Add relying party trust Once ADFS 2.0 is ready, add a new relying party trust to the ADFS 2.0 service.In the ADFS 2.0 console, run “Add Relying Party Trust” wizard.Click “Start”, select “Enter data about the relying party manually” option and click “Next”.Enter a display name and click “Next”Select “ADFS 2.0 profile” options and click “Next”You can Ignore the encryption certificate, so just click “Next”Enable both WS-Federation Passive protocol and SAML 2.0 WebSSO protocol. For both protocols input https://www.securedsigning.com/ADFS/Account/LoginCallbackAdfs as endpoints and click “Next” Input https://www.securedsigning.com/ADFS/Account/LoginCallbackAdfs as identifiers and click “Next”Please notice that the rely party identifier is case sensitive. Please input the exact value. Select the > Permit all users to access this relying party option and click Next Click Next and CloseIn the popup claim rule window, add a new Transform Claim Rule In the popup wizard, select Send LDAP Attributes as Claims and click Next Input the rule name, select Active Directory as the Attribute store and select the LDAP attributes below E-Mail-Address -> E-Mail Address Surname -> Surname Given-Name -> Given Name User-Principal-Name -> Windows account Name Click Finish Setup Single Sign On with ADFS in your Secured Signing Membership You need an enterprise account to integrate secured signing with your own ADFS server.Login to the Enterprise Portal and go to Memberships.Select the membership that requires single sign on with ADFS. In the Single Sign On tab. Enable Single Sign On and input your Federation Metadata Address. Click Users Setup button. This will open the Accounts management page where you can manage your accounts to use ADFS integration. All accounts under this membership must login with ADFS. Users will no longer be able to authenticate using a username and password to access Secured Signing. Select an account from the account list, input the User Domain Name Login (ADFS) and save. This Single Sign On input option is visible only when the Single Sign On has been enabled for the membership. The User Domain Name Login should be in the format ‘Domain\Windows Account’. This should be the User logon name (pre-Windows 2000) property from Active Directory User properties. The “User Domain Name Login” is case insensitive. It should not be duplicated (use same domain name for different accounts) in one membership. You need to setup all accounts for ADFS login. Activate user account Once user account created, the user will receive an activation email, click Click to Activate button in the email. Then in the activation page, click Activate button. Join an Existing Secured Signing Account to a Membership with Single Sign On enabled For an existing user, they can join a membership by adding the membership code to the My Account > My Details page If this membership is configured to use Single Sign On with ADFS, the user will need to enter tjheir User Domain Name Login and click “OK” to join the membership.Initial Login with Single Sign On (ADFS)Once single sign on is enabled, the first time each user accesses Secured Signing they will need to input their email to login. A password is not required.The system will check if Single Sign On is enabled for this user. If so, it will redirect to your ADFS server website. Then the user input his/her windows logon credential to login with your ADFS server. The user can check the option to “Remember my email” to login with ADFS next time.Once the user has logged in with ADFS successfully, the user will be redirected to Secured Signing. On subsequent logins, the user’s domain name will be remembered. Click “Log in with ADFS” the user will be logged in to Secured Signing using the domain name to login.Please notice that, with this option, you should logon to windows with your own account to login with ADFS. Otherwise, you may see an error saying “Cannot login, use your own computer to retry or contact your administrator.”.
Single Sign On (SSO) Setup Guide Welcome to the Secured Signing Single Sign-On (SSO) Documentation!This comprehensive guide is here to help you seamlessly integrate and utilize Secured Signing SSO with platforms. Whether you’re setting up for the first time or optimizing your existing configuration, you’ll find everything you need for a smooth and efficient experience.Explore the links below for detailed instructions and additional resources! Active Directory Federation Services Learn how to set up active directory federation services for use with Secured Signing. ADFS 2.0 Single Sign On (SSO) ADFS 4.0 Single Sign On (SSO) Azure Active Directory Learn how to set up active directory federation services for use with Secured Signing. Azure Active Directory Single Sign On Okta Learn how to set up Okta for use with Secured Signing. Okta Single Sign On Duo Learn how to integrate Secured Signing with Duo Single Sign-On and enhance your security framework. Duo Single Sign-On
ADFS 4.0: Configuring Single Sign On for Secured Signing using Active Directory Federation Services Setting up active directory federation services for use with Secured Signing will allow the nominated users within your domain to use the Secured Signing service using their network credentials. When the single sign on option is enabled in Secured Signing, logged in users will not need to enter their username and password in Secured Signing. The configuration process requires:Activation and configuration of federations services within Active Directory;Add Secured Signing as a relying party trust in ADFS; andConfiguration of your Secured Signing membership to accept authentication against Active Directory using federation services. Install and Configure ADFS 4.0Prepare a valid ssl certificate (.pfx file, with private key). This certificate will be used by the ADFS federation service website, so it should be valid with your ADFS website domain name.Add Active Directory Federation Service Role to the serverOn Windows 2016, Open Server Manager, click “Add roles and features”, select “Active Directory Federation Service” on the popup, and press next to install new role.For more details: visit hereRun ADFS Management tool from Service Manger.Click “Certificates”, import your certificate to ADFS service.Add relying party trustOnce ADFS 4.0 is ready, add a new relying party trust to the ADFS 4.0 service.On ADFS Management, Click “Add Relying Party Trust”Select “Claims aware” on the wizard popup, and click “Next”Select “Enter data about the relying party manually” and click “Next”Input “www.securedsigning.com” in the “Display name” and click “Next”Browse to your certificate to import certificate and click “Next”Enable both WS-Federation Passive protocol and SAML 2.0 WebSSO protocol. For both protocols input https://www.securedsigning.com/ADFS/Account/LoginCallbackAdfs as endpoints and click “Next”Input https://www.securedsigning.com/ADFS/Account/LoginCallbackAdfs as identifiers and click “Next”Please notice that the rely party identifier is case sensitive. Please input the exact value.Select the “Permit all users to access this relying party” option and click “Next”Click “Next” and “Close”Select new added Relying party trust “www.securedsigning.com”, click “Edit Claim Issuance Policy…”click “Add Rule…”In the popup wizard, select “Send LDAP Attributes as Claims” and click “Next”Input the rule name, select “Active Directory” as the Attribute store and select the LDAP attributes below: E-Mail-Address -> E-Mail Address Surname -> Surname Given-Name -> Given Name User-Principal-Name -> Windows account Name Click “Finish”Setup Single Sign On with ADFS in your Secured Signing MembershipYou need an enterprise account to integrate secured signing with your own ADFS server.Login to the Enterprise Portal and go to “Memberships”.Select the membership that requires single sign on with ADFS. In the “Single Sign On” tab. Enable Single Sign On and input your “Federation Metadata Address”.Click “Users Setup” button. This will open the Accounts management page where you can manage your accounts to use ADFS integration. All accounts under this membership must login with ADFS. Users will no longer be able to authenticate using a username and password to access Secured Signing.Select an account from the account list, input the “User Domain Name Login (ADFS)” and save. This Single Sign On input option is visible only when the “Single Sign On” has been enabled for the membership.The User Domain Name Login should be in the format ‘Domain\Windows Account’. This should be the “User logon name (pre-Windows 2000)” property from Active Directory User properties.The “User Domain Name Login” is case insensitive. It should not be duplicated (use same domain name for different accounts) in one membership.You need to setup all accounts for ADFS login.Activate user accountOnce user account created, the user will receive an activation email, click “Click to Activate” button in the email. Then in the activation page, click “Activate” button.Join an Existing Secured Signing Account to a Membership with Single Sign On enabledFor an existing user, he/she can join a membership by adding the membership code to the “My Account” -> “My Details” pageIf this membership is configured to use Single Sign On with ADFS, the user will need to enter tjheir User Domain Name Login and click “OK” to join the membership.Initial Login with Single Sign On (ADFS)Once single sign on is enabled, the first time each user accesses Secured Signing they will need to input their email to login. A password is not required.The system will check if Single Sign On is enabled for this user. If so, it will redirect to your ADFS server website. Then the user input his/her windows logon credential to login with your ADFS server. The user can check the option to “Remember my email” to login with ADFS next time.Once the user has logged in with ADFS successfully, the user will be redirected to Secured Signing. On subsequent logins, the user’s domain name will be remembered. Click “Log in with ADFS” the user will be logged in to Secured Signing using the domain name to login.Please notice that, with this option, you should logon to windows with your own account to login with ADFS. Otherwise, you may see an error saying “Cannot login, use your own computer to retry or contact your administrator.”.
Azure AD: Configuring Single Sign On for Secured Signing using Azure Active Directory Setting up Azure Active Directory (Azure AD) for use with Secured Signing will allow the users can login Secured Signing by using their organizational account hosted in Azure AD as the Identity Provider. When the Azure AD single sign on option is enabled in Secured Signing, logged in users will not need to enter their password in Secured Signing. The configuration process requires: Install app in Azure AD for your organization. Configuration of your Secured Signing membership to accept authentication against Azure Active Directory. Join an Existing Secured Signing Account to a Membership with Azure AD Single Sign On enabled Initial Login with Single Sign On (Azure AD) Install app in Azure AD for your organization Make sure you login Azure AD portal (https://portal.azure.com) with administrator account and click “Azure Active Directory” icon. Click “Enterprise applications” menu item. Click “+ New appliction” menu item. In Add from the gallery section, type “secured signing“, then it will auto populate – “Secured Signing Login“, click on that. Now, click “Sign up for Secured Signing Login“, it will redirect you to app consent authority page. Read the consent information and click “Accept” button to continue. After that, it will jump back to Secured Signing website, since you haven’t bound account between Secured Signing and Azure AD, you can’t login right now, please continue to read the below chapter – Setup Single Sign On with Azure AD in your Secured Signing Membership You can confirm app has been installed by visit MyApps (it may takes several minutes to appear) Setup Single Sign On with Azure AD in your Secured Signing Membership You need an enterprise account to integrate secured signing. Login to the Enterprise Portal and go to “Memberships“. Select the membership that requires single sign on with Azure AD. Click “Single Sign On” tab. Tick “Enable Single Sign On Azure Active Directory” checkbox. Click “SAVE SETTINGS” button. Then, all users in that membership will use Azure AD to login. Activate user account Once new user account created for that membership (Azure AD login) through Enterprise Portal, the user will receive an activation email, click “Click to Activate” button in the email. Then in the activation page, you just need to click “Activate” button (the email address already popuped), then, it will redirect you to Azure AD, you need to input your Azure AD password for authentication, after that, it will redirect you back to our website with logined status. Join an Existing Secured Signing Account to a Membership with Azure AD Single Sign On enabled For an existing user, he/she can join a membership by adding the membership code to the “My Account” -> “My Details” page, put Membership Code and click “Join Membership“ Initial Login with Single Sign On (Azure AD) Once single sign on (Azure AD) is enabled, the first time each user accesses Secured Signing they will need to input their email to login. A password for this case is not required. The system will check if Single Sign On (Azure AD) is enabled for this user. If so, it will redirect to Azure AD login page. Then the user input his/her organizational logon credential to login with Azure AD server. The user can check the option to “Remember my email” to login with Azure AD next time. Once the user has logged in with Azure AD successfully, the user will be redirected to Secured Signing.
SharePoint: How to Send a Document for Signing Step 1: Open with Secured SigningYou can initiate signing from menu, or from context menu:Select one document, and choose “Secured Signing” from menu, select your action from the dropdown menu items, orRight click one document, and select your action from the context menu.Different action will redirect to different pages. In this sample, click “Send for Signature”.Option 1 from the dropdown menu. Option 2 from the context menu. Step 2: Login with Secured SigningYou need a Secured Signing account to connect with SharePoint Online. Input your credentials to login Secured Signing. If you don’t have a Secured Signing account, click “Register”.On the next step, click “Authorize” to allow your Secured Signing permissions. Step 3: Start Signing Your DocumentOn the next page, you should see your account’s info on the top right. Selecting different actions will show different pages. In this sample, you can choose how you would like to sign your document.
SharePoint: Connect the Secured Signing App for Digital Signing Step 1: Open SettingsLogin into your SharePoint Online, go to the Site where you want to connect with Secured Signing. Click the gear icon on the top right and select “Add an app”. Step 2: Search for Secured Signing AppOn the Site contents page, click “SharePoint Store” from the left, then input “Secured Signing” search. Find the Sharepoint Store. Search “Secured Signing”. Step 3: Install Secured Signing AppClick the “Secured Signing” app, click “ADD IT” on the app details page. Then click “Trust It” on the popup window. Add the “Secured Signing for Sharepoint Online” app. Trust the “Secured Signing for Sharepoint Online” app. Step 4: Secured Signing App installedNow SharePoint Online starts to install Secured Signing, the app is gray out and would turns into blue after completing installation. Go to “Documents”, check if “Secured Signing” menu appears.Next: learn how to use Secured Signing App
Google Docs: Use the Secured Signing Digital Signing App Step 1: Sign with Secured SigningClick Add-ons menu in Google Doc, choose Secured Signing – Secure Digital Signature, then choose Sign with Secured Signing Step 2: Start Signing Your DocumentNow your google account is connected to Secured Signing account, you can process your signing.