cancel
Showing results for 
Search instead for 
Did you mean: 

user locks after 2 attempt

0 Kudos

Hello All,

we are facing issue from user saying they are getting locked after 2 attempt in BW system.

we have checked profile parameter login/fails_to_user_lock=3

Also we tried from our end, it locks after 3 attempt only but for client they gets locked after 2 attempt.


pl. help.


BR,

Chandresh.

Accepted Solutions (0)

Answers (7)

Answers (7)

0 Kudos

we increased login/fails_to_user_lock value to maximum level.


Thanks,

C.

Johan_sapbasis
Active Contributor
0 Kudos

Hi Chandres,

Please mark thread as closed.

J

Johan_sapbasis
Active Contributor
0 Kudos

Hi,

As S Sriram has said check sm19/s20 logs settings if enabled.

Alternatively also check SUIM report why user locked.

Kind Regards,

Johan

Sriram2009
Active Contributor
0 Kudos

Hi Chandresh

You can try-out any one of the test user id type the two or three times wrong password and then check the locks in SM21 log.

BR

SS

0 Kudos

Hello Sriram,

we tried using test id, my login id in system and its gets locked after 3 attempt only.

BR,

Chandresh.

Sriram2009
Active Contributor
0 Kudos

Hi Chandresh

You can enable the user audit log by using the transaction code SM19 / SM20 to find the number of wrong password enter in your BW system. you can refer the SCN link

BR

SS

0 Kudos

User is accessing BW system using AO(Analysis Office).

is there any parameter needs to be set?

BR,

C.

Former Member
0 Kudos

Hello Chandresh,

Please check the value of parameter login/fails_to_user_lock in both DEFAULT.PFL and instance profile. If there are different values for same parameter in those files, they can override each other; possibly DEFAULT.PFL would overrun intance profile.

I know it sounds weird but it's a possibility and sometimes happens.

Regards,

Serhat

former_member182657
Active Contributor
0 Kudos

Hi,

It's really strange behavior,i supposed your issue has already been resolved after following recommendations from

login/fails_to_session_end & login/fails_to_user_lock.

A possible reason of getting locked down could be user web access.Please confirm ?

Thanks,

Former Member
0 Kudos

Hi,

Sometimes users describe things that way..

please  check "login/fails_to_session_end"

Former Member
0 Kudos

they gets locked after 2 attempt.

That's not possible. The system acts upon the parameter what we've defined. It shows no Partiality

If the parameter "login/fails_to_user_lock" is set to 3; then what is the value of the parameter "login/fails_to_session_end". Is it 2?

regards,

pavan

Matt_Fraser
Active Contributor
0 Kudos

One possibility could be if they are logging in through a web interface that makes multiple connections to the ABAP system. We see this in our SRM system, for instance, and also in Portal connections to our ECC system. What we found is that a small number of incorrect logon attempts via a web interface could lock an account quickly, because each attempt makes two or three "attempts" behind the scenes.

0 Kudos

Hello Pavan,

login/fails_to_session_end is also set to 3


Hello Matt,

user is accessing system through Citrix. is is due to this?

please suggest.