Uploaded image for project: 'Shibboleth Discovery Service - Java'
  1. Shibboleth Discovery Service - Java
  2. SDSJ-82

DS should comprehend the new mdui extensions and use them correctly

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 1.1.1
    • Fix Version/s: 1.1.3
    • Labels:
      None

      Description

      Appropriately means

      1) Prefer the <mdui:DisplayName> over <md:OrganizationDisplayName> for IdPs *ONLY*
      2) Make the <mdui:Description> <mdui:Logo> <mdui:InformationURL> and <mdui:PrivacyStatementURL> for the IdPsavailable to the jsp (in addition to the name which is already there)
      3) Make the <mdui:Description> and <mdui:DisplayName> for the SP avaiable to the jsp (this is new function)
      4) Make the <mdui:DiscoHints> available to and hint processing plugins.

      Doing this properly will probably break the jsp "API" (since we want tohave all this stuff localized properly) and so I propose that this be done as a 1.2 or a 2.0 release (alongside all the GUI changes). For a 1.2 we could continue to use the deeply slimy hack which was put in in 1.0 to ease the passage from the OpenSAML1 to OpenSAML2.

      Since we do not want to have to be in lock step with OpenSAML we will do this in three stages.

      1) Put appropriate marshallers and unmarshallers into the DS code.
      2) Add the code to "handle these things appropriately"
      3) When the OpenSAML code release with the new supprot is in place we can remove the old code.

        Attachments

          Activity

            People

            • Assignee:
              rdw Rod Widdowson
              Reporter:
              rdw Rod Widdowson
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated: