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

Consent DisplayFunction localized to the Server locale?

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 3.1.0
    • Fix Version/s: 3.1.1
    • Component/s: Attribute Consent
    • Labels:
      None

      Description

      This is from inspection of the code not from testing.

      I think that AttributeDisplayNameFunction is using the server's locale to render the attribute name, rather than the list of acceptable languages pushed by the browser.

      We should consider changing this to function rather more like the RPUIContext (which takes both the browser languages and the fallback languages into conisderation).

      It appears that this is all configured inside system, but the function itself is inside idp-consent (and hence is implied -api). So I suspect we need another implementation to do the client-aware work.

      Meantime I'll document his velocity property as being a Function<IdpAttribute, String> which gives us wiggle room.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                rdw@iay.org.uk Rod Widdowson
                Reporter:
                rdw@iay.org.uk Rod Widdowson
              • Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 4 hours
                  4h
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 3 hours, 45 minutes Time Not Required
                  3h 45m