Ok, might be something having to do with IPA. I’ll play more with it.
Thanks!!
Sergei
> On Aug 17, 2018, at 4:51 PM, Mark Reynolds wrote:
>
>
>
> On 08/17/2018 04:59 PM, Sergei Gerasenko wrote:
>> Hi Mark,
>>
>> I have a test instance of 389-ds running on a vm. I’ve tried updating the
>>
On 08/17/2018 04:59 PM, Sergei Gerasenko wrote:
Hi Mark,
I have a test instance of 389-ds running on a vm. I’ve tried updating
the aci like this:
dn: cn=mapping tree,cn=config
changetype: modify
replace: aci
aci: (targetattr = "cn || nsuniqueid || createtimestamp || description
|| entryusn
Hi Mark,
I have a test instance of 389-ds running on a vm. I’ve tried updating the aci
like this:
dn: cn=mapping tree,cn=config
changetype: modify
replace: aci
aci: (targetattr = "cn || nsuniqueid || createtimestamp || description ||
entryusn || modify
timestamp || nsds50ruv || MORE STUFF)(tar
On 08/17/2018 02:07 PM, Sergei Gerasenko wrote:
Thanks, Mark. I think I will have to do this directly in dse.ldif by
stopping the server, editing the ldif and starting it again?
In this case that would be the easiest way to edit this aci, but
typically I would suggest using ldapmodify instead.
Thanks, Mark. I think I will have to do this directly in dse.ldif by stopping
the server, editing the ldif and starting it again? Looks like there’s already
an ACI for it, but it doesn’t include those attrs. So I think I will need to
add them. Currently it looks like this:
dn: cn=mapping tree,c
On 08/17/2018 11:51 AM, Sergei Gerasenko wrote:
Hi,
I’ve been using repl-monitor.pl for monitoring replication problems. I
would like to use an account with a minimal set of permissions needed
for the functionality. I created a user and added the permission to
Read Replication Agreements. N
Hi,
I’ve been using repl-monitor.pl for monitoring replication problems. I would
like to use an account with a minimal set of permissions needed for the
functionality. I created a user and added the permission to Read Replication
Agreements. Now the user can read the agreements but fails on:
$
On 08/17/2018 11:27 AM, Cassandra Reed wrote:
Hi Everyone,
We are in a sticky spot right now where we need to install a new
certificate in our 389 Production system, but we do not have the
password that was used when the system was built years ago. We have
tried all of the possible passwor
Hi Everyone,
We are in a sticky spot right now where we need to install a new
certificate in our 389 Production system, but we do not have the password
that was used when the system was built years ago. We have tried all of
the possible passwords that we can think of, to no avail.
Is there a way
