Home

 

Supporting Confluence authenticated feeds

Add entries to the proxy-communities-config.tpl file to allow cookies to be sent to the Confluence server.

To edit configuration files, use wsadmin. See Start the wsadmin client for information about how to start the wsadmin command-line tool.


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 do the following:

  1. 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 Lotus Connections features.

  2. If Confluence is not hosted on IBM WebSphere Application Server, 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:

    1. In the WAS admin console, select Servers in the navigation pane, and then select Application servers.

    2. Select a server.

    3. Expand Web Container Settings under Container Settings and click Web container.

    4. Click Session management.

    5. Click Enable Cookies.

    6. Enter a different cookie name in the Cookie name field, for example, LCSESSIONID.

    7. Click OK, click Save, and then click Save again.

  3. Use wsadmin to access the Lotus Connections configuration files:

  4. Check out the proxy configuration file...

    • If the proxy-communities-config.tpl file does not already exist and you want to check it out and customize it:

      1. Check out the file...

        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 while you make changes to them.

        • <cell-name> is the name of the WebSphere Application Server cell hosting the Lotus Connections feature. This argument is required even in stand-alone deployments. This argument is also case-sensitive, so type it with care.

      2. Copy the proxy-config.tpl file and rename it as proxy-communities-config.tpl.

    • If the proxy-communities-config.tpl file already exists:

      CommunitiesConfigService.checkOutProxyConfig("<working-directory>", "<cell-name>")

  5. Open the proxy-communities-config.tpl file in a text editor.

  6. 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>
      

  7. After making your changes, save and close the proxy-communities-config.tpl file.

  8. To check in the proxy-communities-config.tpl file...

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

  9. To exit wsadmin, type

    exit

    at the prompt.

  10. Restart the WebSphere Application Server or servers.


IBM Lotus Connections Connector for Confluence

 

Related tasks

Change common configuration property values


+

Search Tips   |   Advanced Search