Skip to Content

MX_LOCKED does not lock backend accounts

Jun 01, 2017 at 12:03 AM


avatar image


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?

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Best Answer
Henrik Madsen Jun 01, 2017 at 03:48 AM

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...

10 |10000 characters needed characters left characters exceeded