PicketLink 302 Moved Temporarily Posting to <ServiceUrl>

Solution In Progress - Updated -

Issue

We have been using Picketlink SSO and everything has been working in Jboss 6.0 and Jboss 6.1. However after upgrading to Jboss 6.1.1 when the SSO goes to Post the SAMLResponse back to the param in the picketlink.xml we are getting a 302 Moved Temporarily.

Jboss 6.1.1 is using PicketLinke 2.1.6.3 while Jboss 6.1 was using PicketLink 2.1.6. If I take my 6.1.1 and remove the 2.1.6.3 modules and replace them with the ones from Jboss 6.1 everything is back to working.

Is there something I am missing or is this a defect in PicketLink 2.1.6.3.

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6.1.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.