Full Qualified Domain Name (FQDN) doesn't work when try to login in portal

[Former Member]

I Install a NetWeaver 7.0 with BI JAVA

SP15

I try to login in portal with 3 diferent ways:

1) - With IP I can login but I can't see any objects;

2) - With only hostname without domain I can login I see objects, every thing works fine.

3) - With FQDN I can't login. I don't get any error. It refreh again the login page, and ask again the user and pass.

I could always login with only the hostname, but the problem is that all links are generated with FQDN.

This is the error that is in Security.log:

#1.5 #0050568F3C72005B0000026A00000B000004555928D4E3E7#1219741332358#/System/Security/Audit#sap.com/irj#com.sap.security.core.util.SecurityAudit#SAP_BASIS#5575##slmqlsbi1.lm.pt_BIP_3925050#Guest#abd12770734d11dd889a0050568f3c72#SAPEngine_Application_Thread[impl:3]_4##0#0#Info#1#com.sap.security.core.util.SecurityAudit#Plain###SAP_BASIS | LOGIN.OK | USER.R3_DATASOURCE.SAP_BASIS | | IP Address=[192.168.4.4]#

#1.5 #0050568F3C72005F000014BF00000B000004555928F31063#1219741334343#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#5576##n/a##28fb55a072da11dd9b760050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests# #1.5 #0050568F3C720075000005CA00000B00000455592934EDEE#1219741338656#/System/Security/Authentication#sap.com/irj#com.sap.engine.services.security.authentication.logincontext#SAP_BASIS#5577##slmqlsbi1.lm.pt_BIP_3925050#Guest#af8afb20734d11ddc4230050568f3c72#SAPEngine_Application_Thread[impl:3]_33##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.OK User: SAP_BASIS Authentication Stack: ticket Login Module Flag Initialize Login Commit Abort Details 1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule SUFFICIENT ok false false 2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule REQUISITE ok true true 3. com.sap.security.core.server.jaas.CreateTicketLoginModule OPTIONAL ok true true Central Checks true # #1.5 #0050568F3C720075000005CB00000B00000455592934F1FE#1219741338656#/System/Security/Audit#sap.com/irj#com.sap.security.core.util.SecurityAudit#SAP_BASIS#5577##slmqlsbi1.lm.pt_BIP_3925050#Guest#af8afb20734d11ddc4230050568f3c72#SAPEngine_Application_Thread[impl:3]_33##0#0#Info#1#com.sap.security.core.util.SecurityAudit#Plain###SAP_BASIS | LOGIN.OK | USER.R3_DATASOURCE.SAP_BASIS | | IP Address=[192.168.4.4]# #1.5 #0050568F3C72005F000014C000000B0000045559298BC213#1219741344346#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#5578##n/a##28fb55a072da11dd9b760050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests# #1.5 #0050568F3C72005F000014C100000B00000455592A2466F9#1219741354348#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#5579##n/a##28fb55a072da11dd9b760050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests#

Can you tell me why I can't login in portal with FQDN?

Best regards,

Filipe Sacadura Botte

Edited by: Filipe Sacadura Botte on Aug 26, 2008 11:03 AM

[Former Member]

The problem is that the domain only have 2 digits and this is not possible, it must have more than 3 or 3.

aa.aa (not possible)

aaa.aa (possible)

[Former Member]

Hi Filipe

Please check whether the host file entry for the FQDN is properly maintained.

Also request you to check the default trace int the Java home directory and std_server0.out file in work directory and if you find any error there please let us know.

Regards

Kaleem

[Former Member]

Dear,

check your FQDN entires is maintained properly.

1.icm/host_name_full parameter set to FQDN

2. In portal page, system config.>system landscape>sap_bw> set ITS host name & WAS host name to FQDN name.

[Former Member]

I have all that configured:

File host:

IP host FQDN

File Security.log

#1.5 #0050568F3C72006D000002C700000E580004556D63F80A15#1219828223462#/System/Security/Audit#sap.com/irj#com.sap.security.core.util.SecurityAudit#J2EE_ADMIN#7764##slmqlsbi1_BIP_3925050#Guest#fae2cba0741711dd91c40050568f3c72#SAPEngine_Application_Thread[impl:3]_1##0#0#Info#1#com.sap.security.core.util.SecurityAudit#Plain###J2EE_ADMIN | LOGIN.OK | USER.R3_DATASOURCE.J2EE_ADMIN | | IP Address=[10.131.224.205]#

#1.5 #0050568F3C72006300001DB400000E580004556D64287F5C#1219828226635#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#7765##n/a##e398c660736e11dda4c50050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests# #1.5 #0050568F3C72006300001DB500000E580004556D64C1226C#1219828236635#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#7766##n/a##e398c660736e11dda4c50050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests# #1.5 #0050568F3C720076000000E400000E580004556D64CDE4A3#1219828237479#/System/Security/Authentication#sap.com/irj#com.sap.engine.services.security.authentication.logincontext#J2EE_ADMIN#7767##slmqlsbi1_BIP_3925050#Guest#034bcf80741811dd8c500050568f3c72#SAPEngine_Application_Thread[impl:3]_36##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.OK User: J2EE_ADMIN Authentication Stack: ticket Login Module Flag Initialize Login Commit Abort Details 1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule SUFFICIENT ok false false 2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule REQUISITE ok true true 3. com.sap.security.core.server.jaas.CreateTicketLoginModule OPTIONAL ok true true Central Checks true # #1.5 #0050568F3C720076000000E500000E580004556D64CDE766#1219828237479#/System/Security/Audit#sap.com/irj#com.sap.security.core.util.SecurityAudit#J2EE_ADMIN#7767##slmqlsbi1_BIP_3925050#Guest#034bcf80741811dd8c500050568f3c72#SAPEngine_Application_Thread[impl:3]_36##0#0#Info#1#com.sap.security.core.util.SecurityAudit#Plain###J2EE_ADMIN | LOGIN.OK | USER.R3_DATASOURCE.J2EE_ADMIN | | IP Address=[10.131.227.30]# #1.5 #0050568F3C720078000000D100000E580004556D653EF26F#1219828244886#/System/Security/Authentication#sap.com/irj#com.sap.engine.services.security.authentication.logincontext#J2EE_ADMIN#7768##slmqlsbi1_BIP_3925050#Guest#07b14c80741811dd94540050568f3c72#SAPEngine_Application_Thread[impl:3]_18##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.OK User: J2EE_ADMIN Authentication Stack: ticket Login Module Flag Initialize Login Commit Abort Details 1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule SUFFICIENT ok false false 2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule REQUISITE ok true true 3. com.sap.security.core.server.jaas.CreateTicketLoginModule OPTIONAL ok true true Central Checks true # #1.5 #0050568F3C720078000000D200000E580004556D653EF5CD#1219828244886#/System/Security/Audit#sap.com/irj#com.sap.security.core.util.SecurityAudit#J2EE_ADMIN#7768##slmqlsbi1_BIP_3925050#Guest#07b14c80741811dd94540050568f3c72#SAPEngine_Application_Thread[impl:3]_18##0#0#Info#1#com.sap.security.core.util.SecurityAudit#Plain###J2EE_ADMIN | LOGIN.OK | USER.R3_DATASOURCE.J2EE_ADMIN | | IP Address=[10.131.227.30]# #1.5 #0050568F3C72006300001DB600000E580004556D6559DF5B#1219828246652#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#7769##n/a##e398c660736e11dda4c50050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests# #1.5 #0050568F3C72007A0000016C00000E580004556D659A15BF#1219828250856#/System/Security/Authentication#sap.com/irj#com.sap.engine.services.security.authentication.logincontext#J2EE_ADMIN#7770##slmqlsbi1_BIP_3925050#Guest#0b36a2b0741811dd8eeb0050568f3c72#SAPEngine_Application_Thread[impl:3]_22##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.OK User: J2EE_ADMIN Authentication Stack: ticket Login Module Flag Initialize Login Commit Abort Details 1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule SUFFICIENT ok false false 2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule REQUISITE ok true true 3. com.sap.security.core.server.jaas.CreateTicketLoginModule OPTIONAL ok true true Central Checks true # #1.5 #0050568F3C72007A0000016D00000E580004556D659A18AF#1219828250856#/System/Security/Audit#sap.com/irj#com.sap.security.core.util.SecurityAudit#J2EE_ADMIN#7770##slmqlsbi1_BIP_3925050#Guest#0b36a2b0741811dd8eeb0050568f3c72#SAPEngine_Application_Thread[impl:3]_22##0#0#Info#1#com.sap.security.core.util.SecurityAudit#Plain###J2EE_ADMIN | LOGIN.OK | USER.R3_DATASOURCE.J2EE_ADMIN | | IP Address=[10.131.227.30]# #1.5 #0050568F3C72006300001DB700000E580004556D65F28856#1219828256653#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#7771##n/a##e398c660736e11dda4c50050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests#

#1.5 #0050568F3C72006300001DB800000E580004556D668B39B0#1219828266654#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#7772##n/a##e398c660736e11dda4c50050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests# #1.5 #0050568F3C72006300001DB900000E580004556D6723CECE#1219828276655#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#7773##n/a##e398c660736e11dda4c50050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests# #1.5 #0050568F3C72006300001DBA00000E580004556D67BC791B#1219828286656#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#7774##n/a##e398c660736e11dda4c50050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests# #1.5 #0050568F3C72006300001DBB00000E580004556D685513CD#1219828296657#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#7775##n/a##e398c660736e11dda4c50050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests#

#1.5 #0050568F3C72006300001DBC00000E580004556D68EDBF58#1219828306673#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#7776##n/a##e398c660736e11dda4c50050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests# #1.5 #0050568F3C72006300001DBD00000E580004556D69865801#1219828316674#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#7777##n/a##e398c660736e11dda4c50050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests#

files std_server0.out and defaultTrace don't have any error.