Home
Forcing users to log in before they can access a feature
Overview
Change the access levels of members or groups to require them to provide credentials before they can access a Lotus Connections feature.
Do not perform this task if you plan to use the Lotus Connections Multi-Service Portlet plug-in or Lotus Connections Plug-in for Sametime. These extensions do not function as expected when Lotus Connections is configured to force authentication.
The reader role of the Communities feature is set to Everyone by default. If you perform this procedure to change the reader role access level for any of the features that have widgets that are displayed within the Communities feature, also make the same change to the Communities reader role or the widget will no longer work in Communities.
In an effort to invite people to join the social networking community, many of the Lotus Connections features allow users to read public information, such as public blogs or user profiles without requiring users to log in to the feature first. In many cases, it is not until you want to edit your own profile or blog that credentials are required. If you do not want people or a subset of people to be able to freely browse through public information, you can force them to log in to each feature before they can view any content.
Force users to log in before they can access a feature
- Open the WAS admin console hosting the feature for which you want to restrict access and go to...
Applications | Enterprise Applications | feature
If you select the Profiles feature and the Profiles service extension is enabled, also enable single sign-on for LDAP.
- Click...
Security role to user/group mapping
...and select the check box in the column...
All authenticated?
- Select the check box in the Select column next to the reader role.
- To require only a subset of users to authenticate before they gain access, click Look up users or Look up groups to retrieve a list of users and groups from your directory, and then select a user or group to apply this access level to.
- Repeat the previous steps for each feature that you want to force user to authenticate with before using.
- Activities and Home page require users to authenticate by default. The other features do not.
- As long as you have configured single sign-on between the features, requiring authentication for each feature does not prompt the same users for credentials as they move from one feature to another within a single session. It only prompts for credentials when users log in to the first feature.
- If you restrict access to the reader role for the Profiles feature, then enable the Lotus Connections service extensions. If you do not, then users might have trouble logging in to the other features.
- Click OK. Click Apply, and then click OK.
Related tasks
Security
Enable single sign-on between all features
Enable single sign-on for standalone LDAP
Customizing login attributes
Enable Lotus Connections service extensions
Authenticating requests