Knowledge Partner
Knowledge Partner

Re: IDM 4 and Office 365

On 7/5/2012 9:26 AM, matthudson wrote:
> Thanks for the replies! I'll let you know how we get on, its looking
> like the scripting driver is the way forward.

I do know that the guys at Omnibond are pondering a Scripting driver
example config to do this. I can follow up and see its current state.
(Heck they might enjoy having someone to test with. you never know?)

Labels (1)
1 Reply
Absent Member.
Absent Member.

Re: IDM 4 and Office 365

Just a quick follow up on this.

If you are creating federated users with the powershell scripts then
you will need to set the ImmutableId attribute to the guid of AD account
(Assuming you are using ADFS). This is what the DirSync tool does. This
is also used as the NameID for the SSO tokens that are produced.

You can get the guid from the users AD dirxml association value.

Another option is to change the claim rule transformations in ADFS to
match what ever attribute you like. This way you could also point
ADFS/IIS at eDir instead of AD.

rtruscot's Profile: https://forums.netiq.com/member.php?userid=293
View this thread: https://forums.netiq.com/showthread.php?t=1960

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.