WebSphere Application Server & Liberty

 View Only
  • 1.  Validation of LTPA Tokens Failed issue in Websphere

    Posted Tue May 24, 2016 06:22 AM

    Hi All,

    We are currently upgrading WAS from v6.1 to v8.5.5.7 on AIX OS. Both versions of WAS are parallely residing on the same physical server.

    Both environments have separate dedicated file systems and users to access it.

    Cell name of old environment( WAS 6.1): ABC
    Cell name of new environment(WAS 8.5.5.7): XYZ

    While starting the DMGR in the new environment, we are getting the following error:


    HMGR0149E: An attempt to open a connection to core group DefaultCoreGroup has been rejected. The sending process has a name of ABC\hostname\nodeagent and an IP address of /IP Address of the same physical server . Global security in the local process is Enabled. Global security in the sending process is Enabled. The exception is com.ibm.websphere. security.auth.WSLoginFailedException: Validation of L TPA token failed due to invalid keys or token type. at com.ibm.ws.security.ltpa.LTPAServerObject.validateToken (LTPAServerObject.java:1180) at com.ibm.ws.security.ltpa.LTPAServerObject.validateToken (LTPAServerObject.java:1097)

    We have tried the following steps:
    1) stop all websphere app servers and node agents in the cell
    2) turn off administrative security in the cell (via the deployment manager)
    3) gen ltpa
    4) restart the DM - without error
    5) perform a manual sync of all nodes (syncNode.sh)
    6) turn on administrative security in the cell (via the deployment manager)
    7) restart the DM - with error
    8) perform a manual sync of all nodes (syncNode.sh)
    9) start node agents in the cell
    10) start the websphere app servers.

    But we still face the same error.In the above error, we can see clearly see that information of old environment (cell name: ABC) is being considered. I'm not sure why it would take the old environment's cell name in the new environment's deployment manager's logs.


    Please help us to resolve this issue. Thanks in advance!!



  • 2.  RE: Validation of LTPA Tokens Failed issue in Websphere

    Posted Tue May 24, 2016 06:48 AM

    Hi Pavan,

      Please review the next technote:

      HMGR0149E is issued even with security disabled in ALL nodes

      http://www-01.ibm.com/support/docview.wss?uid=swg21596835

      Please review your ports in old and new environement.

      At Dmgr, nodeagent and server level the port DCS_UNICAST_ADDRESS

      Hope this helps. Tell us if you need more support

    Regards



  • 3.  RE: Validation of LTPA Tokens Failed issue in Websphere

    Posted Tue May 24, 2016 11:03 AM

    HI Gabriel,

         Thanks for your quick response!! I have checked and found that there was a port conflict with old and new environment for DCS_UNICAST_ADDRESS port and updated the new one with different port. After this, I did the following:

    1. Stop the App server.

    2. Stop the Node Agent.

    3. Did Manual Sync (syncNode)

    4. Restarted the complete Cell (DMGR,Nodeagent and Appserver JVM).

    Now, I am not getting any exceptions related to LTPA validation in Appserver logs. Unfortunately, I am still getting in DMgr logs.

    Please assist me in this regard. Thanks in advance!!

       



  • 4.  RE: Validation of LTPA Tokens Failed issue in Websphere

    Posted Tue May 24, 2016 04:45 PM

    Pavan,

      Have you review the next thread?

      https://www.ibm.com/developerworks/community/forums/html/topic?id=77777777-0000-0000-0000-000013967224

      When you start DMGR 8.5 have you started DMGR 6.1?

      Have you any ffdc log before the error.

    Regards,



  • 5.  RE: Validation of LTPA Tokens Failed issue in Websphere

    Posted Wed May 25, 2016 11:35 AM

    Hi Gabriel,

          There was another port conflict with DMGR of new env and the JVM of old env. I updated the DMGR port of new env and restarted it. Now, We are not getting  LTPA related errors in DMGR and Appserver logs . Thanks for your valuable suggestions.

    Issue is resolved.