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

Consent screen displays attributes with Empty (NULL) value

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.2.1
    • Fix Version/s: 3.3.0
    • Component/s: Attribute Consent
    • Labels:
      None
    • Environment:

      RHEL6
      OpenJDK 1.7
      Tomcat7
      IdP 3.2.1
      MySQL 5.1

    • Operating System:
      Multiple
    • Java Version:
      Oracle Java 7
    • Servlet Container:
      Apache Tomcat 7

      Description

      Hi,

      I am looking at upgrading our Virtual Home IdP to IdP 3.2.1.

      We use a MySQL database as the backend.

      I have learned from the release notes that IdP 3.2.1 RelationalDatabaseConnector returns EmptyAttributeValue instances in place of MySQL NULLs. In IdP 2.4.x, these were silently discarded and the attributes had an empty set of values.

      The consent module in 3.2.1 does not properly filter out the EmptyAttributeValues and displays such attributes on the consent screen - I get this (the attribute names come from resolver:DisplayName elements I have in my attribute-resolver.xml):

      Organisational Unit 	NULL_VALUE
      Business postal address 	NULL_VALUE
      Business phone number 	NULL_VALUE 
      

      I think the correct behavior would be to not display attributes that only have empty values (and do not get included in the AttributeStatement).

      Cheers,
      Vlad

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              tzeller@shibboleth.net Tom Zeller
              Reporter:
              tuakiriadmin-vmencl@virtualhome.tuakiri.ac.nz Vladimir Mencl
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: