Uploaded image for project: 'Shibboleth SP - C++'
  1. Shibboleth SP - C++
  2. SSPCPP-528

AttributeQuery Handler

    XMLWordPrintable

    Details

    • Operating System:
      Multiple
    • CPU Type:
      Multiple
    • C/C++ Compiler:
      Multiple
    • Web Server:
      Multiple

      Description

      This is a proposal to add a handler like this in Shibboleth:

      <Handler type="AttributeQuery" Location="/AttributeQuery" acl="127.0.0.1"/>

      This handler could be accessed using more or less the same parameters as the arguments of the resolvertest binary. E.g. /Shibboleth.sso/AttributeQuery?nameId=1234asdd&entityId=https://example.org/idp/shibboleth&protocol=SAML2&nameIdFormat=urn:oasis:names:tc:SAML:2.0:nameid-format:persistent

      The SP - provided the acl allows ist - then would make an attribute query to the given Identity Provider and return the attributes (similar format like for the Session handler) or an error message.

      Such a handler would allow to easier check whether a user still has an account (orphan checking) at an Identity Provider and it also would provide a useful mean to update a user's data without any interaction by the user himself.

      Using the resolvertest currently is not a suitable option because it is very slow (>10s per request beacause it loads the whole config) and because it probably was not meant for this job.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              cantor.2@osu.edu Scott Cantor
              Reporter:
              wkiyxkscr4bax/2pq5dvxwse0ei=@https://aai-logon.switch.ch/idp/shibboleth Lukas Haemmerle
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 6 hours
                  6h