Knowledge Partner
Knowledge Partner
589 views

IDM 4.5.1 Office365 Driver 4.1.0.0 released

Enhancements:
- Added support of .NET 4.5 Framework
- Added support of latest MS online modules
- Added two new user types support – UserMailbox and MailUser
- Added native Powershell support – Capable of executing PS commands by
the driver
- Added support of most of Azur and Exchange Schema attributes
Fixes:
- Office 365 shim needs native PS interface. Bug 800676
- Office 365 - Need support for hybrid mode. Bug 885228
- Office365 Questions - "TypeInitializationException. Bug 904908
- Ehn: Full Schema Mapping to Azur. Bug 906780
- Ehn: multivalue attributes should be handled correctly. Bug 906782
- Office 365 query for user license returns zero results. Bug 913326
- Driver fails to set the ManagedBy attribute when a group is created.
Bug 922379
- No way to set a groups Alias, Display Name and Email Address when
creating a group of Group Type =
MailEnabledSecurity. Bug 922381
- Adding a user to group fails if user has an apostrophe in the UPN. Bug
922799
- Office 365 requires publisher channel to be active. Bug 926456
- Office 365 Invalid Sync Attribute:LicenseAssignment. Bug 926459
- Apostrophes in the Department field are not handled properly, Bug 926460
- Office 365 issue with spaces in group alias names. Bug 926465
- Primary SMTP Address overwritten on Modify of Email Address attribute.
Bug 928091
- Resetting of UserPrincipalName does not correctly escape Apostrophe.
Bug 928672
- Office 365 driver filter change causes driver anomaly. Bug 930774
- Investigate driver allowing sub events when rebuilding the cache files.
Bug 930921
- Remove-all of EmailAddresses fails to remove all the Email ids. Bug
931752
- Add EmailAddresses to O365 Driver filter. Bug 934019
- Office 365 should not have errors/warnings during normal operations.
Bug 934778


Personally, I'm most interested in that native Powershell support. It's
similar to the way the current MAD driver allows you to execute arbitrary
Powershell commands via the "PSExecute" pseudo attribute. Looks like the
docs have been updated, too.



--
--------------------------------------------------------------------------
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.
Labels (1)
0 Likes
6 Replies
Knowledge Partner
Knowledge Partner

Re: IDM 4.5.1 Office365 Driver 4.1.0.0 released

David Gersic wrote:

> Personally, I'm most interested in that native Powershell support. It's
> similar to the way the current MAD driver allows you to execute arbitrary
> Powershell commands via the "PSExecute" pseudo attribute. Looks like the
> docs have been updated, too.


It looks better because they allow for more two-way communication (look at the powershell query example which returns an instance)
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
jacmarpet1 Absent Member.
Absent Member.

Re: IDM 4.5.1 Office365 Driver 4.1.0.0 released


dgersic;258776 Wrote:
> Enhancements:
> - Added support of .NET 4.5 Framework
> - Added support of latest MS online modules
> - Added two new user types support – UserMailbox and MailUser
> - Added native Powershell support – Capable of executing PS commands
> by
> the driver
> - Added support of most of Azur and Exchange Schema attributes
> Fixes:
> - Office 365 shim needs native PS interface. Bug 800676
> - Office 365 - Need support for hybrid mode. Bug 885228
> - Office365 Questions - "TypeInitializationException. Bug 904908
> - Ehn: Full Schema Mapping to Azur. Bug 906780
> - Ehn: multivalue attributes should be handled correctly. Bug 906782
> - Office 365 query for user license returns zero results. Bug 913326
> - Driver fails to set the ManagedBy attribute when a group is created.
> Bug 922379
> - No way to set a groups Alias, Display Name and Email Address when
> creating a group of Group Type =
> MailEnabledSecurity. Bug 922381
> - Adding a user to group fails if user has an apostrophe in the UPN.
> Bug
> 922799
> - Office 365 requires publisher channel to be active. Bug 926456
> - Office 365 Invalid Sync Attribute:LicenseAssignment. Bug 926459
> - Apostrophes in the Department field are not handled properly, Bug
> 926460
> - Office 365 issue with spaces in group alias names. Bug 926465
> - Primary SMTP Address overwritten on Modify of Email Address
> attribute.
> Bug 928091
> - Resetting of UserPrincipalName does not correctly escape Apostrophe.
> Bug 928672
> - Office 365 driver filter change causes driver anomaly. Bug 930774
> - Investigate driver allowing sub events when rebuilding the cache
> files.
> Bug 930921
> - Remove-all of EmailAddresses fails to remove all the Email ids. Bug
> 931752
> - Add EmailAddresses to O365 Driver filter. Bug 934019
> - Office 365 should not have errors/warnings during normal operations.
> Bug 934778
>
>
> Personally, I'm most interested in that native Powershell support. It's
> similar to the way the current MAD driver allows you to execute
> arbitrary
> Powershell commands via the "PSExecute" pseudo attribute. Looks like
> the
> docs have been updated, too.
>
>
>
> --
> --------------------------------------------------------------------------
> 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.


