Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

SLDDSUSER Constantly getting locked

Former Member
0 Kudos

Hello Guru's-

Our SLDDSUSER is constantly getting locked out and I'm unable to determine what's locking it. (For the time being, I've created a new user - SLDUSER so the Systems will connect) - I've manually checked all the systems to see if any are using SLDDSUSER for the SLD, but none of them are. The account gets locked several times a day and it's rather frustrating. All the systems are HP-UX / IA64 running with oracle 10g. I've increased the trace logs for the SLD application through visual admin on the SLD, but I'm not getting any details on the failed logins.

I'm currently working with our Unix team to see if we can use wireshark, does anyone know of any other methods?

Thanks,

Jeff

Edited by: Jeffrey Peters on Jan 16, 2009 2:24 PM

5 REPLIES 5

Former Member
0 Kudos

Hai,

Check the below link, might help.....

/thread/1174297 [original link is broken]

Regards,

Yoganand.V

0 Kudos

I've checked that thread, however our security team will not allow us to prevent users from being locked out.

I'm still working on getting wireshark working, so hopefully that will do the trick.

Thanks,

jabella
Employee
Employee
0 Kudos

Jeffrey,

I suggest you check the SLD connection in the Java engine. To do that, execute the Visual Admin in the server, and goto Server -> Services -> SLD Data Supplier. Check the password set there is the correct one.

Regards, Jose

Former Member
0 Kudos

Thanks Jose-

Isn't the SLD Data Supplier in Visual Admin the only place the SLDDSUSER is utilized? If so, I've already checked that as per my first post. If you know of anywhere else it may be stored, please advise.

Thanks,

Former Member
0 Kudos

Check transaction SLDAPICUST on the ABAP side whether SLDDUSER is maintained there?

Also see [SAP Note 1161548|https://service.sap.com/sap/support/notes/1161548] for an improved security feature and check that you have implemented [SAP Note 1244841|https://service.sap.com/sap/support/notes/1244841] which was a side effect.

As a temporary work-around, it might work to disable the secure store method until you have implemented the note.

Cheers,

Julius