on 06-01-2017 1:03 AM
Hi,
I'm having a strange issue... When I set MX_LOCKED =1 the backend account isn't being locked.
Looking through the logic, I can see that the task that determines if an account should be locked, looks at MX_DISABLED. If I set MX_DISABLED AND MX_LOCKED, the account is indeed being locked.
We have custom functionality assigned to MX_DISABLED (expire, lock, remove roles etc), so it's not really an option to use that field instead.
I know this has worked in previous implementations and versions of IdM.
We are on 8 SP4.
Anyone seen similar behaviour and found a way around it?
alright, So - While this annoys me, it seems that this is the way it's supposed to work... MX_DISABLE locks backend account, and MX_LOCKED disables... Oh well, such is life. Resolved it by switching the functionality around in my logic...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
80 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.