This documentation is for WSO2 Private PaaS 4.1.0. View documentation for the latest release.
Page Comparison - Working with Properties of User Stores (v.1 vs v.2) - WSO2 Private PaaS 4.1.0 - WSO2 Documentation

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The following table provides descriptions of the key properties you use to configure primary user stores.

...

Property name

...

Description

...

Connection URL to the user store server. In the case of default LDAP in Carbon, the port is specified in the carbon.xml file, and a reference to that port is included in this configuration.

...

The username used to connect to the database and perform various operations. This user does not have to be an administrator in the user store or have an administrator role in the WSO2 product that you are using, but this user MUST have permissions to read the user list and users' attributes and to perform search operations on the user store. The value you specify is used as the DN (Distinguish Name) attribute of the user. This property is mandatory.

...

Filtering criteria for listing all the user entries in the user store. This query or filter is used when doing search operations on users. In this case, the search operation only provides the objects created from the specified class. This query is the same as listing out all the available users in the management console.

...

DN of the context or object under which the user entries are stored in the user store. In this case, it is the "users" container. When the user store searches for users, it will start from this location of the directory.

Info

Different databases have different search bases.

...

The attribute used for uniquely identifying a user entry. Users can be authenticated using their email address, UID, etc.

Info

The name of the attribute is considered as the username.

...

This property defines the JavaScript regular expression pattern when the EnableEmailUserName property is set to true in carbon.xml configuration file. If you need to support both email as a user name and normal user names, you can set this property as follows.

Code Block
languagexml
<Property name="UsernameWithEmailJavaScriptRegEx">^[\S]{3,30}$</Property>

...

PasswordJavaScriptRegEx

...

A regular expression to validate usernames. By default, strings have a length of 5 to 30. Only non-empty characters are allowed. You can provide ranges of alphabets, numbers and also ranges of ASCII values in the RegEx properties.

Code Block
languagexml
<Property name="UsernameJavaRegEx">[a-zA-z0-9._-|!#$%"'*-=?^`():,;~//\u00C0-\u1FFF\u2C00-\uD7FF\w]{3,30}$</Property>

...

ReadOnly

...

IsEmailUserName

...

DomainCalculation

...

PasswordDigest

...

(JDBC) Digesting algorithm of the password. Has values such as, PLAIN_TEXT, SHA etc.

...

StoreSaltedPassword

...

(JDBC) Indicates whether to salt the password.

...

UserNameUniqueAcrossTenants

...

(JDBC) An attribute used for multi-tenancy.

...

PasswordJavaRegEx

...

(LDAP and JDBC) A regular expression to validate passwords. By default, strings having a length between 5 to 30 with non-empty characters are allowed.

...

PasswordJavaScriptRegEx

...

UsernameJavaRegEx

...

RolenameJavaRegEx

...

RolenameJavaScriptRegEx

...

MultiTenantRealmConfigBuilder

...

Include Page
shared:Working with Properties of User Stores (V3)
shared:Working with Properties of User Stores (V3)