11.6.3. Usage Examples
This section will guide you through the basic steps to get an Identity Provider and a Service Provider working using the subsystem configuration.
Download the PicketLink Federation Quickstarts from https://repository.jboss.org/nexus/content/groups/public/org/picketlink/quickstarts/picketlink-quickstarts/2.1.8.Final/picketlink-quickstarts-2.1.8.Final-webapps-jboss-as7.zip.
Extract the file and copy the idp.war and sales-post.war to${JBOSS.HOME.dir}/standalone/deployments.
Open both files (idp.war and sales-post.war) and remove the following configuration files:
-
WEB-INF/picketlink.xml
-
META-INF/jboss-deployment-structure.xml
-
WEB-INF/jboss-web.xml
Important
Don't forget to configure the security domains for both applications.
Open the standalone.xml and add the following configuration for the PicketLink subsystem:
<subsystem xmlns="urn:jboss:domain:picketlink:1.0"> <federation alias="example-federation"> <!-- Identity Provider configuration --> <identity-provider alias="idp.war" security-domain="idp" supportsSignatures="false" url="http://localhost:8080/idp/"> <trust> <trust-domain name="localhost" /> </trust> </identity-provider> <!-- Service Provider configuration --> <service-providers> <service-provider alias="sales-post.war" post-binding="false" security-domain="sp" url="http://localhost:8080/sales-post/" supportsSignatures="false" /> </service-providers> </federation> </subsystem>
To make sure that everything is ok, please start JBoss AS and try to access the sales application. You should be redirected to the idp application.