orm searches against both of the first 2
servers? Basic ldapsearch/ldapwhoami over TLS. That way we can rule out
connectivity issues.
--
Sincerely,
William Brown
Senior Software Engineer,
Identity and Access Management
SUSE Labs, Australia
--
___
3
:)
>
> Regards,
>
> AI
>
>
> - Mail original -
> > De: "Morgan Jones"
> > À: "General discussion list for the 389 Directory server, project."
> > <389-users@lists.fedoraproject.org>
> > Envoyé: Mercredi 5 Juin 2024 2
Nicolas Riss
--
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines
(9.4 i think). 389ds version
2.5 compiling from git branch (i think the latest one is 2.5.1, maybe it is
available as rpm). No complaints at all :)
Regards,
AI
- Mail original -
> De: "Morgan Jones"
> À: "General discussion list for the 389 Directory server, pr
ars to be 3.x (see above
> re: preferred production version).
>
Due to how we build the docker containers we tend to track the "latest" right
now. But there was some talk to fix that.
--
Sincerely,
William Brown
Senior Software Engineer,
Identity and Access Management
SUSE
for a production install? I see there is an up to
date image which I've been able to start but it appears to be 3.x (see above
re: preferred production version).
Thanks,
-morgan
--
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send
ps some other way that I may have missed in my research?
Thanks everyone,
Trevor
--
___________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://d
e capture audit logs
on.
Is there perhaps some other way that I may have missed in my research?
Thanks everyone,
Trevor
--
_______
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fe
te:
>roleOccupant: uid=user1,ou=users,dc=test,dc=tld
>
> I would like to delete the cn=xyz-object automatically when the
> uid=user1-object is deleted. Is there a way to do this server side, or
> do I have to implement it client side?
>
> Thanks
> Julian
> --
> ____
--
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List
about the initial installation and setup
See Source <https://www.port389.org/docs/389ds/development/source.html> for
information about source tarballs and SCM (git) access.
Feedback
We are very interested in your feedback!
Please provide feedback and comments to the 389-u
Cross-posting this on the 389-users list.
rob
Jochen Kellner via FreeIPA-users wrote:
>
> Hi,
>
> I've upgraded my freeipa server to Fedora 40 (the system was installed
> several releases ago). After the upgrade I get the following new warning
> from ipa-healthcheck:
>
and then I can retire
the old instances.
--
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code
readwaiters: 0
opsinitiated: 1913950
opscompleted: 1913949
entriessent: 1945806
bytessent: 206107062
currenttime: 20240418184424Z
starttime: 20240417165836Z
nbackends: 1
--
_______
389-users mailing list -- 389-users@lists.fedoraproject.org
To
__
> 389-users mailing list -- 389-users@lists.fedoraproject.org
> To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.
.
--
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
ion to halt and it will not resume until it gets passed whatever
the issue is.
I was hoping that I could somehow get past this 2 hour retry by disabling and
re-enabling the agreement but that seems to have no effect.
Any thoughts on how to attack this?
- Tim
--
_________
nstall-389.html> for more
information about the initial installation and setup
See Source <https://www.port389.org/docs/389ds/development/source.html> for
information about source tarballs and SCM (git) access.
Feedback
We are very interested in your feedback!
Please provide feedback and c
: Julian Kippels
Sent: Monday, April 15, 2024 4:51 AM
To: General discussion list for the 389 Directory server project.
<389-users@lists.fedoraproject.org>
Subject: [389-users] Permission of log files
✉External message: Use caution.
Hi,
I am looking for a way to configure the default perm
that my
external log-monitoring can access the files.
Julian
--
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https
.
Julian
smime.p7s
Description: Kryptografische S/MIME-Signatur
--
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org
cated in real time?
My first attempt produced an error about different database
versions.
Maybe it is not supposed to work?
Thank you,
- Alex
--
___
389-users mailing list --389-users@lists.fedoraproject.org
To unsubscribe send an email to389-users-le...
;
>
>
> My first attempt produced an error about different database versions.
>
> Maybe it is not supposed to work?
>
>
>
> Thank you,
>
> - Alex
>
>
>
>
>
>
>
> --
> ___
> 389-users mailing list -- 389-users@lists.fedoraproject.org
&
transition, and get the data replicated in
real time?
My first attempt produced an error about different database versions.
Maybe it is not supposed to work?
Thank you,
- Alex
--
_______
389-users mailing list --389-users@lists.fedoraproject.org
To unsubs
an error about different database versions.
Maybe it is not supposed to work?
Thank you,
- Alex
--
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code
that gives you some more context.
--
Sincerely,
William Brown
Senior Software Engineer,
Identity and Access Management
SUSE Labs, Australia
--
_______
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@l
es: This could be a valuable improvement as the general idea of
PBKDF2 is to increase iteration count over time while hardware resources are
growing. Any comments?
Kind regards,
Tobias Ernstberger
smime.p7s
Description: S/MIME cryptographic signature
--
___________
-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives
of these Password Administrators.
--
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct
,
and I.
If that's not clear, let me know and I can draw a diagram.
--
William Faulk
--
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https
memberof idnssoaserial
entryusn krblastsuccessfulauth krblastfailedauth krbloginfailedcount
nsDS5ReplicatedAttributeListTotal: (objectclass=*) $ EXCLUDE entryusn
krblastsuccessfulauth krblastfailedauth krbloginfailedcount
--
William Faulk
--
_______
389-users mai
, though. I'd
have to perform a rolling reinitialization throughout our whole environment,
and it takes ages and a lot of effort.
--
___________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedorapr
is not yet completed. And I suspect that
you hit a bug about this list. I remember that we fixed something in that
area a few years ago ...
I think I found it, or something closely related.
https://github.com/389ds/389-ds-base/pull/4553
--
___
389-users
iling server and proceed
from there. The issue is if it has changes that other nodes don't have.
--
Sincerely,
William Brown
Senior Software Engineer,
Identity and Access Management
SUSE Labs, Australia
--
___
389-users mailing list --
https://github.com/389ds/389-ds-base/pull/4553
> --
> ___________
> 389-users mailing list -- 389-users@lists.fedoraproject.org
> To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/co
hing closely related.
https://github.com/389ds/389-ds-base/pull/4553
--
_______
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproje
and a lot of effort.
--
William Faulk
--
___________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Gu
nderstand what actually went wrong any
> better than I do now.
>
> > If you want to assert that "Some change I made at CSN X is on all
> servers" then
> > you would need to read and parse the ruv and ensure that all of them are
> at or past that
> > CSN for that
for that replica id.
Well, you'd think so. I've got that problem, too, where some CSNs just seem to
get missed, but the max CSN in the RUV is well past that. But that's a
different problem and not the one I'm working on now.
Thanks for the input.
--
_____
hat problem, too, where some CSNs just seem to
get missed, but the max CSN in the RUV is well past that. But that's a
different problem and not the one I'm working on now.
Thanks for the input.
--
William Faulk
--
___________
389-users mailing list --
which it sends a message that states the greatest CSN that it originated.
> First off, is that a correct understanding?
Might be worth re-reading
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org/thread/UYP4PYBVVDKGKZVZTC34JVXNUVP2VAVI/
It doesn't send a single
, but I'm not having any luck with that yet.)
In particular, I see the max CSN for this server in all of these RUVs less than
CSNs recorded in the server's own log files.
--
William Faulk
--
___
389-users mailing list -- 389-users@lists.fedoraproject.org
=traken-test,dc=ftt
binddn = cn=Directory Manager
--
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US
Message
>>> Subject: dscontainer as non root
>>> Date: Mon, 12 Feb 2024 20:01:09 +0530
>>> From: Antony Jose
>>> To: 389-users-ow...@lists.fedoraproject.org
>>>
>>> Hi,
>>> Can we run dscontainer as non root process. I
Hi Antony,
On Mon, Feb 12, 2024 at 3:37 PM Mark Reynolds wrote:
> Forwarding to the correct list
>
>
> Forwarded Message
> Subject: dscontainer as non root
> Date: Mon, 12 Feb 2024 20:01:09 +0530
> From: Antony Jose
> To: 389-users-ow...@lists.
Forwarding to the correct list
Forwarded Message
Subject:dscontainer as non root
Date: Mon, 12 Feb 2024 20:01:09 +0530
From: Antony Jose
To: 389-users-ow...@lists.fedoraproject.org
Hi,
Can we run dscontainer as non root process. I have deployed
om/389ds/389ds.github.io/blob/main/docs/389ds/releases/release-3-0-1.md#feedback>
Feedback
We are very interested in your feedback!
Please provide feedback and comments to the
- 389-users mailing list:
https://lists.fedoraproject.org/admin/lists/389-users.lists.fedoraproject.org
- 389ds
my Boost Samsung Galaxy A23 5G
> Get Outlook for Android <https://aka.ms/AAb9ysg>
> --
> *From:* Simon Pichugin
> *Sent:* Thursday, January 25, 2024 5:44:57 PM
> *To:* General discussion list for the 389 Directory server project.
> <389-users@lists.fedoraproject.org&
tps://aka.ms/AAb9ysg>
*From:* Simon Pichugin
*Sent:* Thursday, January 25, 2024 5:44:57 PM
*To:* General discussion list for the 389 Directory server project.
<389-users@lists.fedoraproject.org>
*Cc:* alex
Idk how to do that lol
Sent from my Boost Samsung Galaxy A23 5G
Get Outlook for Android<https://aka.ms/AAb9ysg>
From: Simon Pichugin
Sent: Thursday, January 25, 2024 5:44:57 PM
To: General discussion list for the 389 Directory server project.
<
e --suffix "dc=example,dc=com" --host "consumer.example.edu"
> --port 389 --conn-protocol=LDAP --bind-dn "cn=replication
> manager,cn=config" --bind-passwd "***" --bind-method=SIMPLE --init
> 10.140.133.36-RO
>
>
>
> no problem occurred, and
bind-method=SIMPLE --init 10.140.133.36-RO
no problem occurred, and the replication completed successfully.
My question is whether this means the replication over TLS required different
config steps, and if yes – what they are?
Thank you,
- Alex
--
________
ot;server_ip": "34.84.136.11", "ldap_version": 3,
"conn_id": 788, "msg": "Bad Ber Tag or uncleanly closed
connection - B1" }
=
I tested with FreeIpa fedora-39-4.11.0 docker with the recent version of 389ds.
ldapsearch -V
ldapsearch:
ossible to promote the conflict entry, despite the documentation
> providing a procedure exactly for that, and that I would have to
> reinitialize the data on that replica.
>
> If anyone has any suggestions for a vendor that can provide decent IdM
> support, I'd love to hear it.
>
> Again, m
nflict entry, despite the documentation providing a procedure
exactly for that, and that I would have to reinitialize the data on that
replica.
If anyone has any suggestions for a vendor that can provide decent IdM support,
I'd love to hear it.
Again, many thanks to everyone here.
--
_____
ll-389.html> for more
information about the initial installation and setup
See Source <https://www.port389.org/docs/389ds/development/source.html> for
information about source tarballs and SCM (git) access.
Feedback
We are very interested in your feedback!
Please provide feedback and comments
le is the same as the old value: "adamss". Surely
> following these directions naively is going to result in deleting the
> naming attribute altogether. Unless maybe the schema prevents it from
> deleting the last value?
>
> Am I correct in thinking I should just skip that
ld just skip that part, while continuing to
delete the nsds5ReplConflict attribute?
--
___________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://d
Thanks for the confirmation.
I'll follow up with the results, just in case anyone in the future comes across
this thread, and to let folks know how the membership gets handled upon rename
of the conflict entry.
--
___
389-users mailing list -- 389
dentity and Access Management
SUSE Labs, Australia
--
_______________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/projec
nt
SUSE Labs, Australia
--
--
_______
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https:/
own
Senior Software Engineer,
Identity and Access Management
SUSE Labs, Australia
--
___________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https:
se you should, not just because you can.
John Thurston907-465-8591
john.thurs...@alaska.gov
Department of Administration
State of Alaska
--
_______
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@
's renamed. I can't imagine that it will acquire the
> correct groups just by being renamed. Am I going to just need to fix that
> up manually? (That may be outside the scope of this mailing list.)
> --
> _______
> 389-users mailing list -- 3
the scope of this mailing list.)
--
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct
"right" entries
on the other servers, otherwise you will delete them all.
rob
--
_______
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https
.)
--
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List
ad entry from the bad replica will
> cause the good entries on all the good replicas to also be deleted? If so,
> is there a better way to resolve this conflict? (At the moment, I'm
> inclined to just reinitialize the data on this one replica.)
> --
> _
etter way to resolve this conflict? (At the moment, I'm inclined to just
reinitialize the data on this one replica.)
--
_______
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fe
? Or
should it work just fine with such number of groups?
Problem is the same for 389-ds-base-1.4.3 deployments and 389-ds-base-2.2.3
deployments.
--
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389
?
--
--
Do things because you should, not just because you can.
John Thurston907-465-8591
john.thurs...@alaska.gov
Department of Administration
State of Alaska
--
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send
389 and AD accounts?
Currently, these existing accounts seem to be simply skipped by the AD
sync process.
Any hint on this is highly appreciated!
Thank you and best regards,
Alex
--
___
389-users mailing list -- 389-users@lists.fedoraproject.org
l.
I have set it up. However, this setting appears to be a way to refer to the
pipe in a new path, without leaving both the pipe and the file behind.
What we want to achieve is to not lose logs regardless of the pipe leader
state. Any tips on this?
--
_______
to inquire whether request information is
> stored sequentially in the queue, and if so, where can I manage the size
> and settings of the queue?
> --
> ___________
> 389-users mailing list -- 389-users@lists.fedoraproject.org
> To unsubscribe send an emai
to large requests.
Here's what I need to do:
1. Increasing the performance of the pipe reader,
2. If the log buffer is not used, measure the limitations of the LDAP server
and reflect them in my architecture.
Thanks
--
___
389-users mailing list -- 389
?
--
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List
ll public CAs, have intermediate certs.
The bugs I raised in 2020 were all abandoned and closed.
Regards,
Graham
—
--
_______
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fed
Thanks!
> Cheers, Rosario
>
> --
> _______
> 389-users mailing list -- 389-users@lists.fedoraproject.org
> To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject
systemd and wrote
these instructions to make it work:
https://bugzilla.redhat.com/show_bug.cgi?id=1520373#c5 (you can skip dsconf
part as you already did have this configuration in cn=config).
Could you please try this approach?
Thanks.
> --
> _______
> 389-users ma
--
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List
and removing from the L4 switch is repeated. Could
> this be caused by my logging settings to pipe?
> Or should I think it's a problem with the Linux file system?
> --
> _______
> 389-users mailing list -- 389-users@lists.fedoraproject.org
> To
tem?
--
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guideli
on server A.
How can logging to pipe affect directory server port 389 access?
Could it be a file descriptor related issue? Why were the other 17 servers able
to recover to normal?
Thanks
--
___
389-users mailing list -- 389-users@lists.fedoraproject.org
-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives
, Rosario
--
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines
again available in the COPR repo.
Run `dnf clean all` to purge old metadata, and the package should be
available for the downgrade.
HTH
>
> Regards,
> Rosario
>
>
>
>
> --
> ___
> 389-users mailing list -
2.2.8 rpms
are no longer available on the copr repository, then I cannot issue "dnf
downgrade 389*".
Is it supposed to work that way ?
Is there clean way to go back to previous version ?
Regards,
Rosario
--
_______
389-users mailing list --
o be clear, here's the ldapmodify LDIF that worked for me:
dn: cn=replica,cn=...,cn=mapping tree,cn=config
changetype: modify
add: nsds5Task
nsds5Task: CL2LDIF
The LDIF that's created shows the actual changed data and not just a blob,
which certainly helps.
--
_____
easy to pull the
> same data out of there.
>
>
> You could do that. Also I noticed there is code to dump the changelog to a
> flat file, but it isn't clear to me how to call it :
>
> https://github.com/389ds/389-ds-base/blob/main/ldap/servers/plugins/replication/cl5_api.c#
; same data out of there.
You could do that. Also I noticed there is code to dump the changelog to a flat
file, but it isn't clear to me how to call it :
https://github.com/389ds/389-ds-base/blob/main/ldap/servers/plugins/replication/cl5_api.c#L4273
--
_______
ssing something obvious, though. Thanks.
--
_______________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/
> had the same CSN
That shouldn't be possible. It's an axiom of the system that CSNs are unique.
--
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora C
her.
--
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/w
hat hunch is correct it'd be a case of figuring
out the name of the attribute so you request it, and the access rights
required. Also from distant memory, but I thought the changelog was queryable
via LDAP, somehow.
--
_______
389-users mailing list --
ng tools to help communicate here
about what's going on.
--
Sincerely,
William Brown
Senior Software Engineer,
Identity and Access Management
SUSE Labs, Australia
--
_______
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email t
Makes sense. I'll try to read some more documentation/source about the actual
communication.
Do you know how I can find mappings between CSNs and changes? Or even just how
to see the changelog at all?
--
___
389-users mailing list -- 389-users
_________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/
I'm currently just using the Directory Manager credentials for my monitoring;
sorry.
--
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct
This was helpful; thanks. I think my biggest misunderstanding was that the RUV
was just the most recent CSN, when it's actually a list of the most recent CSNs
from each replica.
--
___
389-users mailing list -- 389-users@lists.fedoraproject.org
a problem and I generally understand the "+nsuniqueid" conflict
resolution method. My problem is occurring without conflicting updates.
--
___________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users
1 - 100 of 8031 matches
Mail list logo
