cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Connection to Monitored system isn't possible due authentication problem

Go to solution
former_member956918
Explorer

on ‎03-26-2013 10:40 AM

0 Kudos

Hello Community,

I've got a problem with my Solman 7.1.
My SolMan is unable to connect to the managed java systems. In configuration Step 4 of "Managed Systems Configuriation" under "Java Parameter" I'm not able to logon to the desired system.

It's no permission problem.

The error message is: Logintest failed for User **** Detail : No server is running (Cause, Error during authentication)

So i take a look in the authentication traces from my monitored system.

The user tries to get a LogonTicket, but it's reject because the field host in the HTTP-header is NULL.

08:05:37:922PathGuest...cated_Application_Thread]....loginmodule.ticket.getMappedUser()Exiting method with [Ljava.lang.Object;@5ce85cbc
08:05:37:922DebugGuest...cated_Application_Thread]...y.authentication.loginmodule.ticketFor user [SPML_USER] found $usermapping$:SAP_CLIENT attribute value [null]
08:05:37:923DebugGuest...cated_Application_Thread]...y.authentication.loginmodule.ticketClient is null.
08:05:37:924PathGuest...cated_Application_Thread]...n.loginmodule.ticket.createTicket()Entering method with ({system=DP5, validityMin=0, client=000, inclcert=0, user=SPML_USER, cert=Version: 1
Serial number: 0
Signature algorithm: DSAwithSHA1 (1.2.840.10040.4.3)
Issuer: OU=J2EE,CN=DP5
Valid not before: Sat Nov 10 13:14:13 CET 2012
      not after: Wed Nov 10 13:14:13 CET 2032
Subject: OU=J2EE,CN=DP5
DSA public key (1024 bits):
y: 1ed6e6ab078a6fb2ee442e05389c785a2e47fb8e654fb839d62f400172b2e6936df83d10e4971ca2f6beb88cf723c5852b9e9ed264274d52bd65c2b2fe6d2ac639b9779ca78126864d40b00e45038ad36a13a78e8e949f0c37db1e39b07cb2daadb104384d4f216799728ad8972f8279803bf61d747be0af355a4df4727bd78b
p: 827dd49ca2056984e98371b1340d5d71839285b25acaa382d7ac386e9440843f0a467aa875a8c1ca3b70ba6a970712f6b199ed3eec5313f3940a67bbd69f38722961ab023d17a1333c52235d9fb7d10e95e3a55ef9b04fc7c920c572da7ac3d50f240dbb8e54da9ebb702111c53582e535852e9f593979b33250c88683961917
q: fa5079dafa3f3ab1e80a6df5bd16f224d8f8d71b
g: 4fbdf52e3304f051c17ca55c9381b5c17d4c205076853450cfd9fc72b2e1b2b16fa01048b8ff17e7a90ae1e018053e34d9d561df714cc8dc92b151b5df6659706b5e57c319a2d6583b7d32d2e9e1f1663eaaac460dcd4e677036f7f9be0b2e16a05d695d5b8113a903cb3863561abd364a5d6c156617fa10a32099e1d2347713

Certificate Fingerprint (MD5)  : 1C:90:88:8F:5E:A1:9F:5A:2E:1F:FA:DE:81:C0:1D:9F
Certificate Fingerprint (SHA-1): 7B:9F:83:51:1A:AD:79:A0:51:EF:6F:E5:CE:AF:87:B3:AC:EA:9F:BC

, ume.logon.httponlycookie=true, alias=SAPLogonTicketKeypair, sap.security.auth.configuration.name=service.naming, ume.logon.security.enforce_secure_cookie=false, keystore=TicketKeystore, validity=8, key=DSA private key (1024 bits):
x: 66b73c023974808e8ad836d51dee7d7f68170511
p: 827dd49ca2056984e98371b1340d5d71839285b25acaa382d7ac386e9440843f0a467aa875a8c1ca3b70ba6a970712f6b199ed3eec5313f3940a67bbd69f38722961ab023d17a1333c52235d9fb7d10e95e3a55ef9b04fc7c920c572da7ac3d50f240dbb8e54da9ebb702111c53582e535852e9f593979b33250c88683961917
q: fa5079dafa3f3ab1e80a6df5bd16f224d8f8d71b
g: 4fbdf52e3304f051c17ca55c9381b5c17d4c205076853450cfd9fc72b2e1b2b16fa01048b8ff17e7a90ae1e018053e34d9d561df714cc8dc92b151b5df6659706b5e57c319a2d6583b7d32d2e9e1f1663eaaac460dcd4e677036f7f9be0b2e16a05d695d5b8113a903cb3863561abd364a5d6c156617fa10a32099e1d2347713
, password=, mappeduser=SPML_USER})
08:05:37:924DebugGuest...cated_Application_Thread]...y.authentication.loginmodule.ticketUser set in SAP Logon Ticket is [SPML_USER]. Authentication stack: [service.naming].
08:05:37:925DebugGuest...cated_Application_Thread]...y.authentication.loginmodule.ticketMapped user [SPML_USER] set in SAP Logon Ticket. The authenticated user is [SPML_USER]. Authentication stack: [service.naming].
08:05:37:925DebugGuest...cated_Application_Thread]...y.authentication.loginmodule.ticketMeasured date using new Calendar.getInstance (): java.util.GregorianCalendar[time=1364281537925,areFieldsSet=true,areAllFieldsSet=true,lenient=true,zone=java.util.SimpleTimeZone[id=GMT,offset=0,dstSavings=3600000,useDaylight=false,startYear=0,startMode=0,startMonth=0,startDay=0,startDayOfWeek=0,startTime=0,startTimeMode=0,endMode=0,endMonth=0,endDay=0,endDayOfWeek=0,endTime=0,endTimeMode=0],firstDayOfWeek=2,minimalDaysInFirstWeek=4,ERA=1,YEAR=2013,MONTH=2,WEEK_OF_YEAR=13,WEEK_OF_MONTH=4,DAY_OF_MONTH=26,DAY_OF_YEAR=85,DAY_OF_WEEK=3,DAY_OF_WEEK_IN_MONTH=4,AM_PM=0,HOUR=7,HOUR_OF_DAY=7,MINUTE=5,SECOND=37,MILLISECOND=925,ZONE_OFFSET=0,DST_OFFSET=0]
08:05:37:926DebugGuest...cated_Application_Thread]...y.authentication.loginmodule.ticketCreated utcCreationTime string is 201303260705
08:05:37:928PathGuest...cated_Application_Thread]...n.loginmodule.ticket.createTicket()Exiting method
08:05:37:929InfoGuest...cated_Application_Thread]...dule.ticket.CreateTicketLoginModuleNew SAP Logon Ticket for user [SPML_USER] has been created. Authentication stack: [service.naming].
08:05:37:930DebugGuest...cated_Application_Thread]...dule.ticket.CreateTicketLoginModuleThe created ticket is:
[Ticket [initialized]
  Ticket Version  = 0
  Ticket Codepage =  (Encoding=1100)
  User = SPML_USER
  Issuing System ID     = DP5
  Issuing System Client = 000
  Creation Time = 201303260705
  Valid Time    = 8 h 0 min
  Signature (length=260 bytes)
  InfoUnit id=32, name=portal_user, content=portal:SPML_USER, length=16
  InfoUnit id=136, name=authscheme, content=default, length=7
  InfoUnit id=1, length=9
  InfoUnit id=2, length=3
  InfoUnit id=3, length=3
  InfoUnit id=4, length=12
  InfoUnit id=5, length=4
  InfoUnit id=10, length=9
].
Authentication stack: [service.naming].
08:05:37:931DebugGuest...cated_Application_Thread]...dule.ticket.CreateTicketLoginModuleSAP Logon Ticket added to private credentials.
08:05:37:938PathGuest...cated_Application_Thread]...inmodule.ticket.setTicketAsCookie()Entering method with (com.sap.engine.services.security.remoteimpl.login.RemoteLoginContextHelperImpl@3d78a5c3, SPML_USER)
08:05:37:947DebugGuest...cated_Application_Thread]...y.authentication.loginmodule.ticketHttpGetterCallback (http header 'host') returns null. Cannot set cookie.
08:05:37:948PathGuest...cated_Application_Thread]...inmodule.ticket.setTicketAsCookie()Exiting method
08:05:37:950WarningGuest...cated_Application_Thread]...dule.ticket.CreateTicketLoginModuleAuthentication stack: [service.naming].
[EXCEPTION]
javax.security.auth.login.LoginException: Cannot get remote host header field.
at com.sap.security.core.server.jaas.UMEAdapter.setTicketAsCookie(UMEAdapter.java:344)
at com.sap.security.core.server.jaas.CreateTicketLoginModule.setSSOCookie(CreateTicketLoginModule.java:593)
at com.sap.security.core.server.jaas.CreateTicketLoginModule.commit(CreateTicketLoginModule.java:401)
at com.sap.engine.services.security.login.LoginModuleLoggingWrapperImpl.commit(LoginModuleLoggingWrapperImpl.java:284)
at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:77)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:295)
at com.sap.engine.services.security.remoteimpl.login.RemoteLoginContextHelperImpl.login(RemoteLoginContextHelperImpl.java:145)
at com.sap.engine.services.security.remoteimpl.login.RemoteLoginContextHelperImplp4_Skel.dispatch(RemoteLoginContextHelperImplp4_Skel.java:64)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:462)
at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:72)
at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:43)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:999)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:59)
at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
08:05:37:952PathGuest...cated_Application_Thread]...et.CreateTicketLoginModule.commit()Exiting method with <null>
08:05:37:953DebugGuest...cated_Application_Thread]...ecurity.authentication.logincontextLogin failed!
[EXCEPTION]
java.security.PrivilegedActionException: com.sap.engine.services.security.exceptions.BaseLoginException: Authentication failed.
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:295)
at com.sap.engine.services.security.remoteimpl.login.RemoteLoginContextHelperImpl.login(RemoteLoginContextHelperImpl.java:145)
at com.sap.engine.services.security.remoteimpl.login.RemoteLoginContextHelperImplp4_Skel.dispatch(RemoteLoginContextHelperImplp4_Skel.java:64)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:462)
at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:72)
at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:43)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:999)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:59)
at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Authentication failed.
at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:121)
... 14 more
Caused by: javax.security.auth.login.LoginException: Cannot get remote host header field.
at com.sap.security.core.server.jaas.UMEAdapter.setTicketAsCookie(UMEAdapter.java:344)
at com.sap.security.core.server.jaas.CreateTicketLoginModule.setSSOCookie(CreateTicketLoginModule.java:593)
at com.sap.security.core.server.jaas.CreateTicketLoginModule.commit(CreateTicketLoginModule.java:401)
at com.sap.engine.services.security.login.LoginModuleLoggingWrapperImpl.commit(LoginModuleLoggingWrapperImpl.java:284)
at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:77)
... 14 more

Best regards

Bastian Gschrey

Show replies
Show replies
Answer

Accepted Solutions (1)

Accepted Solutions (1)

former_member956918
Explorer
‎04-16-2013 7:38 AM
0 Kudos

Anyone else with this Problem?

I' still getting the error "HttpGetterCallback (http header 'host') returns null. Cannot set cookie."

Any suggestions?

Best Regards

Bastian Gschrey

Show replies
Show replies
former_member956918
Explorer
‎04-16-2013 10:15 AM
0 Kudos

Okay I solved the problem.

in the Ticket authentication stack, I changed CreateTicketLoginModule from SUFFICIENT to OPTIONAL. Now it's working

Answers (0)

Ask a Question