Attached to this article are 3 documents that are required to complete an SSO implementation.
The order the documents should be used in is:
- Daptiv SSO Exploration Worksheet (discovery worksheet)
- Daptiv SSO Integration (technical document + FAQ)
- Daptiv SSO ADFS 2.0 Guide (only to be used if you have ADFS)
SSO and AD integration/sync are completely separate things. SSO is what allows users to be authenticated to the system without having to provide a Daptiv password. AD integration uses Daptiv Connect to automatically sync users from their Active Directory system to Daptiv. The former is free, and the latter is a paid service.
The Utilities (ProjectTransit syncing with Microsoft Project, Outlook Integration, and DeskDocs) can be used with SSO, but will require the Daptiv password; they do not support SSO capabilities.
By default, SSO is not designed to work with links or notifications. If a user is not logged in to Daptiv, and clicks a link or an email notification, they are taken to the Daptiv login page. This is correct behavior; the user must first log in with their internal SSO link, before clicking notifications, if they want to go straight through to the item. However, links and notifications can be configured to authenticate with SSO by disabling the native login page. Users will be forced to use SSO only for authentication. If you are interested in this, please contact Daptiv Support.
If SSO is enabled for an enterprise, it is possible to force users to sign in via SSO. If you would like to configure this, please contact Daptiv Support to have the native login page https://login.daptiv.com disabled for your enterprise. The switch is instantaneous and will require no downtime. If users try to login via the native page (https://login.daptiv.com) when SSO only is enabled, the user will experience an invalid credentials error.