Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.

Changes between Version 1 and Version 2 of Ticket #2587


Ignore:
Timestamp:
09/30/11 11:22:33 (13 years ago)
Author:
jmoore
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #2587

    • Property Milestone changed from Unscheduled to OME-5.0
    • Property Summary changed from Have LdapPasswordProvider re-run query on all password lookups to LDAP: remove DN from OMERO DB.
  • Ticket #2587 – Description

    v1 v2  
    1 Currently, LdapPasswordProvider is only using the dn for checking a users password. In addition, the query with filters that is initially used to look the user should be used. (In fact, we could stop storing the DN of the user, and only store a flag "in_ldap") 
     1Before 4.3.2, LdapPasswordProvider Was only using the dn for checking a users password. Starting with 4.3.2, the query with filters that is initially used to look the user should be used, but the DN is still being stored. We could stop storing the DN of the user, and only store a flag "in_ldap" (or perhaps the connection information for the case of multiple server support). 
    22 
    3 Note: some of this functionality was added as #6248 in 4.3.2. Removing the DN to prevent synchronization errors, etc. still remains undone. 
     3See #6248 (4.3.2) for the work to check on every login.. Removing the DN to prevent synchronization errors, etc. still remains undone. 

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.13459 sec.)

We're Hiring!