Name	Last Update	Last Commit da4e5e11 – [OPENIDM-3463]Update openidmui -> selfservice, ... History
..
conf	Loading commit data...
data	Loading commit data...
script	Loading commit data...
tools	Loading commit data...
README.md	Loading commit data...

README.md

/**
 * DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
 *
 * Copyright (c) 2014-2015 ForgeRock AS. All rights reserved.
 *
 * The contents of this file are subject to the terms
 * of the Common Development and Distribution License
 * (the License). You may not use this file except in
 * compliance with the License.
 *
 * You can obtain a copy of the License at
 * http://forgerock.org/license/CDDLv1.0.html
 * See the License for the specific language governing
 * permission and limitations under the License.
 *
 * When distributing Covered Code, include this CDDL
 * Header Notice in each file and include the License file
 * at http://forgerock.org/license/CDDLv1.0.html
 * If applicable, add the following below the CDDL Header,
 * with the fields enclosed by brackets [] replaced by
 * your own identifying information:
 * "Portions Copyrighted [year] [name of copyright owner]"
 */

Sample 3 - Scripted SQL

This sample demonstrates creating a new CustomScriptedSQL connector, using the custom-scripted-connector-bundler-3.2.0-SNAPSHOT.jar that is included in the tools directory of the OpenIDM zip file. The sample relies on the new custom connector that you will create with the connector bundler. It provides an example configuration and a handful of Groovy scripts that are used to communicate with an SQL server.

This example requires a fresh installation of OpenIDM. It also requires that you have Maven installed.

For documentation pertaining to this example see: http://openidm.forgerock.org/doc/bootstrap/install-guide/index.html#more-sample3

This sample also demonstrates the use of complex data types. Complex types can be stored, retrieved and synced like any other property of an object. These types can be mapped to your external data sources in any way you choose but are generally stored in the managed data as JSON represented as a String. This may be customized further to do additional work with or transformation on that data.

The sync.json script demonstrates the use of event hooks to perform an action. In this example there are two hooks, one for the onCreate event and another for onUpdate, both for the managed user to external repo user case. In both events this sample will log a statement to OpenIDM's log file (see the logs directory) when a managed user is created or updated in the external repo. In both cases the script is explicitly included in the sync.json file but could just as easily have referenced an external file for the script source instead. For more information see:

http://openidm.forgerock.org/doc/bootstrap/integrators-guide/appendix-scripting.html

The scripted connector supports any number of custom scripted endpoints. These are configured via the provisioner script and currently support only Groovy. See provisioner.openicf-scriptedsql.json and tools/ResetDatabaseScript.groovy for a sample implementation. Step 5 below executes this script.

CAVEAT: Because MySQL cannot "un-hash" user passwords, there is no way for a recon to retrieve and store the password in the managed user object in OpenIDM. This may impact configurations that support multiple external repositories in that passwords are unlikely to be in sync immediately after a mysql -> managed recon. Despite creating any missing users in the managed repo during reconciliation, their passwords are empty, so those same users synchronized to the other external repositories will have blank passwords. Some additional scripting may be required to handle this situation, depending on the requirements of your deployment.

Setup the Database

Copy the MySQL Connector/J .jar to the OpenIDM bundle/ directory.

$ cp mysql-connector-java-5.1.18-bin.jar /path/to/openidm/bundle/
Set up MySQL to listen on localhost:3306, connecting as root:password.
Create the initial database OpenIDM will sync with.

mysql> CREATE DATABASE hrdb CHARACTER SET utf8 COLLATE utf8_bin;

Create the CustomScriptedSQL Connector

Description: In this section, you generate the classes and files necessary to build a custom connector. Using these generated files, you build the custom ScriptedSQL connector that will be used in the rest of this sample.

From the sample3/create-connector directory, run the following command, using the custom config provided in the sample3/data directory.

$ cd path/to/openidm/samples/sample3/create-connector $ java -jar ../../../tools/custom-scripted-connector-bundler-3.2.0-SNAPSHOT.jar -c ../data/scriptedsql.json

Copy the provided sample scripts into the connector src directory; these will become part of the custom connector.

$ cp ../tools/* src/main/resources/script/hrdb/

If you need to modify the scripts provided, now is the time to do so.

Build the custom connector. (You should be in the sample3/create-connector directory.)

$ mvn install
Change directory up one directory to the sample's main directory, /path/to/openidm/samples/sample3.

$ cd ..
Copy the connector that you created from the create-connector directory to the connectors directory of OpenIDM. If you are in the sample3 directory, run this command:

$ cp create-connector/target/hrdb-connector-1.4.1.0.jar ../../connectors/

At this point you have a connector that is ready to be used in OpenIDM. This connector has all the necessary files that will allow it to be displayed in the UI. It also has both the scripts and provisioner config that allow it to be used.

Load the provisioner.openicf-hrdb.json file into the sample3/conf directory so that it can be used.

$ jar -xvf ../../connectors/hrdb-connector-1.4.1.0.jar conf/provisioner.openicf-hrdb.json

The output should show that the file has been inflated:
```
inflated: conf/provisioner.openicf-hrdb.json
```
Replace the "systemActions" value inside the sample3/conf/provisioner.openicf-hrdb.json with the following value: [ { "scriptId" : "ResetDatabase", "actions" : [ { "systemType" : ".*HRDBConnector", "actionType" : "Groovy", "actionFile" : "tools/ResetDatabaseScript.groovy" } ] } ]
For the purposes of demonstrating this sample, copy the generated html template file associated with this connector. This file will be used to display the connector in the UI.

Inside the connector jar that you created, search for a file containing "1.4.html".

    $ cd path/to/openidm
    $ jar -tvf connectors/hrdb-connector-1.4.1.0.jar | grep "1.4.html"

Extract the file that you found in the preceding step into the /path/to/openidm/ui directory.

    $ jar -xvf connectors/hrdb-connector-1.4.1.0.jar ui/org.forgerock.openicf.connectors.hrdb.HRDBConnector_1.4.html
    $ mkdir -p ui/extension/templates/admin/connector; mv ui/org.forgerock.openicf.connectors.hrdb.HRDBConnector_1.4.html ui/extension/templates/admin/connector

Starting up the sample

Start OpenIDM with the configuration for sample 3.

$ /path/to/openidm/startup.sh -p samples/sample3
Populate the MySQL database with sample data. Use REST to execute a custom script that, in this case, resets and populates the database. This script may be re-run at any time to reset the database.

$ curl -k --header "X-OpenIDM-Username: openidm-admin" --header "X-OpenIDM-Password: openidm-admin" --header "Content-Type: application/json" --request POST "https://localhost:8443/openidm/system/hrdb?_action=script&scriptId=ResetDatabase" { "actions": [ { "result": "Successfully reset the database" } ] }

At this point the MySQL database should be fully populated.

Note that these passwords are hashed, and not available to be read into OpenIDM as cleartext.
sha1 is used to hash these passwords for compatibility reasons; in production, use more secure algorithms.

Run the Sample

Run reconciliation:

$ curl -k -H "Content-type: application/json" -u "openidm-admin:openidm-admin" -X POST "https://localhost:8443/openidm/recon?_action=recon&mapping=systemHrdb_managedUser"
Retrieve the list of users from OpenIDM's internal repository:

$ curl -k -u "openidm-admin:openidm-admin" --request GET "https://localhost:8443/openidm/managed/user/?_queryId=query-all-ids&_prettyPrint=true"

{ "remainingPagedResults": -1, "pagedResultsCookie": null, "resultCount": 5, "result": [ { "rev": "0", "id": "9ee75d24-899c-4221-97a0-0aca298febd6" }, { "_rev": "0", "_id": "25be1c4c-0c2a-48b6-96f6-58d2e4d2357d" }, { "rev": "0", "_id": "2850c77b-f51a-4fb2-8cc4-4c1d03108ac2" }, { "rev": "0", "id": "126d74e1-1c03-4774-b18d-bd4d1dfdf884" }, { "_rev": "0", "id": "46570045-0644-45c6-af10-c88ad3df93cc" } ] }
Query for an individual user (by userName):

$ curl -k -u "openidm-admin:openidm-admin" --request GET "https://localhost:8443/openidm/managed/user?_queryId=for-userName&uid=rowley&_prettyPrint=true"

{ "result" : [ { "mail" : "Rowley.Birkin@example.com", "sn" : "Birkin", "passwordAttempts" : "0", "lastPasswordAttempt" : "Wed Oct 22 2014 09:51:31 GMT-0700 (PDT)", "address2" : "", "givenName" : "Rowley", "effectiveRoles" : [ "openidm-authorized" ], "country" : "", "city" : "", "lastPasswordSet" : "", "organization" : "SALES", "postalCode" : "", "_id" : "ed8bbe46-08a1-4716-9d5f-3cc5d09e2a7c", "_rev" : "1", "cars" : [ { "make" : "BMW", "year" : "2013", "model" : "328ci" }, { "make" : "Lexus", "year" : "2010", "model" : "ES300" } ], "accountStatus" : "active", "telephoneNumber" : "", "roles" : [ "openidm-authorized" ], "effectiveAssignments" : null, "postalAddress" : "", "userName" : "rowley", "stateProvince" : "" } ], "resultCount" : 1, "pagedResultsCookie" : null, "remainingPagedResults" : -1 }

Note the "cars" list containing multiple objects. This structure is displayed in the admin UI as well. The name "cars" was used to help differentiate what matters to the complex type versus what is required by OpenIDM/OpenICF in the Groovy scripts.

In the database the 'car' table joins to the 'users' table via the cars.users_id column. The Groovy scripts are responsible for reading this data from MySQL and repackaging it in a way that OpenIDM can understand. With support for complex types this data is passed through to OpenIDM in the same form: as a list of 'car' objects. Likewise, data is synced from OpenIDM to MySQL in the same form.

Group membership (not shown here) is maintained with a traditional "join table" in MySQL ('groups_users'). OpenIDM does not maintain group membership this way so the Groovy scripts do the work to translate between the two. This demonstrates another form of complex object though the sky is the limit. Complex objects may also be nested to any depth.
Show paging results with page size of 2

$ curl -k -u "openidm-admin:openidm-admin" --request GET 'https://localhost:8443/openidm/system/hrdb/account?_queryFilter=uid+sw+""&_pageSize=2&_sortKeys=timestamp,id'

{ "result":[ { "uid":"bob", "_id":"1" }, { "uid":"rowley", "_id":"2" } ], "resultCount":2, "pagedResultsCookie":"2014-09-11 10:07:57.0,2", "remainingPagedResults":-1 }
Use the pagedResultsCookie from the result in step 10 for the next query to retrieve the next result set. Make sure you encode the date:time.

$ curl -k -u "openidm-admin:openidm-admin" --request GET 'https://localhost:8443/openidm/system/hrdb/account?_queryFilter=uid+sw+""&_pageSize=2&_sortKeys=timestamp,id&_pagedResultsCookie=2014-09-11%2010:07:57.0,2'

{ "result":[ { "uid":"louis", "_id":"3" }, { "uid":"john", "_id":"4" }], "resultCount":2, "pagedResultsCookie":"2014-09-11 10:07:57.0,4", "remainingPagedResults":-1 }

You can log in to the OpenIDM UI (https://localhost:8443/selfservice) with any of the users that were created in the repository by the reconciliation operation. Consult the values from the sample3/tools/ResetDatabaseScript.groovy script to retrieve the clear text passwords of each of these users. Users can update their profiles or passwords. Any changes will be automatically synchronized back to the MySQL database.

GITLAB

org.forgerock / org.forgerock.openidm