Description of problem: In EAP 6.3.x as SP, you can access the SP resource with an alias hostname other than the hostname specified in <ServiceURL/> in picketlink.xml. In EAP 6.4.x, Since the fix for PLINK-680 [1] is applied, Accessing with an alias hostname causes the "Invalid destination" error. Please make <ServiceURL/> store multiple destinations. [1] https://issues.jboss.org/browse/PLINK-680 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
The fix that resulting in this BZ was required by the SAML2 specification, so this would be an RFE not a bug. Closing out.