ory / ory/mocksaml

Add <SingleLogoutService> to IdP metadata?

Open
#1,192 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
168
Forks
54
PR merge metrics
No merged PRs in 30d

Description

Greetings.

I'm not a SAML expert at all but I had to work with a service provider that uses it (for testing purposes). At some point, the system complained that the IdP XML metadata didn't contain a logout URL. Using Copilot to help me out, I basically copied these lines:

<md:SingleSignOnService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect" Location="https://mocksaml.com/api/saml/sso"/>
<md:SingleSignOnService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="https://mocksaml.com/api/saml/sso"/>

... and pasted them below, after changing the element name from SingleSignOnService to SingleLogoutService:

<md:SingleLogoutService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect" Location="https://mocksaml.com/api/saml/sso"/>
<md:SingleLogoutService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="https://mocksaml.com/api/saml/sso"/>

I don't know if that's correct/mandatory/useful? This seems to work with the service provider I'm using though. Is https://mocksaml.com/api/saml/sso receptive to logout SAML messages?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue does not identify a file, test, or entry point. First verify how the IdP metadata is generated and whether SingleLogoutService is required for the reported service provider; confirm whether the advertised endpoint accepts logout SAML messages. Done means the metadata behavior and logout endpoint support are documented or implemented with a clear validation case.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
authentication
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.