Introducing the Novell Identity Manager Google Apps Driver – Part 2
In the first article of this series Introducing the Novell Identity Manager Google Apps Driver – Part 1 I introduced the new driver and some of the features. In this article I will go into more in-depth with the objects that are supported by the driver starting with the User object.
The user object in eDirectory is mapped to the UserEntry object in Google. Google uses different API’s for different features related to users. The Provisioning API is responsible for creating the Google Apps account, password, Given Name, First Name, Login Disabled, and Nick Name.
The profile API is responsible for the information that is found in the Google Contact application (Address Book). The driver supports over 20 of these attributes including department, phone number, mobile phone number, title, and location. The profile API is similar to the shared contact API in attributes only. The contact API will be discussed in a future article. Google has a very interesting quirk with the information passed to these API’s. Any new user that is created via the Google control panel or from the API will not show up in Google Contacts (Address Book) for 24 hours even though the information is there and can be queried for immediately after creation. When testing the driver please be aware of this. Once the initial 24 hour period is complete the changes will show as soon as the driver processes the modify.
The driver also supports attributes that affect the users email account via the email API. These attributes include the GmailSettings attributes included with the drivers schema. The driver documentation includes sample settings on how to set these values on your User accounts. In most cases these attributes are not necessary. However if you have multiple email domains or unique email requirements these attributes may be necessary.
The following list details a few of the most commonly used attributes with the email api:
All of the Identity Management events (Add, Modify, Delete, Rename, Move and Query) are supported on this object. The default driver packages include policies for account entitlements as well as a framework for multiple email domain support. I will dedicate an entire article for setting the driver up to work with multiple email domains. Here is a breakdown of all the events.
Placement of users is either flat or mirrored. It is possible to write entitlements for user placement if you require it. It is important to note that when placing a user in Google Apps that the DN not contain a leading ‘\’ like we do with other drivers. We will discuss Organizations in a future article as well.
In the next article we will discuss group management with the driver.
The driver has officially shipped on April 15th and is included with the standard and advanced editions of Identity Manager 4.0.1.
Disclaimer: As with everything else at NetIQ Cool Solutions, this content is definitely not supported by NetIQ, so Customer Support will not be able to help you if it has any adverse effect on your environment. It just worked for at least one person, and perhaps it will be useful for you too. Be sure to test in a non-production environment.