Supporting Confluence authenticated feedsAdded by IBM | Edited by IBM on March 15, 2012 | Version 3 (Show original)
|Add entries to the proxy-config.tpl file to allow cookies to be sent to the Confluence server.
Add entries to the proxy-config.tpl
file to allow cookies to be sent to the Confluence server.
Before you begin
To edit configuration files, you must use the wsadmin client. See Starting the wsadmin client
for information about how to start the wsadmin command-line tool.
About this task
Displaying Confluence feeds in a restricted community requires users to log in to the Confluence server using basic authentication and the propagation of cookies. By default, Communities does not allow cookies to be sent to third-party servers. To enable this functionality, you need to perform the following steps.
Ensure that you only enable access to servers that you trust. For more information, see Configuring the Ajax proxy
Parent topic: IBM Connections Connector for Confluence
Changing common configuration property values
Configuring the AJAX proxy
- To force traffic to be sent over SSL, set the force.conf.comm.enabled property to true. For more information about how to do this, see Changing common configuration property values.
By default, SSL is enabled for all installed IBM Connections applications.
- If Confluence is not hosted on the IBM WebSphere® Application Server cell, by default the Confluence and WebSphere Application Server servers will have conflicting use of the JSESSIONID session ID cookie. For each WebSphere Application Server that uses the same virtual host (hostname) as the one that hosts Communities, do the following:
- In the WebSphere Application Server Integrated Solutions Console, expand Servers in the navigation pane, and then select Server Types -> WebSphere application servers.
- Select a server.
- Expand Web Container Settings under Container Settings, and then select Web container.
- Click Session management.
- Select Enable cookies.
- Enter a different cookie name in the Cookie name field, for example, LCSESSIONID.
- Click OK, click Save, and then click Save again.
- Start the wsadmin client from the following directory of the system on which you installed the Deployment Manager:
is the WebSphere
Application Server installation directory and <dm_profile_root>
is the Deployment Manager profile directory, typically dmgr01.
You must start the client from this directory or subsequent commands that you enter do not execute correctly.
- Start the Communities Jython script interpreter using the following command:
If prompted to specify a service to connect to, type 1 to pick the first node in the list. Most commands can run on any node. If the command writes or reads information to or from a file using a local file path, you must pick the node where the file is stored.
- Check out the proxy configuration file using the following commands:
- <working-directory> is the temporary working directory to which the configuration TPL and XSD files are copied. The files are kept in this working directory while you make changes to them.
- <cell-name> is the name of the WebSphere Application Server cell hosting the IBM Connections application. This argument is required. It is also case-sensitive, so type it with care.
- Navigate to the <working-directory> that you specified in the checkOut command, and then open the proxy-config.tpl file in a text editor.
- Add the following <proxy:policy> entry before the default policy, replacing <confluence.yourcompany.com> with the host name of your Confluence server and replacing <port_number> with the port number for your server. Be sure to insert the custom policy earlier in the code than the default policy.
<proxy:policy url="https://<confluence.yourcompany.com>:<port_number>/*" acf="none" basic-auth-support="true">
- After making your changes, save and close the proxy-config.tpl file.
- To check in the proxy-config.tpl file, use the following command:
- To exit the wsadmin client, type exit at the prompt.
- Restart the WebSphere Application Server or servers.
- Regenerate the plugin-cfg.xml file for the IBM HTTP Server in the WebSphere Application Server Integrated Solutions Console. To do so, complete the following steps:
- Open the WebSphere Application Server Integrated Solutions Console.
- Expand Servers, and then select Server Types -> Web servers.
- Select the check box beside the IBM HTTP Server name. For example: webserver1.
- Click Generate Plug-in to regenerate the plugin-cfg.xml file.
- If necessary, click Propagate Plug-in to copy the plugin-cfg.xml file from the local directory where the Application Server is installed to the remote machine.
- Restart the IBM HTTP Server.