details about locking reason

[Former Member]

Hi all,

is there any way to get the information why a user was locked in ABAP system via the connector? I would like to differentiate in IDM if the user was locked by the administrator or because of too many failed login attempts. I can see only the general information if a user is locked or not. But I need the locking reason code.

Thanks in advance

Jörn Kaplan

[Former Member]

Jorn,

Do you have the Security Audit log activated (SM19 / SM20). Basically, if you set the rsau/eable to 1 in the instance profile, you'll activate the audit log. Once configed in SM19, SM20 will show you the information you seek. Every time a user gets locked (among other events) a code will be generated for the lock reason - just as you seek.

Please let me know if this answers your questions.

Cheers,

Tim

[Former Member]

Thanks for your answer. But I think I have to make clear that I need this information in the Identity Store. I know that you can find it in the ABAP system but I need this information to be transferred to IDM.

[Former Member]

Hello Jörn,

I have something like this in my mind:

Implement a class extending the ToSAP class, which is in the DSE.jar . For each needed method (initCustom, exitPass, add-, mod- and deleteEntryCustom) use super.xyz to call the method from the ToSAP.

Then the class needs to write the locking reason to the desired place. I guess it could work somehow like this, but cannot think of an other possibility.

The other possibility would be to file an OSS. But that could take some time, too.

EDIT: Or is it possible to store the locking reason in the system? Then you only need to read that out and store it in the IS using a FromCustom pass after the pass that writes to the ABAP.

Best regards