Introduction

This wiki page aims to show how to manage user requests are handled; this cover self registration for anonymous usersas well.

...

Self registration

Self registration can be enabled or disabled by setting the value of property createRequest.allowed to true or false.

...

Self registration is enabled by default in embedded mode and disabled by default in real world deployments.

The self registration process

Submit anonymous user request

When enabled, anonymous users can access the self registration form by clicking on the Self registration link available at the bottom of the administration console login form.Image Removed Image Removed

When an anonymous user submits the self registration form, an UserRequest is created and forwarded to designated administrators.
Requests will be available in the administration console under the TODO > User request tab.

Image Added Image Added

Manage user request

Designed administrators can select a user request for reviewing (and possibly modifying) attributes, resources and roles.
Once the request has been approved, the user is created and a new workflow instance is started.

In the default workflow definition, requesting users will go through approval if requiring the role with id 9 (obviously, this is just a reference sample).

Image Removed

Users falling under this condition will be set the createApproval status.

Image Removed

Authenticated user request (Edit profile)

Each authenticated user can edit his own profile by clicking on the username on the top right corner of the admin console window.

When submitting, Once a new user request is created, an administrator can claim the task and choose whether to accept or reject this request. In the former case, the requesting user is created and made active; in the latter the user goes in the rejected status.Image Removed Image Removed Image Removedgenerated and forwarded to designated administrators. Such request will be managed similarly to self-registration requests.