Just so long as your Prospect user ID, i.e. Without setting up any integration or using administrative privilege, any user can start using SSO. For more information please visit this page. password length or even two-factor authentication), etc. And, as an IT administrator, you have greater control in being able to centrally block users from applications, centrally enforce security standards and best practice (e.g. The benefits are of course less clicks and less typing of passwords, but with less passwords to manage, users are more likely to use stronger passwords and change them more regularly. Through strong encryption and tight security standards, we can be sure that Microsoft logged you in, and on that basis we log you into our application without asking for another password. Essentially, in the case of Azure AD SSO, we trust Microsoft to validate your identity on our behalf. Single Sign On (SSO) allows you to log in to multiple applications. To start using integrated logins on a personal level, you don't need any more than an account on each, but to set up full integration for all your users, you'll also need to be an Administrator for both products. If you don't use Office 365, you can create an Azure AD Tenant by visiting this link If you use Office 365 then you already have an Azure AD Account If your organisation hasn't signed up yet, then sign up for free here If your organisation has a Prospect subscription but you don't have a login, contact your Administrator All you need is an Azure AD subscription.which sounds a bit complicated.but you've probably already got one as it comes bundled in with Office 365 (or can be set up separately). Simplify the log in flow for your users, whilst increasing security and control by implementing Single Sign On (SSO) with Azure AD (AAD).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |