-
Type:
Bug
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 5.0.0.0
-
Fix Version/s: None
-
Component/s: Web Agents
-
Labels:
-
Environment:Windows 2016 / IIS 10.0 / Version: 5.0.0-SNAPSHOT, Revision: 235b9c5, Build machine: WIN-6RS21TL5R77, Build date: Nov 8 2017 02:50:54
-
Target Version/s:
It is not possible to install an IIS agent for child application, if one agent instance is installed for parent application/site.
Steps to reproduce
1.) Create a site for IIS, e.g AgentSite (this site will listen on http://example.com/)
2.) Create an application App1 for Agent site (this application will listen on http://example.com/App1)
3.) Install the agent for AgentSite (2.1.1 see bellow)
4.) Install the agent for Application under AgentSite
Expected
You can install agent for children apps and these children will be protected with the installed agent, parent will be protected with the agent instance installed before
Observed
Error, config exist
IIS Site configuration:
========================================================================================================================
id details
========================================================================================================================
Default Web Site
application path:/, pool: DefaultAppPool
1.1.1 virtualDirectory path:/, configuration: C:\inetpub\wwwroot\web.config (*)
AgentSite
application path:/, pool: AgentSite
2.1.1 virtualDirectory path:/, configuration: C:\AgentSite\testingPagesWin\web.config (*)
application path:/App1, pool: AgentSite
2.2.1 virtualDirectory path:/, configuration: C:\AgentSite\Application\web.config (*)
application path:/App1/App2, pool: AgentSite
2.3.1 virtualDirectory path:/, configuration: C:\AgentSite\Application2\web.config (*)
Enter IIS Server Site identification number.
[ q or 'ctrl+c' to exit ]
Site id: 2.2.1
Error: this server site is already configured with OpenAM Web Agent module.
Please try again.
Workaround
1.) Install the agent for the children first and then for the parents.
2.) It is also possible to update IIS Application web.config by hand and copy agent_X instance for new agent + updating required properties, but I am suggesting the option 1
- is related to
-
AMAGENTS-1075 Multiple IIS Sites
- Closed