Are these fixes also coming for IDM 4.0.2?


--
jacmarpet
------------------------------------------------------------------------
jacmarpet's Profile: https://forums.netiq.com/member.php?userid=415
View this thread: https://forums.netiq.com/showthread.php?t=53850

0 Likes
cpedersen Outstanding Contributor.
Outstanding Contributor.

Re: IDM 4.5.1 Office365 Driver 4.1.0.0 released

On 7/9/15 6:44 PM, jacmarpet wrote:
>
> dgersic;258776 Wrote:
>> Enhancements:
>> - Added support of .NET 4.5 Framework
>> - Added support of latest MS online modules
>> - Added two new user types support – UserMailbox and MailUser
>> - Added native Powershell support – Capable of executing PS commands
>> by
>> the driver
>> - Added support of most of Azur and Exchange Schema attributes
>> Fixes:
>> - Office 365 shim needs native PS interface. Bug 800676
>> - Office 365 - Need support for hybrid mode. Bug 885228
>> - Office365 Questions - "TypeInitializationException. Bug 904908
>> - Ehn: Full Schema Mapping to Azur. Bug 906780
>> - Ehn: multivalue attributes should be handled correctly. Bug 906782
>> - Office 365 query for user license returns zero results. Bug 913326
>> - Driver fails to set the ManagedBy attribute when a group is created.
>> Bug 922379
>> - No way to set a groups Alias, Display Name and Email Address when
>> creating a group of Group Type =
>> MailEnabledSecurity. Bug 922381
>> - Adding a user to group fails if user has an apostrophe in the UPN.
>> Bug
>> 922799
>> - Office 365 requires publisher channel to be active. Bug 926456
>> - Office 365 Invalid Sync Attribute:LicenseAssignment. Bug 926459
>> - Apostrophes in the Department field are not handled properly, Bug
>> 926460
>> - Office 365 issue with spaces in group alias names. Bug 926465
>> - Primary SMTP Address overwritten on Modify of Email Address
>> attribute.
>> Bug 928091
>> - Resetting of UserPrincipalName does not correctly escape Apostrophe.
>> Bug 928672
>> - Office 365 driver filter change causes driver anomaly. Bug 930774
>> - Investigate driver allowing sub events when rebuilding the cache
>> files.
>> Bug 930921
>> - Remove-all of EmailAddresses fails to remove all the Email ids. Bug
>> 931752
>> - Add EmailAddresses to O365 Driver filter. Bug 934019
>> - Office 365 should not have errors/warnings during normal operations.
>> Bug 934778
>>
>>
>> Personally, I'm most interested in that native Powershell support. It's
>> similar to the way the current MAD driver allows you to execute
>> arbitrary
>> Powershell commands via the "PSExecute" pseudo attribute. Looks like
>> the
>> docs have been updated, too.
>>
>>
>>
>> --
>> --------------------------------------------------------------------------
>> 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.

>
> Are these fixes also coming for IDM 4.0.2?


The readme states that the driver is supported with IDM 4.5 and 4.0.2.

Casper


0 Likes
bartvdb1 Absent Member.
Absent Member.

Re: IDM 4.5.1 Office365 Driver 4.1.0.0 released


cpedersen;258829 Wrote:
> On 7/9/15 6:44 PM, jacmarpet wrote:
> >
> >
> > Are these fixes also coming for IDM 4.0.2?

>
> The readme states that the driver is supported with IDM 4.5 and 4.0.2.
>
> Casper


Are you sure about that? On 'Downloads - IDM 4.5.1 Office365 Driver
4.1.0.0' (https://download.novell.com/Download?buildid=EGYu8dguw84~) it
says:
> System Requirements
>
> Novell Identity Manager 4.5.1 or higher

