This topic explains the architecture of a user store manager and it's management and its main components. Once you have understood the concepts defined in this topic, you will be able to write a custom user store manager.
User management architecture
The complete functionality and contents of a user store is called a realm. The realm includes the user management classes, configuration, and repository. A realm is exposed as a service so that other classes can interact with the user store.
|Table of Contents|
User Store Manager
The User Store Manager is responsible for managing the underlying user store. It is represented by the
UserStoreManager Java interface. There can be different User Store Manager implementations to connect with different user stores, but you can configure only one User Store Manager implementation in a single user realm (that is, a single WSO2 Carbon instance). The User Store Manager can be operated in both read/write mode and read-only mode. In read-only mode, you can only connect with an existing user store. WSO2 products provide the following default User Store Manager implementations:
You can write a custom user store manager implementation by implementing
UserStoreManager or by extending
AbstractUserStoreManager or one of the default implementations.
JDBCUserStoreManager class uses a schema that is specific to WSO2 Carbon. It contains the following tables:
You can find the full schema of these tables from the database script files in the
<PRODUCT_HOME>/dbscripts directory. Note that these scripts also contain schemas for other tables that are used for user management and registry functions. If your organization contains an existing JDBC user store that you want to use with a WSO2 product, you must extend
JDBCUserStoreManager and write a new implementation for your user store according to your schema.
The Authorization Manager uses role-based access control (RBAC) to protect resources related to the WSO2 Carbon platform. The default implementation of the Authorization Manager is
JDBCAuthorizationManager, which uses a permission model specific to WSO2 Carbon and uses the authorization data that is stored in tables in the JDBC database. You can replace this implementation with a custom implementation (for example, if you want to use a XACML authorization manager) and use it with WSO2 products.
In WSO2 Identity Server, the Claim Manager is responsible for adding/deleting claims and mapping claims from one namespace to another. The default implementation is
DefaultClaimManager, which is used to store claim data in tables of the JDBC database.
See Writing a Custom User Store Manager for a sample on how to configure the custom user store.