Changes

Single Sign-On

60 bytes removed, 9 December
Expected Behaviour for Role Mapping
<!--Ticket#124791 - SSO to update roles for existing users for a fully federated SSO-->
 
'''''Role Mapping''''' set to '''''Disabled''''' / '''''Create New User''''' on ''No Match'' is '''''OFF'''''
* User will not be created if user does not exist in the SmartSimple instance
* Only existing users in the SmartSimple instance will be able to login and no role/status updates for existing users
<br /> '''''Role Mapping '''''set to '''''Disabled''''' / '''''Create New User''''' on ''No Match'' is '''''ON'''''  
* '''''Define User Roles Through Custom Attribute is OFF''''' User will be created with default new user role / default new user status settings if user does not exist in the SmartSimple instance
* No role/status updates for existing users
<br /> '''''Role Mapping''''' set to '''''Enabled''''' / '''''Create New User''''' on ''No Match'' is '''''OFF'''''
* '''''Create New User''''' on ''No Match'' is '''''OFF''''' User should not be created on the system if not already created when using SSO to access system
Smartstaff
136
edits