Hi,
I have a very strange problem.
Since a password change of the portal user "Administrator", this account is locked hourly.
OS: W2k8
DB: MSSQL 2k8
SAP: Portal 7.00
User: Administrator (UME)
Portal IP: 192.168.1.1
responses.trc
[May 14, 2014 8:42:02 AM ] - 192.168.1.1 : POST /sld/cimom HTTP/1.1 401 1792 [May 14, 2014 8:42:02 AM ] - 192.168.1.1 : POST /sld/cimom HTTP/1.1 401 1792 [May 14, 2014 8:42:03 AM ] - 192.168.1.1 : POST /sld/cimom HTTP/1.1 401 1792 [May 14, 2014 8:42:03 AM ] - 192.168.1.1 : POST /sld/cimom HTTP/1.1 401 1792 ... [May 14, 2014 9:42:01 AM ] - 192.168.1.1 : POST /sld/cimom HTTP/1.1 401 1792 [May 14, 2014 9:42:01 AM ] - 192.168.1.1 : POST /sld/cimom HTTP/1.1 401 1792 [May 14, 2014 9:42:01 AM ] - 192.168.1.1 : POST /sld/cimom HTTP/1.1 401 1792 [May 14, 2014 9:42:01 AM ] - 192.168.1.1 : POST /sld/cimom HTTP/1.1 401 1792
security.log
#1.5 #00155D11160300650000014F00000F000004F95827B00C09#1400056919503#/System/Security/Audit##com.sap.security.core.util.SecurityAudit#Guest#0#SAP J2EE Engine JTA Transaction : [045ffffffe5ffffff8e00ffffffcefffffffa]#n/a##9d0725f0db4311e3c01800155d111603#SAPEngine_Application_Thread[impl:3]_0##0#0#Warning#1#com.sap.security.core.util.SecurityAudit#Plain###Guest | USERACCOUNT.MODIFY | UACC.PRIVATE_DATASOURCE.un:Administrator | | SET_ATTRIBUTE: lastfailedlogon=[{0001400053321593} -> {0001400056919450}], SET_ATTRIBUTE: PRINCIPAL_MODIFY_DATE=[{0001400053367448} -> {0001400056919483}], SET_ATTRIBUTE: failedlogonattempts=[{0} -> {1}], SET_ATTRIBUTE: LAST_MODIFIED_BY=[{} -> {Guest}]#
#1.5 #00155D11160300650000015000000F000004F95827B03D0C#1400056919521#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#Guest#0##n/a##9d0725f0db4311e3c01800155d111603#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.FAILED
User: N/A
Authentication Stack: sap.com/com.sap.lcr*sld
Login Module Flag Initialize Login Commit Abort Details
1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule SUFFICIENT ok false true
2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule REQUISITE ok exception true Authentication did not succeed.
3. com.sap.security.core.server.jaas.CreateTicketLoginModule OPTIONAL ok true #
#1.5 #00155D111603006F0000014100000F000004F95827B072ED#1400056919624#/System/Security/Audit##com.sap.security.core.util.SecurityAudit#Guest#0#SAP J2EE Engine JTA Transaction : [045ffffffe5ffffff8e00ffffffcf0]#n/a##9d199c80db4311e38ead00155d111603#SAPEngine_Application_Thread[impl:3]_4##0#0#Warning#1#com.sap.security.core.util.SecurityAudit#Plain###Guest | USERACCOUNT.MODIFY | UACC.PRIVATE_DATASOURCE.un:Administrator | | SET_ATTRIBUTE: LAST_MODIFIED_BY=[{} -> {Guest}], SET_ATTRIBUTE: PRINCIPAL_MODIFY_DATE=[{0001400056919483} -> {0001400056919606}], SET_ATTRIBUTE: lastfailedlogon=[{0001400056919450} -> {0001400056919576}], SET_ATTRIBUTE: failedlogonattempts=[{1} -> {2}]#
#1.5 #00155D111603006F0000014200000F000004F95827B0B823#1400056919654#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#Guest#0##n/a##9d199c80db4311e38ead00155d111603#SAPEngine_Application_Thread[impl:3]_4##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.FAILED
User: N/A
Authentication Stack: sap.com/com.sap.lcr*sld
Login Module Flag Initialize Login Commit Abort Details
1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule SUFFICIENT ok false true
2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule REQUISITE ok exception true Authentication did not succeed.
3. com.sap.security.core.server.jaas.CreateTicketLoginModule OPTIONAL ok true #
#1.5 #00155D111603006A0000019C00000F000004F95827B45A12#1400056920281#/System/Security/Audit##com.sap.security.core.util.SecurityAudit#Guest#0#SAP J2EE Engine JTA Transaction : [045ffffffe5ffffff8e00ffffffcf7]#n/a##9d7ddc90db4311e3b8e200155d111603#SAPEngine_Application_Thread[impl:3]_19##0#0#Warning#1#com.sap.security.core.util.SecurityAudit#Plain###Guest | USERACCOUNT.MODIFY | UACC.PRIVATE_DATASOURCE.un:Administrator | | SET_ATTRIBUTE: PRINCIPAL_MODIFY_DATE=[{0001400056919606} -> {0001400056920260}], SET_ATTRIBUTE: failedlogonattempts=[{2} -> {3}], SET_ATTRIBUTE: LAST_MODIFIED_BY=[{} -> {Guest}], SET_ATTRIBUTE: lastfailedlogon=[{0001400056919576} -> {0001400056920224}]#
#1.5 #00155D111603006A0000019D00000F000004F95827B463A9#1400056920295#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#Guest#0##n/a##9d7ddc90db4311e3b8e200155d111603#SAPEngine_Application_Thread[impl:3]_19##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.FAILED
User: N/A
Authentication Stack: sap.com/com.sap.lcr*sld
Login Module Flag Initialize Login Commit Abort Details
1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule SUFFICIENT ok false true
2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule REQUISITE ok exception true Authentication did not succeed.
3. com.sap.security.core.server.jaas.CreateTicketLoginModule OPTIONAL ok true #
#1.5 #00155D111603005E000000FF00000F000004F95827B4A30A#1400056920413#/System/Security/Audit##com.sap.security.core.util.SecurityAudit#Guest#0#SAP J2EE Engine JTA Transaction : [045ffffffe5ffffff8e00ffffffcfd]#n/a##9d9200d0db4311e3a8cf00155d111603#SAPEngine_Application_Thread[impl:3]_24##0#0#Warning#1#com.sap.security.core.util.SecurityAudit#Plain###Guest | USERACCOUNT.MODIFY | UACC.PRIVATE_DATASOURCE.un:Administrator | | SET_ATTRIBUTE: lastfailedlogon=[{0001400056920224} -> {0001400056920362}], SET_ATTRIBUTE: LAST_MODIFIED_BY=[{} -> {Guest}], SET_ATTRIBUTE: failedlogonattempts=[{3} -> {4}], SET_ATTRIBUTE: PRINCIPAL_MODIFY_DATE=[{0001400056920260} -> {0001400056920395}]#
#1.5 #00155D111603005E0000010000000F000004F95827B4AB21#1400056920424#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#Guest#0##n/a##9d9200d0db4311e3a8cf00155d111603#SAPEngine_Application_Thread[impl:3]_24##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.FAILED
User: N/A
Authentication Stack: sap.com/com.sap.lcr*sld
Login Module Flag Initialize Login Commit Abort Details
1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule SUFFICIENT ok false true
2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule REQUISITE ok exception true Authentication did not succeed.
3. com.sap.security.core.server.jaas.CreateTicketLoginModule OPTIONAL ok true #Normaly that means that the CIM Client is not correctly configured, but the SLD runs over the SolMan (7.1) and in the VisualAdmin > Server > Services > SLD Data Supplier
HTTP Settings and CIM Client Settings are set to the SolMan host and uses the SLDDSUSER to sync the data with the SLD.
Does anyone have an idea what process will connect hourly to the portal where the Administrator is set as user?
I've been searching and reading the now for over two days on the SCN and the web, but I didn't figured it out.
It looks like the portal itselfs want to connect to the local /sld/cimom but the SLD of the portal is still stopped, and also if its running, I get the same error every hour.
Thanks for any advise!
Tobias