Difference between revisions of "Enforce Single Sign-On by Disabling Direct Login Access - Why?"
From SmartWiki
| Line 1: | Line 1: | ||
{{WhyHeader}} | {{WhyHeader}} | ||
| + | With this feature enabled, global administrators can restrict specific users (by role) from logging into their SmartSimple instance via the standard login page. For organizations that have SSO requirements this feature ensures that this requirement is adhered to. | ||
| − | This feature grants global administrators the ability to enforce the use of [[Sso|SSO]] (Single Sign On) on a role by role basis. With '''Enforce SSO''' enabled, users assigned specific roles will not be able to login through the login page. System access is only available thorough SSO. | + | <!-- This feature grants global administrators the ability to enforce the use of [[Sso|SSO]] (Single Sign On) on a role by role basis. With '''Enforce SSO''' enabled, users assigned specific roles will not be able to login through the login page. System access is only available thorough SSO. --> |
| − | |||
| − | |||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
Revision as of 16:59, 8 March 2016
|
This article will explain why this feature is a benefit to your organization. |
With this feature enabled, global administrators can restrict specific users (by role) from logging into their SmartSimple instance via the standard login page. For organizations that have SSO requirements this feature ensures that this requirement is adhered to.
|
Click here for an overview on setting up this feature. |
