This section guides you through using the SOAP Service to set up and use the self-registration feature. You can use an application such as SOAP UI to try out the service.
The self sign up process creates the user and locks the user account until the user confirmation is received. The created user has an expiry period which, if exceeded, ensures the account cannot be unlocked. The expired accounts are not actually used by the creator and may have been forgotten long ago. The system administrator can later delete these accounts if needed, hence making this a better way to manage the resources.
To set up and use the self registration feature with REST APIs, which is now the recommended method, see Self Sign Up Using REST APIs.
Configuring WSO2 Identity Server
identity.xmlfile found in the
<IS_HOME>/repository/conf/identity/directory. Enable the following SOAP identity listener by setting the
true. Disable the REST API listeners (listeners with
orderId=97) by setting the
Configure the following properties in the
See the following table for descriptions of these configurations.
This enables the internal email sending module. If this property is set to
false, the email sending data is available to the application via a Web service. Thus the application can send the email using its own email sender.
This enables locking the account when the account is created.
The time specified here is in minutes. In this case, the recovery expires after 7200 minutes.
This enables the email sending function when recovering the account and verifying the user creation.
This enables the authentication flow level checks for the account lock and account confirmation features. This must be enabled to make the account confirmation feature work.
Configure the email-admin-config.xml file found in
<PRODUCT_HOME>/repository/conf/email/with the email template of type “
accountConfirmation”. The following is a sample template:
Tip: You can also customize the email template through the WSO2 IS management console in other languages. For more information on how to do this, see Customizing Automated Emails.
<IS_HOME>/repository/conf/axis2/axis2.xmlfile and uncomment the following email
transportSenderconfigurations. This is necessary because notification sending is internally managed. The configuration values provided are sample values therefore, provide your email details as required.
Custom user store - claim mapping
If you are using a custom user store, follow the steps below and map the claim. Note that this is only required for custom user stores.
Start the IS server and login to the management console.
- Click on List under Claims on the Main tab and click on the http://wso2.org/claims dialect.
- Click on the Edit button next to the AccountLocked claim and map the claim to the relevant attribute in the underlying user store.
See Claim Management for more information on how to do this.
Try out the service
Once you have configured the WSO2 IS, make the following SOAP requests in the order that it is listed, to use the service to self register a user.
Self Sign Up
The sequence of services calls are described below for self sign up.
getUserIdentitySupportedClaims() - Set of claims to which the user profile details should be saved in the Identity Server.
registerUser() - This registers a user in the system. You need to pass values like user name, password, claim attributes and values returned from the previous call and the tenant domain. The confirmation code is sent by email to the given email address.
The sequence of service calls are described below for account confirmation.
getCaptcha() - Get the captcha for the current request.
confirmUserSelfRegistration() - The confirmation code sent to user account, user name, captcha details and tenant domain needs to be passed to the call. Upon successful verification the account is unlocked. Also the verification status is returned to the caller.
Resending the confirmation email
Tip: Once the account is registered and confirmed, if the user has not received the email, the confirmation email can be resent.
To receive the confirmation email again, the user can do the following:
Attempt to log in to the WSO2 Identity Server dashboard using the specified credentials that were not activated. The following notification and option will appear.
- Click on the Resend button and the confirmation email will be sent again to the registered email address.