Smartstaff
1,390
edits
Changes
→Expected Behaviour for Role Mapping
'''Scenerio 3: ''User Access Mapping'' set to ''Enabled'' / ''Create New User'' on ''No Match'' is ''OFF'' / No Assertion defined '''
* User will should not be created on the system if user not already created when using SSO to access system* User should see no role updates if accessing with existing account that does not exist have of the roles defined in the SmartSimple instanceRoles controlled by Assertion* No User should see role updates if accessing SSO with existing usersaccount that does have roles defined in the Roles controlled by Assertion. The change will be based on the Mappings defined.
* User will be created with roles defined in the assertion if user does not exist in the SmartSimple instance and assertion roles are defined in the ''User Roles Assertion Mapping''
* User will be created with default new user role / default new user status settings if user does not exists in the SmartSimple instance and if assertion roles do not exist in the ''User Roles Assertion Mapping''
* When Access Mapping is set to Classic Mode and there is no mapping section, role updates will only happen in user creation and the roles in assertion has to have the same user role names matching value with the SmartSimple role names.
==Example of SSO configuration in SmartSimple==