I'm implementing a SAML 2.0 Service Provider and need to install a SAML 2.0 Identity Provider for testing. Given this need, the Identity Provider should ideally be free (or have a trial period) and be easy to set up and configure.
I'm looking for basic single sign on and single log out functionality.
I've tried Sun Opensso Enterprise. The price is right, but so far it's been a nightmare to configure. Also, its error messaging and logging leaves a lot to be desired and I'm often troubleshooting an issue that basically boils down to a misconfiguration or a counterintuitive default setting.
SAML 2.0 (Security Assertion Markup Language) is an open standard created to provide cross-domain single sign-on (SSO). In other words, it allows a user to authenticate in a system and gain access to another system by providing proof of their authentication.
Test to ensure the SAML configuration between your SP tenant and IdP tenant works. Go to Dashboard > Authentication > Enterprise and select SAML. Locate the SAML connection you created, and select its Try arrow icon.
SAML 2.0 was introduced in 2005 and remains the current version of the standard. The previous version, 1.1, is now largely deprecated.
Security Assertion Markup Language (SAML) is an open standard that allows identity providers (IdP) to pass authorization credentials to service providers (SP). What that jargon means is that you can use one set of credentials to log into many different websites.
What problems are you having configuring OpenSSO? I found OpenSSO to be the easiest setup!
My notes on getting the basic IDP up and running are below - hopefully they help you get up and running.
Michael
I've found that the best (i.e. most painless) way is...
I've used the following as my setup steps (I use OpenSSO build 7):
The instructions above are based on http://developers.sun.com/identity/reference/techart/opensso-glassfish.html
You've now got your basics up and running. Create a subrealm under / called users, and create an account or two in there.
Now prep your SP metadata. Don't put too much in your metadata to start with - keep it simple.
In the default page of the GUI, choose to create a hosted IDP. This is a pretty basic workflow. You should specify your /users realm and choose to use the test key alias for signing. The circle of trust you create can be called petty much anything.
When you complete the workflow you'll be asked if you want to import metadata for an SP - say yes and choose to import from your prepared metadata file.
At this stage you should be pretty much set up.
You'll want to grab your IDP metadata next. There are a few ways to do this. You could use "http://servername:8080/opensso/ssoadm.jsp?cmd=export-entity" or "http://servername:8080/opensso/saml2/jsp/exportmetadata.jsp?realm=/users".
... and that's pretty much it for setup.
If you run into issues interoperating with OpenSSO you can look in the OpenSSO data directory (~/opensso by default). There's debugging and logging information in the subdirectories under there. You can cross reference that information with the OpenSSO Wiki, which has some pretty good troubleshooting information.
Instead of installing and configuring an IdP you can use a hosted test platform such as TestShib or OpenIdP. Both work along the same lines but OpenIdP requires you to register.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With