Am Tue, 25 Feb 2014 18:24:14 -0300
schrieb Italo Valcy italova...@gmail.com:
Hello Dieter,
On Tue, Feb 25, 2014 at 5:05 PM, Dieter Klünter die...@dkluenter.de
wrote:
No, syncrepl (consumer) does not reqire operational attributs. Only
if the ldap backend is also defined as syncprov
On Wed, Feb 26, 2014 at 12:26:28PM +0800, saurabh ohri wrote:
Hi all,
I am new to openldap and i manage dto install and configure the same. My
linux client is working well but not able to authenticate windows and mac
clients.
Have been trying since past 2 days by google and other posts
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/26/2014 05:26 AM, saurabh ohri wrote:
Hi all,
I am new to openldap and i manage dto install and configure the
same. My linux client is working well but not able to authenticate
windows and mac clients.
Have been trying since past 2 days
Hi Italo
On Tue, Feb 25, 2014 at 2:08 AM, Italo Valcy italova...@gmail.com wrote:
Dear all,
I`m trying to setup replication from OpenLDAP to Fedora 389 DS.
Honestly I don't know the actual state of this implementation, but I
suggest you have a look at:
- the changelog of 389DS 1.3.2.2 [1]
-
Hi,
the accesslog in my production environment is growing quite large which makes
backing it up challenging.
The reason is that there are plenty of accesslog entires which originate from
slapo-ppolicy (users who can't remember their
passwords):
dn:
Thanks Dennis. You ate right the problem is not related to ldap but was looking
for help against it.
I am able to have successful authentication from ldap on both mac and windows
after trying 50 combinations of configuration
But finally it worked and it our effort paid.
Thanks again and
Thanks matthijs, I was able to make ldap work on Mac and windows finally.
Sent from my iPhone
On 26 Feb 2014, at 4:17 pm, l...@grootstyr.eu wrote:
On Wed, Feb 26, 2014 at 12:26:28PM +0800, saurabh ohri wrote:
Hi all,
I am new to openldap and i manage dto install and configure the same.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Have a look at the shadow* attributes from the shadowAccount class.
Those should help you enforcing password related stuff. For self
changes of passwords use an ACL like:
access to attrs=userPassword
by self write
by anonymous auth
Hello guys,
Thanks for the replies! I'll take a look at each suggestion and give you a
reply soon.
Regards, Italo.
--
Saudações,
Italo Valcy :: http://wiki.dcc.ufba.br/Main/ItaloValcy
Jefferson Davis wrote:
So I've read, however, there is very little documentation on
implementation, at least that I've been able to find.
There are tons of information about nis, rf2307 and/or rfc207bis.
However it is easy to search but often hard to find.
So before you search the web, try
Hi,
I know that openldap usage behaviour is case insensitive.
In my case a client use ldap attribute values in a case sensitive way.
I've noticed that the memberOf value is created by the overlay using the
DN case used in the query and not the DN case read from the database, I
mean:
dn:
Matteo Perego wrote:
Hi,
I know that openldap usage behaviour is case insensitive.
False. OpenLDAP conforms to the schema. If an attribute is defined to be
case-insensitive in the schema, then it will be treated as such. If it is
defined to be case-sensitive, that will also be done.
In my
Am Mittwoch, 26. Februar 2014 schrieb Jefferson Davis:
Sorry to be dense, but it appears I create my schema file from the
attribute definitions in the RFC, is that correct?
Yes
--
Harry Jede
Howard Chu wrote:
Matteo Perego wrote:
Hi,
I know that openldap usage behaviour is case insensitive.
False. OpenLDAP conforms to the schema. If an attribute is defined to be
case-insensitive in the schema, then it will be treated as such. If it is
defined to be case-sensitive, that will
Hi Denis,
I did following steps in order to get the password policy work, still nothing
is working.
1) In my slapd.conf file added below lines:
# Password Policy Configuration
overlay ppolicy
ppolicy_default cn=default,ou=Policies,dc=j,dc=example,dc=com
ppolicy_use_lockout
15 matches
Mail list logo
