Configure J2C Aliases for the moderation proxy service 

Configure J2C Aliases so that community owners can moderate their community Blogs, Forums, and Files applications.

About this task

Moderation actions are performed by a moderation API. Community owners cannot access that API, so IBM Connections handles their moderation requests through a proxy service. The proxy service uses J2C Aliases to pass the requests. Proxy service alias users must be in the global-moderator roles of the appropriate applications, and they must be able to log in to IBM Connections.

By default the proxy service uses the connectionsAdmin J2C Alias provided during installation. That user is mapped to the global-moderator roles for Blogs, Forums, Files, Moderation, and Communities by the installation program, and can log in to IBM Connections. However, you can create different moderation aliases for each of the different supported applications. You can create the following aliases:

The different applications recognize these specific aliases. You can map any users to these aliases, but all users must be in the global-moderator roles of the appropriate application, and they must be able to log into IBM Connections. For example, the moderationBlogsAlias user must be in the global-moderator role for Blogs. See Roles.

The proxy service logs its actions, so if the users (other than the connectionAdmin user) are only used for this purpose, it will make reading the log more clear.


To create moderation aliases and then map them to a global moderator role...

  1. Create a moderation alias:

    1. From the IBM WAS Integrated Solutions Console, expand Security, and then click Global security.

    2. In the Authentication area, expand Java Authentication and Authorization Service, and click J2C authentication data.

    3. Click New.

    4. Name the alias, for example moderationFilesAlias.

    5. Type the name and password of a user for the alias.

    6. Click OK.

  2. Map an alias user to a global-moderator role:

    1. Expand Applications -> Application Types, and then select WebSphere enterprise applications. Find and click the link to the application that you want to configure.

    2. Click Security role to user/group mapping.

    3. Select the check box beside the global-moderator role, and then click Map users.

    4. In the Search String box, type the name of the user to assign to the role, and then click Search. If the user exists in the directory, it is displayed in the Available list.

    5. Select the user or group name from the Available box, and then move it into the Selected column by clicking the right arrow button.

    6. Click OK.

    7. Click OK, and then click Save to save the changes.

  3. Synchronize and restart all your WAS instances.

Parent topic

Configure Moderation

Related reference



Submitted by Elizabeth Hecht on May 25, 2011 3:09:46 PM

Re: Configuring J2C Aliases for the moderation proxy service: ic301

The post install instructions for 3.01. and upgrade instructions mention that if you want to use moderation you need to add a user to the moderator role in the Application security roles. However when moderator wants to view the flagged content they also need to change the widget-admin in Blogs from using the default WAS admin to a user that exists in Profiles as well.