We're updating the issue view to help you get more done. 

Missing namespace breaks SamlService functionality

Description

We recently integrated CAS with our hosted e-mail filtering service provider, Postini, using the SAML 1.1 pull process. Their Request document does not include the "samlp:" namespace prefix on the "AssertionArtifact" tag. This causes SamlService.createServiceFrom(...) to break, in that it's parsing the xml as a string, looking for "<samlp:AssertionArtifact>" and "</samlp:AssertionArtifact>". I don't know whether the namespace is strictly required, but CAS could be made more resilient if it parsed that tag using a method that made the "samlp:" prefix optional.

Environment

None

Status

Assignee

ScottS

Reporter

John Pile

Labels

None

Estimated End Date

None

Audience

None

Components

Fix versions

Affects versions

3.4.3.1

Priority

Major