Topic
  • 3 replies
  • Latest Post - ‏2013-02-14T20:23:08Z by JMW98
SystemAdmin
SystemAdmin
30895 Posts

Pinned topic Login page back to login page

‏2011-05-26T14:31:56Z |
Hi All,

When I access http://<hostname>:port/wps/myportal/Administration I am getting login page.After I enter the userid and password it again giving me the same login page.I went thru the info center and did wht it says abt cookie in IE.And even SSO is enable properly.And logs are not getting updated at all.

Portal version is 6.1.0.4
Thank you all in advance.

John.
Updated on 2013-02-14T20:23:08Z at 2013-02-14T20:23:08Z by JMW98
  • JMW98
    JMW98
    1097 Posts

    Re: Login page back to login page

    ‏2011-05-27T16:25:12Z  
    Is a domain set for the LTPA token? If so, does it match the way you're addressing the server? i.e. If a domain is set for LTPAToken2, this might work through a web server but not hitting Portal directly.
  • SystemAdmin
    SystemAdmin
    30895 Posts

    Re: Login page back to login page

    ‏2013-02-13T13:35:27Z  
    • JMW98
    • ‏2011-05-27T16:25:12Z
    Is a domain set for the LTPA token? If so, does it match the way you're addressing the server? i.e. If a domain is set for LTPAToken2, this might work through a web server but not hitting Portal directly.
    Hi I am facing the similar issue with IBM web sphere admin console login. With the domain name, login page redirected to login page again. When i am using system name,ip and local host it is working fine. I faced issue with domain name only.

    How can i resolve this issue
  • JMW98
    JMW98
    1097 Posts

    Re: Login page back to login page

    ‏2013-02-14T20:23:08Z  
    Hi I am facing the similar issue with IBM web sphere admin console login. With the domain name, login page redirected to login page again. When i am using system name,ip and local host it is working fine. I faced issue with domain name only.

    How can i resolve this issue
    Take a Fiddler trace & check to see if the LTPAToken2 is set on the response. If so, is it presented on subsequent requests? If not, work backward to figure out why. What is the "Set-Cookie" header that sets the LTPA token. Does it match subsequent requests?