Hello,

SAML is one of those 'standards' that isn't entirely followed by each vendor. We've integrated SSO Plugin with a few different types of SAML Identity Provider, ie ADFSv2, Ping Federate, Symphony Identity Manager, and a Juniper device. Each one has required some level of engineering effort.

For example, some IDPs only support a single 'target' URL (ie http://host/arsys/home) through a single service provider configuration, hence one has problems when you may want to support another entry point (ie http://host/arsys/forms/*).

Others require slightly oddly formed HTTP requests, which OpenSSO (probably) isn't going to support out of the box.

SAML is also a very high level description of the problem: different SAML profiles exist (POST/Redirect/Artifact) and different ways to deploy the profiles, ie SP -> POST -> IDP -> Artifact -> SP, or SP -> Artifact -> IDP -> Artifact -> SP. (Have a read of the SAML2 Wiki page.)

While AtriumSSO/OpenSSO8 has "supported" SAML for years, it doesn't mean it'll actually work or BMC can deploy/support it. OpenSSO aspired to be the "we support everything" solution and the world moved on. Ping Identity are the current cool kids on the block with respect to a SAML IDP/SP (the Ping Federate product). I've used it a few times and while it really does seem to have a feature for everything, it can be a little complicated.

When someone asks JSS if we support SAML IDP X, unless we've done it before, we do our homework to ensure it'll work. I would expect any other vendor to do exactly the same.

And when you've deployed your SAML solution, what happens when users don't exist in ITSM? It's another one of those issues people tend to forget when deploying an SSO solution. Authenticating a user who doesn't exist in ITSM is of no use to anyone.

On the subject of BMC AREA LDAP: One has to be careful with respect to multiple un-trusted third parties because sending usernames and passwords for company X to company Y is considered less than secure. It is however perfectly adequate in a single organisation.


John

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"

Reply via email to