Task #507
closed
Added by Petr Michal over 7 years ago.
Updated over 7 years ago.
Description
When user has one account on system, but filled with multiple roles (ldap groups), after any change is provisioning executed for every role.
Expected behavior is that provision will be executed just ones for every account on system.
In frontend it must be fixed on pages for password change and identity accounts.
- Priority changed from High to Normal
Those are two separate things. Provisioning per role and data representation in FE. The first thing is architectonical but has impact on UX. The second one is bug and we have to fix it asap. For that I make a new ticket
- Tracker changed from Defect to Task
- Related to Defect #508: Account reprezentation in FE if user has many roles added
- Status changed from New to Needs feedback
- Assignee changed from Ondřej Kopr to Petr Michal
I have checked the behavior described by you:
- For newly added roles, provisioning is made for each role,
- after the entity update, only one provisioning is made. Even if it has more roles for one system.
Please check if the role does not change mapping for identifier - entity should have only one AccAccount.
I will check mapping.
Ye, my use was that I added roles where multiple provisioning is expected.
Then I did password chnage for that user, where was bug which is already fixed from another ticket.
So issue was just in password change instead of main implementation.
Thanks for explanation.
- Status changed from Needs feedback to Resolved
- % Done changed from 0 to 100
The behavior was fine, other issues related to this one were processed in other tickets.
Closing the ticket.
- Status changed from Resolved to Closed
Also available in: Atom
PDF
