Novell/NetIQ IDM and Shibboleth

[David Gersic]

If you can get me the bug details (Bugzilla #) or a customer service request number, I can see if there's anything that can be done, but the "NAM is their only supported IdP" comment makes me think that I know enough already to say that it's not likely to be fixed by simple technical details being provided. If this affects you, your best bet is to ensure that you have a Service Request open with their support channel, then get your sales contact involved and let them know how important it is to you that it be fixed properly.


________________________________
From: users <users-bounces at shibboleth.net> on behalf of Liam Hoekenga <liamr at umich.edu>
Sent: Monday, February 15, 2016 9:40 AM
To: Shib Users
Subject: Re: Novell/NetIQ IDM and Shibboleth


On Mon, Feb 15, 2016 at 10:24 AM, David Gersic <dgersic at niu.edu<mailto:dgersic at niu.edu>> wrote:

NIU is a long time user of MicroFocus (was NetIQ, was Novell) eDirectory and Identity Manager. We're also using Shibboleth here. They go quite well together, IMHO. We aren't using OSP here, but a friend has written an article on how to get OSP to work with Shibboleth (https://www.netiq.com/communities/cool-solutions/configuring-idm-4-5s-osp-talk-shibboleth-idp/), so maybe that's an option for you.

I was talking to Brad about this off-list, and apparently there's a change between the OSP in 4.5.2 and 4.5.3 that breaks things:

    From 4.5 through 4.5.2 Shibboleth IDP worked by virtue of the SAML2 support, but in 4.5.3 it breaks
    from a bug.  Since NAM is their only supported IDP, and the bugI found is not a problem in NAM, but
    it is a problem with Shibboleth, they are not considering it a bug that needs to be fixed.

Liam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160215/3c881db8/attachment.html>