Configuring self-registration for external users
Set properties that make it possible for people outside of your company to self-register for a Connections account when invited to join.
Before you begin
Note: Self-registration requires that users have anonymous access to be able to register and reset
their guest password. If an access manager solution such as IBM® Security Access Manager is in place, a junction for the following context route has to be
created/whitelisted: /selfservice/
Procedure
-
For external collaboration self-registration to work, it is mandatory that each of the
following properties in the selfregistration-config.xml file have a value
entered. You can modify default values to fit your environment.
Note: For this feature, you need to edit the configuration file directly in the /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/Cell01/LotusConnections-config directory.
-
While completing step 1 is all that's required to deploy the feature, it's a good idea to also
review the following default values now and change any that aren't optimal for your
environment.
- (Optional) Specify other settings if you want to extend the feature, or if you have legal considerations like record keeping of successful registrations or providing a link to a privacy policy document.
What to do next
To prevent invited users from changing their email addresses, it's also best to add readonly=”true” to the [input id=”mail”…/] field in AppSrv01/installedApps/[cell]/Invite.ear/invite.war/pages/register.jsp.