and the readme linked there says the same. As does the section
'Prerequisites' (http://tinyurl.com/oekb3af) of the manual. Don't get
me wrong, I'd like to use it with IdM 4.0.2, but before your post all
signs indicated that is not supported.


--
bartvdb
------------------------------------------------------------------------
bartvdb's Profile: https://forums.netiq.com/member.php?userid=886
View this thread: https://forums.netiq.com/showthread.php?t=53850

0 Likes
cpedersen Outstanding Contributor.
Outstanding Contributor.

Re: IDM 4.5.1 Office365 Driver 4.1.0.0 released

On 7/14/15 11:14 AM, bartvdb wrote:
>
> cpedersen;258829 Wrote:
>> On 7/9/15 6:44 PM, jacmarpet wrote:
>>>
>>>
>>> Are these fixes also coming for IDM 4.0.2?

>>
>> The readme states that the driver is supported with IDM 4.5 and 4.0.2.
>>
>> Casper

>
> Are you sure about that? On 'Downloads - IDM 4.5.1 Office365 Driver
> 4.1.0.0' (https://download.novell.com/Download?buildid=EGYu8dguw84~) it
> says:
>> System Requirements
>>
>> Novell Identity Manager 4.5.1 or higher

> and the readme linked there says the same. As does the section
> 'Prerequisites' (http://tinyurl.com/oekb3af) of the manual. Don't get
> me wrong, I'd like to use it with IdM 4.0.2, but before your post all
> signs indicated that is not supported.


They have updated the Documentation since I looked at it after the
release
(https://www.netiq.com/documentation/idm45drivers/office365/data/b11rrjn6.html).

It should work with IDM 4.0.2, but you must use the IDM 4.5 Remote Loader.

Support for is something - I will see if I can get someone to comment on it.


0 Likes
cpedersen Outstanding Contributor.
Outstanding Contributor.

Re: IDM 4.5.1 Office365 Driver 4.1.0.0 released

Hi,

We will support this, in the following scenario:

- IDM 4.0.2 Patch 7 engine *)
- IDM 4.5.1 *) .Net Remote Loader

*) or later

The driver will not work with the IDM 4.0.2 .Net remote loader.


Casper



On 7/9/15 6:44 PM, jacmarpet wrote:
>
> dgersic;258776 Wrote:
>> Enhancements:
>> - Added support of .NET 4.5 Framework
>> - Added support of latest MS online modules
>> - Added two new user types support – UserMailbox and MailUser
>> - Added native Powershell support – Capable of executing PS commands
>> by
>> the driver
>> - Added support of most of Azur and Exchange Schema attributes
>> Fixes:
>> - Office 365 shim needs native PS interface. Bug 800676
>> - Office 365 - Need support for hybrid mode. Bug 885228
>> - Office365 Questions - "TypeInitializationException. Bug 904908
>> - Ehn: Full Schema Mapping to Azur. Bug 906780
>> - Ehn: multivalue attributes should be handled correctly. Bug 906782
>> - Office 365 query for user license returns zero results. Bug 913326
>> - Driver fails to set the ManagedBy attribute when a group is created.
>> Bug 922379
>> - No way to set a groups Alias, Display Name and Email Address when
>> creating a group of Group Type =
>> MailEnabledSecurity. Bug 922381
>> - Adding a user to group fails if user has an apostrophe in the UPN.
>> Bug
>> 922799
>> - Office 365 requires publisher channel to be active. Bug 926456
>> - Office 365 Invalid Sync Attribute:LicenseAssignment. Bug 926459
>> - Apostrophes in the Department field are not handled properly, Bug
>> 926460
>> - Office 365 issue with spaces in group alias names. Bug 926465
>> - Primary SMTP Address overwritten on Modify of Email Address
>> attribute.
>> Bug 928091
>> - Resetting of UserPrincipalName does not correctly escape Apostrophe.
>> Bug 928672
>> - Office 365 driver filter change causes driver anomaly. Bug 930774
>> - Investigate driver allowing sub events when rebuilding the cache
>> files.
>> Bug 930921
>> - Remove-all of EmailAddresses fails to remove all the Email ids. Bug
>> 931752
>> - Add EmailAddresses to O365 Driver filter. Bug 934019
>> - Office 365 should not have errors/warnings during normal operations.
>> Bug 934778
>>
>>
>> Personally, I'm most interested in that native Powershell support. It's
>> similar to the way the current MAD driver allows you to execute
>> arbitrary
>> Powershell commands via the "PSExecute" pseudo attribute. Looks like
>> the
>> docs have been updated, too.
>>
>>
>>
>> --
>> --------------------------------------------------------------------------
>> 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.

>
> Are these fixes also coming for IDM 4.0.2?
>
>



0 Likes
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.