No need for extended permissions within the identity provider application setup.In the legacy implementation, a Filespace admin needed to confirm new users manually before they could start using the Filespace. No need for a Filespace admin to confirm new users manually.Key improvements over the legacy implementation include the following: LucidLink Single Sign-On (SSO): Legacy to Just-in-Time Migration.LucidLink Single Sign-On (SSO): Assigning Shares to Single Sign-On Users and Groups.LucidLink Single Sign-On (SSO): First-time SSO Login Fundamentals.LucidLink Single Sign-On (SSO): Filespace key Distribution Workflow.LucidLink Single Sign-On (SSO): Azure AD Filespace Certificate & Secret Renewal.LucidLink Single Sign-On (SSO): Integrating with Azure AD.LucidLink Single Sign-On (SSO): Integrating with Okta.LucidLink Single Sign-On (SSO): "Just-in-Time" Provisioning for Users and Groups (this article).The series includes the following articles: This LucidLink Knowledge Base article is the first in a series of seven articles fully describing how to integrate and deploy the new SSO implementation. LucidLink Single Sign-On (SSO) Knowledge Base Articles in this Series ![]() This new version of SSO supports all existing LucidLink 2.0 Filespaces. ![]() We have redesigned our SSO implementation to address some deficiencies in our legacy SSO implementation, making it easier to set up for small and large organizations alike. LucidLink's single sign-on (SSO) mechanism authenticates users using their organization's existing identity provider (currently Okta or Azure AD). Target audience: Filespace administrators Please note, as of Filespace format 2.2 the legacy term “Shares” has been changed to “Permissions.”
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |