5.2 Schema Mapping

This section details the default schema mapping of the driver. The schema map details how Identity Vault attributes and classes are translated into Google Apps attributes and classes.

The section includes:

5.2.1 User Attributes Mapping

Identity Vault

Google Apps

User

UserEntry

 

Agreed to terms

preferredName

Alias

assistant

Assistant

assistantPhone

AssistantPhoneNumber

 

Brother

 

CallbackPhoneNumber

 

CarPhoneNumber

 

ChangePasswordAtNextLogin

 

Child

 

CompanyMainPhoneNumber

 

DomesticPartner

 

ExternalId

Surname

FamilyName

 

Father

 

Friend

 

GeneralPhoneNumber

Given Name

GivenName

 

GmailSettingsDelegates

 

GmailSettingsEnableIMAP

 

GmailSettingsEnablePOP

 

GmailSettingsForwarding

 

GmailSettingsLabel

Language

GmailSettingsLanguage

 

GmailSettingsSendAs

 

GmailSettingsSignature

Groups Memberships

Groups

 

Hidden

 

HomeCity

 

HomeCountry

 

HomeCountryCode

 

HomeFaxPhoneNumber

 

HomeFormattedAddress

 

HomePhoneNumber

 

HomePostalCode

 

HomeRegion

Home Phone

HomeStreetAddress

 

IpWhiteListed

 

IsAdmin

internationalISDNNumber

ISDNPhoneNumber

Login Disabled

IsSupended

 

MainPhoneNumber

manager

Manager

mobile

MobilePhoneNumber

 

Mother

 

OrgCostCenter

OU

OrgDepartment

 

OrgJobDescription

L

OrgLocation

company

OrgName

 

OrgSymbol

Title

OrgTitle

 

OtherEmailAddress

 

OtherFaxPhoneNumber

otherPhoneNumber

OtherPhoneNumber

Pager

PagerPhoneNumber

 

Parent

 

Partner

nspmDistributionPassword

Password

 

Photo

 

RadioPhoneNumber

 

ReferredBy

 

Sister

 

Spouse

TelexNumber

TelexPhoneNumber

 

TTY_TDDPhoneNumber

CN

UserName

 

WorkCity

 

WorkCountry

 

WorkCountryCode

Fascimile Telephone Number

WorkFaxPhoneNumber

 

WorkFormattedAddress

 

WorkMobilePhoneNumber

 

WorkPagerPhoneNumber

 

WorkPhoneNumber

 

WorkPostalCode

S

WorkRegion

SA

WorkStreetAddress

5.2.2 Group Attribute Mapping

Identity Vault

Google Apps

Group

Group

 

AllowExternalMembers

 

AllowGoogleCommunication

 

AllowWebPosting

 

ArchiveOnly

 

CustomReplyTo

 

DefaultMessageDenyNotificationText

Description

Description

DirXML-GAGroupEmailAddress

EmailAddress

 

IncludeInGlobalAddressList

 

IsArchived

 

MaxMessageBytes

Member

Members

 

MembersCanPostAsTheGroup

 

MessageDisplayFont

 

MessageModerationLevel

CN

Name

Owner

Owners

 

PrimaryLanguage

 

ReplyTo

 

SendMessageDenyNotification

 

ShowInGroupDirectory

 

SpamModerationLevel

 

WhoCanContactOwner

 

WhoCanInvite

 

WhoCanJoin

 

WhoCanLeaveGroup

 

WhoCanPostMessage

 

WhoCanViewGroup

 

WhoCanViewMembership

5.2.3 Organizational Unit Attribute Mapping

Identity Vault

Google Apps

Organizational Unit

Organizational Unit

 

BlockInheritance

Description

Description

OU

Name

 

OrgUnitPath

 

ParentOrgUnitPath

5.2.4 Contact Attribute Mapping

The ContactEntry class does not map directly to a class in eDirectory. The schema can be extended (or mapped to the user object class). The driver contains a sample GoogleContact.sch file that can be used to extend the eDirectory schema. The following table lists the available attributes within Google Apps.

Identity Vault (EXAMPLE)

Google Apps

GoogleContact

ContactEntry

assistant

Assistant

assistantPhone

AssistantPhoneNumber

 

Brother

 

CallbackPhoneNumber

 

CarPhoneNumber

 

Child

 

CompanyMainPhoneNumber

 

Cube

 

DomesticPartner

 

Father

 

Friend

 

GeneralPhoneNumber

 

HomeCity

 

HomeCountry

 

HomeCountryCode

 

HomeEmailAddress

 

HomeFaxPhoneNumber

Home Phone

HomePhoneNumber

 

HomePostalCode

 

HomeRegion

 

HomeStreetAddress

internationalISDNNumber

ISDNPhoneNumber

 

MainPhoneNumber

Manager

Manager

mobile

MobilePhoneNumber

 

Mother

 

OfficeMailstop

OU

OrgDepartment

 

OrgJobDescription

L

OrgLocation

company

OrgName

 

OrgSymbol

Title

OrgTitle

 

OtherEmailAddress

 

OtherFaxPhoneNumber

otherPhoneNumber

OtherPhoneNumber

Pager

PagerPhoneNumber

 

Parent

 

Partner

 

ProfileAdditionalName

 

ProfileFamilyName

 

ProfileFullName

 

ProfileGivenName

 

ProfileNamePrefix

 

ProfileNameSuffix

 

RadioPhoneNumber

 

ReferredBy

 

Sister

 

Spouse

TelexNumber

TelexPhoneNumber

 

TTY_TDDPhoneNumber

 

WorkCity

 

WorkCountry

 

WorkCountryCode

 

WorkEmailAddress

Facsimile Telephone Number

WorkFaxPhoneNumber

mobile

WorkMobilePhoneNumber

pager

WorkPagerPhoneNumber

Telephone Number

WorkPhoneNumber

 

WorkPostalCode

 

WorkRegion

 

WorkStreetAddress

5.2.5 Using Google Custom Schema

The Google Apps Directory API provides the ability to extend the schema of a UserEntry object through the use of Google Custom Schema. Customers can create multiple custom schemas, each of which can define multiple custom attributes. These fields can be used to hold attribute data. Adding Custom Schema effectively extends the application schema managed by the driver. When the driver is asked to refresh application schema from Designer or iManager, the driver queries all of the Custom Schema objects, and adds all of the attributes to the application schema. The custom schema attributes appear in the schema as <Schema name>.<Attribute Name>. Once the driver has returned the new schema attributes, the attributes are available to be included in the filter, schema mapped, and used in the Policy Builder.

Google Custom Schema attribute definitions carry metadata to indicate whether or not the attribute is multi-valued, as well as the datatype of the field. Google supports the following datatypes:

  • BOOL

  • DATE

  • DOUBLE

  • EMAIL

  • INT64

  • PHONE

  • STRING