Skip to content

docs: add name and description to example SAML2 backend #393

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

Merged
merged 1 commit into from
Nov 19, 2021
Merged

docs: add name and description to example SAML2 backend #393

merged 1 commit into from
Nov 19, 2021

Conversation

melanger
Copy link
Contributor

These attributes are required to generate valid metadata in combination with required_attributes and/or optional_attributes.

Without these attributes specified (and there is no hint in pysaml2 docs about this either), the generated metadata contains empty <ns0:ServiceName xml:lang="en" /> inside AttributeConsumingService, which is invalid. This was probably the cause of pysaml2#345

@melanger
Copy link
Contributor Author

Please consider updating the docs as well and/or adding a check for this in code, either here or in pysaml2.

@melanger melanger changed the title docs: add sp.name and sp.description to example SAML2 backend WIP: docs: add sp.name and sp.description to example SAML2 backend Nov 16, 2021
these attributes are required to generate valid metadata in combination with required_attributes and/or optional_attributes
@melanger melanger changed the title WIP: docs: add sp.name and sp.description to example SAML2 backend docs: add name and description to example SAML2 backend Nov 16, 2021
@c00kiemon5ter c00kiemon5ter added the next-release should become part of the next release label Nov 16, 2021
@c00kiemon5ter c00kiemon5ter merged commit 43fd132 into IdentityPython:master Nov 19, 2021
@c00kiemon5ter
Copy link
Member

thank you!

@melanger melanger deleted the patch-3 branch April 1, 2022 11:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
next-release should become part of the next release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants