This topic has 2 replies, 2 voices, and was last updated 3 years, 10 months ago by William Hepler.
-
AuthorPosts
-
August 16, 2018 at 6:38 pm #22925
martin.bertrand
ParticipantGreetings, my site (lets call it http://www.example.com), is configured with that URI Prefix:
https://www.example.com:443/amagent.
The property for this setting is com.sun.identity.agents.config.agenturi.prefix
My question is what does it do? If I try
https://www.example.com:443/amagent
in a browser, it is refused by my agent, since I did not configure any policy for “/amagent”, or in the do not enforce list. Should I?OpenAM 13
Web Agent 5-
This topic was modified 3 years, 10 months ago by
martin.bertrand.
August 17, 2018 at 3:46 pm #22932martin.bertrand
ParticipantFYI OpenAM is actually 13.5.0.
August 20, 2018 at 10:04 pm #22945William Hepler
ParticipantReally agent 4.1x should be used with Am 13.5.x.
https://backstage.forgerock.com/knowledge/kb/article/a71812526I’m not finding specifics on the uri amagent other than it’s the Module thats’ loaded for the webcontainer.
The setting com.sun.identity.agents.config.agenturi.prefix mainly is used to allow the agent to understand it’s hostname/protocol/port, there’s a reference in this KB about it’s usage with reguards to overriding protocol, host, and port on the protected server with the web policy agent.
https://backstage.forgerock.com/knowledge/kb/article/a57713800
You may want to start with just SSOonly mode for initial testing then try policy based just to ensure first that the agent is protecting the resource. The resource it’s self can be the default page of your webserver, such as the “it works” page on apache.
-
This topic was modified 3 years, 10 months ago by
-
AuthorPosts
You must be logged in to reply to this topic.