...
Coming next release
| Area | Description |
|---|---|
| Invite job | Fix: |
Activate user deactivated by Invite job (RTC- |
When user is removed from invited group in AAD, he is deactivated in User Management. When he is added again to one of invited groups, he is activated, with both (if specified) added roles and existing before deactivation. For now, if user had some roles assigned, for instance via auto-provisioning, then even when he is deactivated by being removed from invited group, he keeps these roles. Then when added to different group and being activated, these roles are still assigned. This mechanism is planned to |
Fix: Activate user deactivated by Invite job (RTC-42719)
When user is removed from invited group in AAD, he is deactivated in User Management. When he is added again to one of invited groups, he is activated, with both (if specified) added roles and existing before deactivation.
For now, if user had some roles assigned, for instance via auto-provisioning, then even when he is deactivated by being removed from invited group, he keeps these roles. Then when added to different group and being activated, these roles are still assigned. This mechanism is planned tobe changed during development of assigning roles to store groups in invite job. |
...
Release 04.07.2024
| Area | Description |
|---|---|
| Invite job | Fix: Users added manually lost access (RTC-42162) Users, who were added to tenant manually, through tenant AAD, imported etc. not invited trough Invite job, can sign in to tenant and have the same access as before changes in job. |
...
Release 02.07.2024
| Area | Description |
|---|---|
| Invite job | Allow users to change username on source AAD (RTC-39861) Users, who are invited to tenant AAD, can change their user name (UPN) on source AAD and login to Cloud modules. Behaviour of invite job is the same as before - users who are added to configured groups on source AAD are updated in tenant AAD or when removed - disabled on tenant. In configuration of job, there can be added groups with auto-provisioning and then users will be invited and added configured permissions. Casing of name of the group in AAD and in configuration must be the same, otherwise job will finish with warnings and users added to that group will not be invited. Performance of job executions is good. |
| Import of stores | Fix: Staging merger aborted when duplicated key on ExternalStoreNo on Store (RTC-41220) ExternalStoreNo is not unique in the identity database, so it does not cause problems during import. |
| User roles | Fix: Not possible to "Expand all" in user management (RTC-34799) 'Expand all' button expands the whole tree of user roles. |
| User role export | Fix for: Blob export when assigning permissions to a role (RTC-23813) When permissions assigned to the role change, only users assigned to this role are exported, not all the users. |
...