- SAP Community
- Groups
- Interest Groups
- Application Development
- Discussions
- Autosys Id gets locked
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Autosys Id gets locked
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-20-2008 3:43 PM
Hi everyone,
We have Autosys job scheduler in our environment (ECC 6.0). For whatever reason, 'Autosys' Id gets locked in SAP peridocally.
Since there is no manual entry of password for this Id, we are at loss to explain why this ID gets locked peridocally.
Did any of you run into this issue?
Would appreciate any comments.
Regards,
VP
- SAP Managed Tags:
- Security
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-20-2008 3:50 PM
By "locked" do you mean user lock (USR02-UFLAG = 64) or password lock (USR02-UFLAG = 128)?
If you are sure that it does not need a password, then just delete the password ("deactivate password" button in SU01) and move it into a secure user group (S_USER_GRP).
Cheers,
Julius
- SAP Managed Tags:
- Security
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-20-2008 4:08 PM
Julius,
Thanks for the quick response.
It is password lock.
What I meant to say was that there is no manual entry of password, not that we do not need a password. However, it is good to know that this could be a workaround for now.
What are the drawbacks of not having a password if we are able to secure this user using S_USER_GRP as you mentioned?
VP
- SAP Managed Tags:
- Security
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-20-2008 4:18 PM
The draw-back of not having a pasword is that you cannot logon with a password; which is however advisable if the user does not need one.
The advantage is that other folks (or outdated config) cannot password lock the user by logging on incorrectly with it.
What I meant by S_USER_GRP is to protect the user master record itself so that only authorized administartors can change it, or admin-lock it, or recreate an initial password again.
First check to see whether there is another system on a lower release which is attempting to communicate with yours, as the password rules changed. Chances are good that it is the case sensitive password rule causing this.
Otherwise, activate the dynamic configuration filters of the Security Audit Log in transaction SM19 on your servers to log the event Unsuccessfull Login and wait for it to happen again. Then check your SM20N log to see where it is coming from.
Cheers,
Julius
- SAP Managed Tags:
- Security
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-20-2008 9:20 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-20-2008 9:34 PM
Lets wait a while until it happens again, and then let us know
ps: as it could happen again for other reasons... you can also monitor it via static SM19 filters (if setup).
pps: Another option (if you are fast enough) is to use transaction STAD (or STAT) to find the "terminal".
- SAP Managed Tags:
- Security
