Getting error while upgrading the policy agent 5.0.1.1 in apache webserver 2.2

This topic contains 3 replies, has 2 voices, and was last updated by  gopalsg456 3 months, 3 weeks ago.

  • Author
    Posts
  • #25831
     gopalsg456 
    Participant

    I upgraded openam12 to openam 13.0 successfully.

    But when I try to upgrade the policy agent from 4.0 to 5.0.1.1 in in apache webserver 2.2 I am getting the below error.

    =====================
    2019-05-20 18:00:09 existing config property com.sun.identity.cookie.httponly set to ‘false’

    2019-05-20 18:00:09 existing config property org.forgerock.agents.config.json.url set to ”

    2019-05-20 18:00:09 existing config property org.forgerock.agents.config.notenforced.ext.regex.enable set to ”

    2019-05-20 18:00:09 existing config property org.forgerock.agents.config.notenforced.ipurl set to ”

    2019-05-20 18:00:09 existing config property org.forgerock.agents.pdp.javascript.repost set to ”

    2019-05-20 18:00:09 setting the naming URL list to http://openam.mydomain.com:8080/openam
    2019-05-20 18:00:23 Agent password file /bin/pwd
    2019-05-20 18:00:23 agent password file /bin/pwd opened successfully
    2019-05-20 18:00:25 validating configuration parameters…
    2019-05-20 18:00:25 error validating OpenAM agent configuration
    2019-05-20 18:00:25 installation error
    2019-05-20 18:00:25.141 +0000 ERROR [958db185-37b5-3f45-afe6-3419d7986d18]agent login to http://openam.mydomain.com:8080/openam fails
    2019-05-20 18:00:25 installation exit
    =================================================
    Note: I am able to ping the openam server from apache webserver.

    Please help

    #25832
     Matt Miller 
    Participant

    Policy Agent 5.0.1 requires AM 5.5 or higher.
    See: https://backstage.forgerock.com/knowledge/kb/article/a71812526

    • This reply was modified 4 months ago by  Matt Miller.
    #25834
     gopalsg456 
    Participant

    Thanks Matt😊… I will try with the suitable version and let you know my results.

    #25899
     gopalsg456 
    Participant

    I upgraded the policy agent to 4x Mat and it worked fine without any issues. Many thanks Matt

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.

©2019 ForgeRock - we provide an identity and access platform to secure every online relationship for the enterprise market, educational sector and even entire countries. Click to view our privacy policy and terms of use.

Log in with your credentials

Forgot your details?