The MySQLUser Connector capabilities are pretty limited. The connector supports just a user creation from "Modeluser" template. The updates of the model user access rights are possible. Updated can be the user name and password. The delete and search of user are also supported.
The MySQLUSer connector uses the template user called the "Modeluser". Model user and its rights are taken as a template for creating every new user on the MySQL resource.
The MySQL Connector supports provisioning and authentication with MySQL databases.
The connector is backward compatible with adapter. All features
from the adapter have been implemented except the "JDBC URL Template"
property. The JDBC URL Template configuration property is not
required, because all versions of MySQL support the same URL schema.
There is no need to change the "JDBC URL Template".
The Datasouce property and JndiProperties has been added
to support the server side defined resources.
The new "MySQL Conversion Utility" server task will convert adapter to connector.
All configuration properties are supported except the "JDBC URL Template".
For further information please see the migration page located at the connector sources.
Provides implementation of connector to MySQL database
resource. MySQL Connector uses MySQL database mysql.user table to
manage users. There could be a multiple records for particular user.
The unique key of the record is a sequence of host, user, schema,
table. The rest of the record consist of encoded user password and SQL
user rights.
The MySQL resource accepts the % wildcard. This wildcard can be used
for specifying any host, any user, any schema, any table.
The user account must have right to read, create, update and
delete the users from any hosts and for any schema and table. The
modeluser can have any rights. Use of same account for user and
modeluser is not recommended and can lead to problems.
The MySQL connector does not difference between the hosts. Every
access right is considered valid from any host. It must imply the
default wildcard "%" for hosts. It is not recommended to set up the
model user with different SQL access rights which differs just in
host.
Newly supported are DataSource name and jndiProperties
configuration properties. If your server environment supports
datasources, you can set up the datasource name, e.g: java:comp/env/jdbc/mysql
which in case of tomcat corespond to following application context
descriptor.
When new datasource is configured, the user, host, password and port
could be left empty.
See {@link org.identityconnectors.mysqluser.MySQLUserConfiguration}
and {@link org.identityconnectors.mysqluser.MySQLUserConnector} for
more information about MySQLUser connector.
Connector Version | Framework Version | Supported Resource Version(s) | Supported Connectors |
---|---|---|---|
1.1 | 1.0 |
|
|
Note: The "Framework Version" listed is the minimum required framework version for that version of the connector. Newer framework versions are backwards compatible and will support previous connectors.