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

Expose NameID Format on SloLogoutrequest #420

Conversation

jeffparsons
Copy link
Contributor

Status

?? READY/IN DEVELOPMENT/HOLD

Migrations

NO

Description

Expose NameID Format on SloLogoutrequest.

This is equivalent to the name_id_format (nameid_format) methods on Response class. Clients are likely to need access to this (I did) for the same reasons as they need it on Response.

Equivalent to `name_id_format` (`nameid_format`) on `Response` class.
@@ -1,4 +1,4 @@
<samlp:LogoutRequest Version='2.0' ID='_c0348950-935b-0131-1060-782bcb56fcaa' xmlns:samlp='urn:oasis:names:tc:SAML:2.0:protocol' IssueInstant='2014-03-21T19:20:13'>
<saml:Issuer xmlns:saml='urn:oasis:names:tc:SAML:2.0:assertion'>https://app.onelogin.com/saml/metadata/SOMEACCOUNT</saml:Issuer>
<saml:NameID xmlns:saml='urn:oasis:names:tc:SAML:2.0:assertion'>someone@example.org</saml:NameID>
<saml:NameID xmlns:saml='urn:oasis:names:tc:SAML:2.0:assertion' Format='urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress'>someone@example.org</saml:NameID>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you create a new xml instead modify it?
slo_request.xml is related to slo_request.xml.base64 and slo_request_deflated.xml.base64

Use a separate XML file for SloLogoutrequest#name_id_format tests.
Apparently there are various representations of the file that I modified
that are all supposed to be equivalent.
@pitbulk pitbulk merged commit 843ade7 into SAML-Toolkits:master Nov 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants