how to Configure openam as Identity provider(IdP) to test SAML based SSO

Question

I am trying to configure openam as Identity provider to test my SAML based service provider application.

I have searched a lot and saw documentation of openam. There are lots of thing supported by openam which probably I do not need at this moment. I don't wish to read whole documentation which will take lot of time reading things I do not want to test right now. I even saw chatpet 9 "Managing SAML 2.0 SSO" at http://docs.forgerock.org/en/openam/10.0.0/admin-guide/index/index.html But it requires lot of things to be configured before this.

Is there any quick start guide to test it as saml based IdP?

EDIT

Not a quick, detailed is also fine. But I want OpenAm as Identity provider. SP is an application hosted on Jetty which we have developed. Also tell me what changed do I have to make on SP like what urls of application should respond with what.

Answer 1

There is no one-fits-all answer to your question really. Setting up SAMLv2 Federation largely depends on the actual SP implementation, some SPs can work with SAML metadata, some don't.. The simplest way to set up federation between two OpenAM instances for reference would be something like:

• Create Hosted IdP wizard on node1
• Create Hosted SP wizard on node2
• On both nodes remove the persistent NameID-Format, so both will have transient at the top of the list
• Register Remote SP wizard on node1, with URL: node2/openam/saml2/jsp/exportmetadata.jsp
• Register Remote IdP wizard on node2, with URL: node1/openam/saml2/jsp/exportmetadata.jsp
• On node2 in the Hosted SP setting set the transient user to "anonymous"

After all this you can test Federation by using:

• /openam/spssoinit?metaAlias=/sp&idpEntityID=node1_entityid on node2
• /openam/idpssoinit?metaAlias=/idp&spEntityID=node2_entityid on node1

I've used the default metaAlias values, but those should be visible on the console pages. Similarly by downloading the metadata you can see the actual entity IDs for the given entities.

Based on this, you should see now that with an OpenAM IdP you could at least test SAML support using the idpssoinit URL (if your SP supports unsolicited responses), but from the other way around it pretty much depends on your SP implementation how you need to actually trigger a SAML authentication.