Uploaded image for project: 'Identity Provider'
  1. Identity Provider
  2. IDP-1740

Configurable shibboleth.OutgoingSOAPBindings

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Answered
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Configuration, Logout, SAML2
    • Labels:
      None
    • Operating System:
      Linux
    • Java Version:
      Debian OpenJDK 11
    • Servlet Container:
      Apache Tomcat 8.5

      Description

      When testing Logout on a 4.0.1 IdP without backchannel support, I saw the IdP PropagateLogout flow was sending the Logout requests to SPs via the Artifact profile, unaware the IdP does not have an endpoint to resolve the artifact.

      I found I could get Logout working by commenting the Artifact profile out in shibboleth.OutgoingSOAPBindings in system/conf/saml-binding-config.xml - but that is a system/ file.

      I think this is a legitimate use case (Logout with no back-channel) and it should be possible to stop the IdP from sending logout requests via the artifact profile - with just standard config, without touching system/ files.

      Thanks a lot in advance for looking into this!

      Cheers,
      Vlad

        Attachments

          Activity

            People

            Assignee:
            cantor.2@osu.edu Scott Cantor
            Reporter:
            tuakiriadmin-vmencl@virtualhome.tuakiri.ac.nz Vladimir Mencl
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: