Support Confluence authenticated feeds

Support Confluence authenticated feeds
Add entries to proxy-config.tpl to allow cookies to be sent to the Confluence server.

Before starting
To edit configuration files, 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.
Ensure that you only enable access to servers that you trust.

Procedure
To force traffic to be sent over SSL, set the property...
force.conf.comm.enabled property = true

By default, SSL is enabled for all installed IBM Connections applications.
If Confluence is not hosted on the IBM WAS cell, by default the Confluence and WAS servers will have conflicting use of the JSESSIONID session ID cookie.
For each WAS that uses the same virtual host (hostname) as the one that hosts Communities, do the following:

In the WAS admin console, expand...
Servers | Server Types | WebSphere application servers | servername | Container Settings | Web Container Settings | Web container | Session management | Enable cookies

Enter a different cookie name in the Cookie name field, for example, LCSESSIONID.
Click OK, click Save, and then click Save again.

From the dmgr host:
cd $DMGR_PROFILE/bin
./wsadmin.sh -jython
execfile("communitiesAdmin.py")
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, pick the node where the file is stored.

Check out the proxy configuration file using the following commands:

execfile("connectionsConfig.py")
LCConfigService.checkOutProxyConfig("<working-directory>", "<cell-name>")
where:

<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 WAS 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 proxy-config.tpl 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">
        <proxy:actions>
            <proxy:method>GET</proxy:method>
        </proxy:actions>
    </proxy:policy>
After making your changes, save and close proxy-config.tpl.
To check in proxy-config.tpl, use the following command:

LCConfigService.checkInProxyConfig("<working-directory>", "<cell-name>")

To exit the wsadmin client, type exit at the prompt.
Restart the WAS or servers.
Regenerate the plugin-cfg.xml file for the IBM HTTP Server in the WAS admin console. To do so...

Open the WAS admin 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.
Parent topic
IBM Connections Connector for Confluence

Related tasks
Change common configuration property values
Configure the AJAX proxy

+
Search Tips | Advanced Search