Search results

| <nowiki>search query to get the users ldap dn ,@USER@ will be replaced by the username </nowiki> ...ntries don't get invalidated, since the cache may not be deterministic for LDAP contacts. Therefore, the properties 'MaxObjects', 'MaxMemoryIdleTimeSeconds

| <nowiki>search query to get the users ldap dn ,@USER@ will be replaced by the username </nowiki> ...ntries don't get invalidated, since the cache may not be deterministic for LDAP contacts. Therefore, the properties 'MaxObjects', 'MaxMemoryIdleTimeSeconds

| <nowiki>search query to get the users ldap dn ,@USER@ will be replaced by the username </nowiki> ...ntries don't get invalidated, since the cache may not be deterministic for LDAP contacts. Therefore, the properties 'MaxObjects', 'MaxMemoryIdleTimeSeconds

|Open-Xchange provided a new LDAP Contact Storage Integration Bundle. Open-Xchange discontinued support for t

| <nowiki>search query to get the users ldap dn ,@USER@ will be replaced by the username </nowiki> ...ntries don't get invalidated, since the cache may not be deterministic for LDAP contacts. Therefore, the properties 'MaxMemoryIdleTimeSeconds', 'MaxLifeSec

| <nowiki>search query to get the users ldap dn ,@USER@ will be replaced by the username </nowiki> ...es don&#39;t get invalidated, since the cache may not be deterministic for LDAP contacts. Therefore, the properties &#39;MaxMemoryIdleTimeSeconds&#39;, &#3

| <nowiki>search query to get the users ldap dn ,@USER@ will be replaced by the username </nowiki> ...es don&#39;t get invalidated, since the cache may not be deterministic for LDAP contacts. Therefore, the properties &#39;MaxMemoryIdleTimeSeconds&#39;, &#3

| <nowiki>search query to get the users ldap dn ,@USER@ will be replaced by the username </nowiki> ...es don&#39;t get invalidated, since the cache may not be deterministic for LDAP contacts. Therefore, the properties &#39;MaxMemoryIdleTimeSeconds&#39;, &#3

| <nowiki>search query to get the users ldap dn ,@USER@ will be replaced by the username </nowiki> ...es don&#39;t get invalidated, since the cache may not be deterministic for LDAP contacts. Therefore, the properties &#39;MaxMemoryIdleTimeSeconds&#39;, &#3

| <nowiki>search query to get the users ldap dn ,@USER@ will be replaced by the username </nowiki> ...es don&#39;t get invalidated, since the cache may not be deterministic for LDAP contacts. Therefore, the properties &#39;MaxMemoryIdleTimeSeconds&#39;, &#3

| <nowiki>search query to get the users ldap dn ,@USER@ will be replaced by the username </nowiki> ...es don&#39;t get invalidated, since the cache may not be deterministic for LDAP contacts. Therefore, the properties &#39;MaxMemoryIdleTimeSeconds&#39;, &#3

| <nowiki>search query to get the users ldap dn ,@USER@ will be replaced by the username </nowiki> ...es don&#39;t get invalidated, since the cache may not be deterministic for LDAP contacts. Therefore, the properties &#39;MaxMemoryIdleTimeSeconds&#39;, &#3

| <nowiki>search query to get the users ldap dn ,@USER@ will be replaced by the username </nowiki> ...es don&#39;t get invalidated, since the cache may not be deterministic for LDAP contacts. Therefore, the properties &#39;MaxMemoryIdleTimeSeconds&#39;, &#3

| <nowiki>search query to get the users ldap dn ,@USER@ will be replaced by the username </nowiki> ...es don&#39;t get invalidated, since the cache may not be deterministic for LDAP contacts. Therefore, the properties &#39;MaxMemoryIdleTimeSeconds&#39;, &#3

| <nowiki>search query to get the users ldap dn ,@USER@ will be replaced by the username </nowiki> ...es don&#39;t get invalidated, since the cache may not be deterministic for LDAP contacts. Therefore, the properties &#39;MaxMemoryIdleTimeSeconds&#39;, &#3

| <nowiki>Search query to get the users ldap dn ,%s will be replaced by the username. | <nowiki> ldap attribute containing the OX Login name</nowiki>

| directly store provided pwHash into userPassword attribute of matching ldap entry. Note: Input will be validated against valid mechanisms.