Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Special characters are not properly XML-encoded #179

Open
hobzcalvin opened this issue Jan 19, 2017 · 2 comments
Open

Special characters are not properly XML-encoded #179

hobzcalvin opened this issue Jan 19, 2017 · 2 comments
Labels

Comments

@hobzcalvin
Copy link

If my ACS URL is http://foobar.com/saml/connect/?someparam=baz&another=bing the XML generated by the library will be of the form:

<samlp:AuthnRequest
    xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"
    xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"
    ID="ONELOGIN_b59b8f4a13f6f86bb14230429abd724e5fa80c96"
    Version="2.0"
    IssueInstant="2017-01-19T00:32:06Z"
    Destination="https://foobar-dev.onelogin.com/trust/saml2/http-post/sso/123456"
    ProtocolBinding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
    AssertionConsumerServiceURL="http://foobar.com/saml/connect/?someparam=baz&another=bing"
    >
    <saml:Issuer>http://127.0.0.1:8000/</saml:Issuer>
</samlp:AuthnRequest>

which is not valid XML. The & in the ACS URL must be quoted as &amp;

@pitbulk
Copy link
Contributor

pitbulk commented Jan 19, 2017

I will investigate.

@hobzcalvin
Copy link
Author

Thanks @pitbulk. This issue was breaking an integration with CA Single Sign-On which gives up parsing the XML when it sees the unescaped &.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants