Single Sign On Integration(SSO)

I was wondering if someone has some experience on integrating a Single Sign On solution with 3rd party service providers, our company plans to integrate with google apps and silk roads, however as I understand the credentials will be sole stored at our Active Directory Server, I would like to know how will the user manipulate his/her password. Any setup instructions or tips for a smooth integration will be well appreciated.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

You need to install Microsoft ADFS 2.0 \ 3.0 server in your on premise Active Directory and need to publish it on internet

Then your applications need to integrated with ADFS server
In applications, you need to configure ADFS as account provider (Identity Provider)
In ADFS, you need to configure applications as a Relying Party

Also you need to set HomeRealmDiscovery on corporate machines, so that whenever user access application url, it will forward that request to your ADFS server for authentication and ADFS will authenticate user with active directory, ideally it will ask user with logon prompt and user has to enter his AD username and password.

U can add ADFS server URL to intranet zone in IE on all client machines so that user will not be get username \ password prompt and it will pickup user existing logon as windows integrated authentication and user will get SSO experience

If you did not add ADFS server URL to intranet zone, user will initially prompted for username and password and that information will get cached on his machine to get kind of SSO experience

You can check your application manual \ settings on how to establish trust with ADFS

Only thing application must be ADFS aware (Claims aware - SAML 2.0 protocol support) because ADFS works on Claims and SAML protocol.

To configure ADFS on windows server
U will get MS documentation as well.

Check below URLs wrt Google Apps

There are numerous posts available on above topics
Allen FalconCEO & Pragmatic EvangelistCommented:
Before you jump through hoops ... are you looking to integrate SSO yourself or are you looking at a third party solution that would provide a single login screen for both Google Apps and Silk Road HR?
jdffAuthor Commented:
I plan to deploy adfs to integrate silkroad ride away but if there is any 3rd party solution to make things easier or to save time, i would consider it. Not very concerned about google apps at the present time since my project needs to move forward with silk road first.
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

If your application is claims aware (Supports SAML), then its not very hard to setup ADFS,
There is one 3rd party product I am aware.
But I don't think its required.
Allen FalconCEO & Pragmatic EvangelistCommented:
I would also look at ClearLogin.
jdffAuthor Commented:
Hi Allen,
I did contact Clearlogin and we'll go for a demo now, if anyone has any other suggestions, please let me know. We are also strongly considering to deploy the solution ourselves as Mahesh has detailed.
MS has done lots of improvements in Windows 2012 R2 ADFS 3.0 by inserting TWO factor authentication and addition of Web Application Proxy role
This role provides you variety of authentication and application publishing methods and also supports ADFS proxy functionality like previous versions
Check below links

Further more they have released more features as part of Windows Server next version Technical Preview
jdffAuthor Commented:
We have a 2008 STD R2 domain controller, should I deploy a secondary domain controller with Windows 2012 for this purpose?
For AD FS to operate successfully, domain controllers in either the account partner organization or the resource partner organization must be running Windows Server 2003 SP1, Windows Server 2003 R2, Windows Server 2008, or Windows Server 2012 / 2012 R2

AD FS does not require schema changes or functional-level modifications to AD DS.

Most AD FS features do not require AD DS functional-level modifications to operate successfully. However, Windows Server 2008 domain functional level or higher is required for client certificate authentication to operate successfully if the certificate is explicitly mapped to a user's account in AD DS.
I don't think this is your case, so any DC with 2003 SP1 and above will work

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Google Apps

From novice to tech pro — start learning today.