06 Apr, 2007

3 commits


05 Apr, 2007

2 commits


04 Apr, 2007

2 commits


03 Apr, 2007

3 commits

  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1563 41b1ffd8-f28e-4786-ab96-9950f0a78031
    el_kaboing
     
  • different kinds of virtual attributes.  This commit addresses the following
    issues:
    
    - Issue #1475 -- General virtual attribute support
    - Issue #539  -- Support for the isMemberOf virtual attribute
    - Issue #544  -- Support for the entryDN virtual attribute
    - Issue #1056 -- Support for the subschemaSubentry virtual attribute
    - Issue #85   -- Support for the real attributes only control
    - Issue #86   -- Support for the virutal attributes only control
    
    In general, virtual attribute support consists of three parts:
    
    - An implementation of the org.opends.server.api.VirtualAttributeProvider
      class, which provides the logic for actually generating the values, providing
      support for various kinds of matching, and potentially the ability to process
      search operations involving the virtual attribute that might not otherwise be
      indexed.
    
    - The org.opends.server.types.VirtualAttribute class, which is a subclass of
      org.opends.server.types.Attribute and uses the virtual attribute provider to
      generate its values.
    
    - The org.opends.server.types.VirtualAttributeRule class, which associates a
      virtual attribute provider with a given attribute type, and also with a set
      of criteria that controls which entries should have the attribute.
    
    
    The virtual attribute rule currently supports the following criteria that can
    be used to decide whether an entry should have a given virtual attribute:
    
    - Zero or more base DNs.  If any base DNs are provided, then any entry which
      falls below one of those base DNs will be a candidate to get the virtual
      attribute.  If no base DNs are provided, then DIT location will not be taken
      into account when determining eligibility.
    
    - Zero or more group DNs.  If any group DNs are provided, then any entry that
      belongs to one of the specified groups will be a candidate to get the virtual
      attribute.  If no group DNs are provided, then group membership will not be
      taken into account when determining eligibility.
    
    - Zero or more search filters.  If any filters are provided, then any entry
      that matches one of the specified filters will be a candidate to get the
      virtual attribute.  If no filters are provided, then the contents of the
      entry will not be taken into account when determining eligibility.
    
    
    In addition to that criteria, virtual attribute rules define a conflict
    behavior, which controls how to behave when the entry already has one or more
    real values for the attribute.  The conflict behavior can be
    "real-overrides-virtual" (to only show the real values),
    "virtual-overrides-real" (to only show the virtual values), or
    "merge-real-and-virtual" (to show both real and virtual values).
    
    The virtual attribute implementation has been designed so that there should be
    virtually no performance impact unless the attribute needs to be returned to
    the client or it is referenced in a search filter, and you can completely
    disable virtual attributes if you don't need them.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1562 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@1561 41b1ffd8-f28e-4786-ab96-9950f0a78031
    coulbeck
     

02 Apr, 2007

2 commits


29 Mar, 2007

2 commits

  • properly (it appears to reference classes that are not in the repository).
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1541 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • These changes implies :
    - new messages in the protocol and their tests
    - new logic in the SynchronizationDomain to handle the import and the export
    - new logic in the Changelog server to forward the messages for this feature
    - new tasks to trigger the total update
    Object class
    1.3.6.1.4.1.26027.1.2.91: ds-task-initialize-from-remote-replica
    1.3.6.1.4.1.26027.1.2.92: ds-task-initialize-remote-replica
    Attributes - same for both tasks :
    1.3.6.1.4.1.26027.1.1.332: ds-task-initialize-domain-dn
    1.3.6.1.4.1.26027.1.1.333: ds-task-initialize-replica-server-id
    1.3.6.1.4.1.26027.1.1.334: ds-task-unprocessed-entry-count
    1.3.6.1.4.1.26027.1.1.335: ds-task-processed-entry-count
    - a bunch of unit tests to tests the export and the import, on the producer
    side and on the consumer side
    
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1539 41b1ffd8-f28e-4786-ab96-9950f0a78031
    pgamba
     

28 Mar, 2007

3 commits


27 Mar, 2007

2 commits

  • git-svn-id: https://svn.forgerock.org/opendj/trunk@1526 41b1ffd8-f28e-4786-ab96-9950f0a78031
    coulbeck
     
  • manager provider and trust manager provider values if either SSL or StartTLS is
    enabled.  Previously, if a key/trust manager provider value was provided, then
    the server would require it to refer to a valid enabled key/trust manager
    provider, even if it wouldn't be used.  Also, add a new check to ensure that if
    SSL or StartTLS is enabled, then a valid key manager provider and trust manager
    provider must have been configured for that connection handler.
    
    OpenDS Issue Number:  1294
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1525 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

26 Mar, 2007

4 commits

  • - A validator which enforces a restriction that passwords must have at least a
      specified number of unique characters (issue #1219).
    
    - A validator which enforces a restriction that passwords may not have any
      character which appears more than a specified number of times in a row (issue
      #1220).
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1520 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • … called PatternDN.  This will make it easier to rewrite the pattern matching to actually fix the related TODOs.  I also have added unit tests for the DN wildcard examples in the DSEE documentation (three of which fail and are commented out for the time being).
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1516 41b1ffd8-f28e-4786-ab96-9950f0a78031
    coulbeck
     
  • import/export/backup/restore interface to get notifications of import
    and restore and then resynchronize the server approprietely.
    
    It was necessary to move the call to the import and restore listeners in the
    import and restore task implementations because these calls were made too
    late and the backend that were given in parameter were already invalid when
    the listeners are called.
    
    This code is already covered by the ReSyncTest.java
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1512 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     
  • is acceptable based on how similar it is to the user's current password.  The
    processing uses the Levenshtein Distance algorithm to determine the number of
    changes required to convert the current password into the new password (a
    change may be either inserting a new character, removing an existing character,
    or replacing an existing character).
    
    Contributed By:  Ales Novak
    OpenDS Issue Number:  340
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1511 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

25 Mar, 2007

2 commits


24 Mar, 2007

1 commit


23 Mar, 2007

2 commits


22 Mar, 2007

4 commits


21 Mar, 2007

4 commits


20 Mar, 2007

4 commits