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

Refuso nell'avviso n. 3: PartialLogout #17

Open
alranel opened this issue Dec 27, 2017 · 1 comment
Open

Refuso nell'avviso n. 3: PartialLogout #17

alranel opened this issue Dec 27, 2017 · 1 comment
Labels
bug to be fixed in official spec This fix should be applied to the official upstream regulation

Comments

@alranel
Copy link
Member

alranel commented Dec 27, 2017

Nell'avviso n. 3 relativo al Single Logout è presente questo passaggio:

Viceversa nel caso in cui si verificasse una condizione di partial logout il gestore dell’identità, se in condizione di poterlo fare, dovrà notificare tale esito al fornitore di servizi richiedente, riportando nella response (cfr par. 2.2) i seguenti status code:

  • status code: urn:oasis:names:tc:SAML:2.0:status:Requester
  • sub status: urn:oasis:names:tc:SAML:2.0:PartialLogout

Tuttavia il valore corretto previsto dalle specifiche SAML OASIS è urn:oasis:names:tc:SAML:2.0:status:PartialLogout.

@alranel alranel added the bug label Dec 27, 2017
@alranel
Copy link
Member Author

alranel commented Dec 28, 2017

Inoltre nelle specifiche SAML OASIS (righe 2631-2633) è scritto:

If the session authority successfully terminates the principal's session with respect to itself, then it MUST respond to the original requester, if any, with a <LogoutResponse> message containing a top-level status code of urn:oasis:names:tc:SAML:2.0:status:Success.

Questa indicazione sembra in contraddizione con il passaggio dell'avviso n. 3 sopra riportato. Infatti lo status :Requester è descritto da OASIS come segue (riga 1639):

The request could not be performed due to an error on the part of the requester.

e ancora (righe 1513-1515):

If a SAML responder deems a request to be invalid according to SAML syntax or processing rules, then if it responds, it MUST return a SAML response message with a <StatusCode> element with the value urn:oasis:names:tc:SAML:2.0:status:Requester.

@alranel alranel added the to be fixed in official spec This fix should be applied to the official upstream regulation label Jul 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug to be fixed in official spec This fix should be applied to the official upstream regulation
Projects
None yet
Development

No branches or pull requests

2 participants