Uploaded image for project: 'OpenAM'
  1. OpenAM
  2. OPENAM-11627

DeviceIdSave does not work with User alias search ( if the username in sharedstate map does not 'match' the search attribute of the data store)

    XMLWordPrintable

    Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Duplicate
    • 13.5.1, 14.1.1
    • None
    • authentication
    • Rank:
      1|hzuk3b:
    • Sprint 2017.14 Curie
    • No
    • Yes
    • No
    • Yes and I used the same an in the description

      Description

      Bug description

      This is more of less the same as OPENAM-10971 and OPENAM-11115 where the issue is that if the IdRepo search attribute and naming attribute is differen, and even if the user search alias is set to the "naming" attribute, the deviceidSave will not save the profile

      amAuthDeviceIdSave:08/28/2017 09:30:01:060 AM SGT: Thread[http-nio-8080-exec-5,5,main]: TransactionId[18fd9666-44cd-4bfa-8f6b-c4cacb16ba56-811]
      ERROR: Cannot get User's Device Print Profiles attribute. java.lang.NullPointerException
      

      How to reproduce the issue

      Details steps outlining how to recreate the issue (remove this text)
      1. Setup a realm
      2. Setup the realm datastore to use naming=mail, search=uid
      and add a user search alias=mail
      3. Setup a chain

      • DataStore
      • DeviceIdMatch (optional)
      • DeviceIdSave
        4. Add/Change the demo user to have mail: demo@example.com
        5. Login to the realm as demo@example.com
      Expected behaviour
      After login, the uid=demo ldap entry should have the devicePrintProfile and there previous device profile should be found
      
      Current behaviour
      ERROR: Cannot get User's Device Print Profiles attribute. java.lang.NullPointerException  seen in Authentication logs
      
      and the uid=demo entry does not have devicePrintProfile entry saved.
      

      Work around

      DeviceIdSave does not work using userSearchAlias so it relies currently on the default search attribute of the datastore profile.

      Code analysis

      The same fix needed from OPENAM-10971 and OPENAM-11115 to have getIdentity search with userSearchAlias too.

        Attachments

          Issue Links

            Activity

              People

              dipu.seminlal Dipu Seminlal
              chee-weng.chea C-Weng C
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: