Anonymous_User Absent Member.
Absent Member.
311 views

O365 Driver -Schema Mapping Question


We are just getting this driver setup. According to the documentation
we should be able to map attributes from Identity Vault up to O365, but
we are having an issue getting the attributes to map up to the
CustomAttributes in O365. I know the mapping that we currently have
isn't correct. Can someone point me in the right direction?

<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE attr-name-map PUBLIC
"nds_2"
"C:\netiq\idm\apps\Designer\plugins\com.novell.idm.schemamap_4.0.0.201509291552\DTD\nds_2.dtd"><attr-name-map>
<attr-name class-name="User">
<nds-name>company</nds-name>
<app-name>Company</app-name>
</attr-name>
<attr-name class-name="User">
<nds-name>costCenterDescription</nds-name>
<app-name>CustomAttribute10</app-name>
</attr-name>
<attr-name class-name="User">
<nds-name>DistrictName</nds-name>
<app-name>CustomAttribute7</app-name>
</attr-name>
<attr-name class-name="User">
<nds-name>division</nds-name>
<app-name>CustomAttribute5</app-name>
</attr-name>
<attr-name class-name="User">
<nds-name>employeeType</nds-name>
<app-name>CustomAttribute3</app-name>
</attr-name>
<attr-name class-name="User">
<nds-name>Initials</nds-name>
<app-name>Initials</app-name>
</attr-name>
<attr-name class-name="User">
<nds-name>jobCode</nds-name>
<app-name>CustomAttribute4</app-name>
</attr-name>
<attr-name class-name="User">
<nds-name>mailstop</nds-name>
<app-name>CustomAttribute6</app-name>
</attr-name>
<attr-name class-name="User">
<nds-name>manager</nds-name>
<app-name>Manager</app-name>
</attr-name>
<attr-name class-name="User">
<nds-name>Postal Office Box</nds-name>
<app-name>PostOfficeBox</app-name>
</attr-name>
<attr-name class-name="User">
<nds-name>preferredName</nds-name>
<app-name>CustomAttribute1</app-name>
</attr-name>
<attr-name class-name="User">
<nds-name>RegionName</nds-name>
<app-name>CustomAttribute9</app-name>
</attr-name>
<attr-name class-name="User">
<nds-name>TerritoryName</nds-name>
<app-name>CustomAttribute8</app-name>
</attr-name>
<attr-name class-name="User">
<nds-name>workforceID</nds-name>
<app-name>CustomAttribute2</app-name>
</attr-name>
<class-name>
<nds-name>Group</nds-name>
<app-name>MSolGroup</app-name>
</class-name>
<attr-name class-name="Group">
<nds-name>authOrig</nds-name>
<app-name>AcceptMessagesOnlyFrom</app-name>
</attr-name>
<attr-name class-name="Group">
<nds-name>CN</nds-name>
<app-name>DisplayName</app-name>
</attr-name>
<attr-name class-name="Group">
<nds-name>Description</nds-name>
<app-name>Description</app-name>
</attr-name>
<attr-name class-name="Group">
<nds-name>EMail Address</nds-name>
<app-name>EmailAddress</app-name>
</attr-name>
<attr-name class-name="Group">
<nds-name>GroupType</nds-name>
<app-name>GroupType</app-name>
</attr-name>
<attr-name class-name="Group">
<nds-name>Member</nds-name>
<app-name>Member</app-name>
</attr-name>
<attr-name class-name="Group">
<nds-name>Owner</nds-name>
<app-name>ManagedBy</app-name>
</attr-name>
<class-name>
<nds-name>User</nds-name>
<app-name>MSolUser</app-name>
</class-name>
<attr-name class-name="User">
<nds-name>city</nds-name>
<app-name>City</app-name>
</attr-name>
<attr-name class-name="User">
<nds-name>CN</nds-name>
<app-name>UserPrincipalName</app-name>
</attr-name>
<attr-name class-name="User">
<nds-name>Facsimile Telephone Number</nds-name>
<app-name>Fax</app-name>
</attr-name>
<attr-name class-name="User">
<nds-name>Full Name</nds-name>
<app-name>DisplayName</app-name>
</attr-name>
<attr-name class-name="User">
<nds-name>Given Name</nds-name>
<app-name>FirstName</app-name>
</attr-name>
<attr-name class-name="User">
<nds-name>Internet EMail Address</nds-name>
<app-name>AlternateEmailAddresses</app-name>
</attr-name>
<attr-name class-name="User">
<nds-name>L</nds-name>
<app-name>Office</app-name>
</attr-name>
<attr-name class-name="User">
<nds-name>Language</nds-name>
<app-name>PreferredLanguage</app-name>
</attr-name>
<attr-name class-name="User">
<nds-name>Login Disabled</nds-name>
<app-name>BlockCredential</app-name>
</attr-name>
<attr-name class-name="User">
<nds-name>mobile</nds-name>
<app-name>MobilePhone</app-name>
</attr-name>
<attr-name class-name="User">
<nds-name>nspmDistributionPassword</nds-name>
<app-name>Password</app-name>
</attr-name>
<attr-name class-name="User">
<nds-name>OU</nds-name>
<app-name>Department</app-name>
</attr-name>
<attr-name class-name="User">
<nds-name>Password Allow Change</nds-name>
<app-name>ForceChangePassword</app-name>
</attr-name>
<attr-name class-name="User">
<nds-name>Physical Delivery Office Name</nds-name>
<app-name>Office</app-name>
</attr-name>
<attr-name class-name="User">
<nds-name>Postal Code</nds-name>
<app-name>PostalCode</app-name>
</attr-name>
<attr-name class-name="User">
<nds-name>S</nds-name>
<app-name>State</app-name>
</attr-name>
<attr-name class-name="User">
<nds-name>SA</nds-name>
<app-name>StreetAddress</app-name>
</attr-name>
<attr-name class-name="User">
<nds-name>Surname</nds-name>
<app-name>LastName</app-name>
</attr-name>
<attr-name class-name="User">
<nds-name>Telephone Number</nds-name>
<app-name>PhoneNumber</app-name>
</attr-name>
<attr-name class-name="User">
<nds-name>Title</nds-name>
<app-name>Title</app-name>
</attr-name>
</attr-name-map>


--
abertucci01
------------------------------------------------------------------------
abertucci01's Profile: https://forums.netiq.com/member.php?userid=11452
View this thread: https://forums.netiq.com/showthread.php?t=55390

Labels (1)
0 Likes
3 Replies
Knowledge Partner
Knowledge Partner

Re: O365 Driver -Schema Mapping Question

On Thu, 18 Feb 2016 17:22:01 +0000, abertucci01 wrote:

> We are just getting this driver setup. According to the documentation
> we should be able to map attributes from Identity Vault up to O365, but
> we are having an issue getting the attributes to map up to the
> CustomAttributes in O365. I know the mapping that we currently have
> isn't correct. Can someone point me in the right direction?


CustomAttributes are an Exchange thing, not an Active Directory thing.
You'll need to explore the PowerShell commandlet support to set them, not
just map them in the schema map.


--
--------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.microfocus.com

Please post questions in the forums. No support provided via email.
If you find this post helpful, please click on the star below.
0 Likes
Knowledge Partner
Knowledge Partner

Re: O365 Driver -Schema Mapping Question

David Gersic <dgersic@no-mx.forums.microfocus.com> wrote:
> On Thu, 18 Feb 2016 17:22:01 +0000, abertucci01 wrote:
>
>> We are just getting this driver setup. According to the documentation
>> we should be able to map attributes from Identity Vault up to O365, but
>> we are having an issue getting the attributes to map up to the
>> CustomAttributes in O365. I know the mapping that we currently have
>> isn't correct. Can someone point me in the right direction?

>
> CustomAttributes are an Exchange thing, not an Active Directory thing.
> You'll need to explore the PowerShell commandlet support to set them, not
> just map them in the schema map.
>
>


Not entirely correct. These are listed as supported in latest o365 driver
doc
https://www.netiq.com/documentation/idm45drivers/office365/data/b138b384.html

So if you are patched to latest shim and this doesn't work. I'd open a SR

--
If you find this post helpful and are logged into the web interface, show
your appreciation and click on the star below...
Alex McHugh - Knowledge Partner - Stavanger, Norway
Who are the Knowledge Partners
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
0 Likes
Knowledge Partner
Knowledge Partner

Re: O365 Driver -Schema Mapping Question

David right, when he mention about CustomAttributes!
CustomAttributes in O365 will be available, when you will use MsolOnline UserMailbox/MailUser (Exchange Online users)


Using PowerShell, if you want to add a custom attribute for an individual user, you would run the following PowerShell command in Exchange. If you want to add the same to a user in office 365, you would first have to connect to Office 365, then run the following PowerShell command.

Set-Mailbox –Identity “Fname Lname” –CustomAttribute1 attributevalue
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.