Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

I'm comparing different STS's for claims based authentication and am trying when it's appropriate to use each one.

It appears that ADFSv2 should be used in all Windows Environments. Ping and Siteminder are more for the Unix side... although a sales rep said Ping was better for Windows, I didn't really understand "why"

Any comparative information is much appreciated!

share|improve this question
add comment

2 Answers 2

We are in the middle of doing SSO where I'm at right now. We couldn't get Site Minder to let us pay for a developer license; they literally didn't return the numerous calls we made begging to use their software (one of our clients was using it and we figured it would be the easiest path).

We went with Ping Identity's Pingfederate product (or is it the other way around)?

The documentation isn't amazing, but it's working for us. When you can get past first-level support, they have been very helpful and getting us going. Your application will be dependent upon their APIs, but your application will also support numerous open standards for SSO. They also have consulting available to do the heavy lifting if you have the budget.

share|improve this answer
    
Do you mind me dropping you an email regarding SSO as it is warping my brain? If you drop me an email at peanutsmonkey@gmail.com, I'll reply in response. –  PeanutsMonkey Apr 24 '12 at 9:17
add comment

Which STS you choose should really be based on your near term as well as strategic requirements. For the record, PingFederate works very well in a Windows environment. Ping Identity actually has many, many Windows IT shops successfully deploying PingFederate. So whether or not you are a Windows shop shouldn't be the sole determiner.

You might want to consider the range of applications that need to integrate into your SSO ecosystem. That includes both identity management products such as Active Directory, OAM, SiteMinder, as well as relying applications. Your SSO solution should be selected based on those integration needs.

Ping Identity did a ton of work this summer to ensure that we are well aligned with ADFSv2/WCF/WIF environments. Along with that, PingFederate provides very rich integration into many existing identity management products, directories, and databases. There are also several language kits for embedding SAML, WS-Trust, and WS-Federation single sign-on into .Net, Java, and PHP.

Another key differentiator between PingFederate and other SSO/Federation products is the speed and ease with which a PingFederate ecosystem can be established. Generally, PingFederate customers get up in running in hours or day. Not weeks or months.

Also note that Ping Identity offers a cloud based solution, PingConnect, for those companies that are not ready or don't need to invest in a full scale on premise SSO/Federation solution.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.