Uploaded image for project: 'PicketLink'
  1. PicketLink
  2. PLINK-533

LDAPIdentityStore should dynamically handle mapping of attributes from AttributedType

    Details

    • Type: Feature Request
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: PLINK_2.6.0.CR5
    • Fix Version/s: PLINK_2.7.0.Beta1
    • Component/s: IDM
    • Labels:
      None

      Description

      Actually all properties mapped to LDAP must be available as java properties on target type. It would be great that picketlink LDAPIdentityStore could also handle situation when LDAP mapped property is not available as Java property on target type, but just as attribute. For example:

      User john = new User("john");
      john.setAttribute("foo", "fooValue");
      

      and particular mapping:

       .mapping(User.class)                            
        .objectClasses(userObjectClasses)
        ...
       .attribute("firstName", "cn")
       .attribute("foo", "givenName")
      

      In this case target type "User" has Java property "firstName" so it's mapped normally through this via getFirstName/setFirstName as it's now. In case of "foo" property, which doesn't exist on User, it will be mapped through getAttribute("foo")/setAttribute("foo", VAL)

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                mposolda Marek Posolda
                Reporter:
                mposolda Marek Posolda
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: