https://fedorapeople.org/groups/389ds/ci/nightly/2019/06/14/report-389-ds-base-1.4.1.3-20190613git054d32e.fc30.x86_64.html
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to
We have a problem... FreeIPA, as well as other unknown applications,
expect the status to be in the old format. While we can fix this in
FreeIPA, it will still break older versions of FreeIPA during replica
installs when it tries to setup replication with the new version. So
all
https://www.port389.org/docs/389ds/design/repl-agmt-status-design.html
https://pagure.io/389-ds-base/pull-request/50447
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to
Hi all,
Issue: https://pagure.io/389-ds-base/issue/50446
from lib389.utils import (ds_is_older) is missing in
https://pagure.io/389-ds-base/blob/master/f/src/lib389/lib389/idm/account.py
users = UserAccounts(standalone, DEFAULT_SUFFIX)
for i in users.list(): i.dn
On 6/13/19 4:02 AM, William Brown wrote:
On 12 Jun 2019, at 17:36, Mark Reynolds wrote:
http://www.port389.org/docs/389ds/design/repl-agmt-status-design.html
Looks great!
Instead of "Success" we could use "Healthy" because replication isn't a success/fail, it's a longterm
"good/bad" IE
On Thu, Jun 13, 2019 at 3:26 PM William Brown wrote:
>
> Is the test case *just* testing if binary searching of attributes works?
The test was to check if we can query the server for
userCertificate=, where is a string representation of a
base64 encoded x509 certificate. The original test was
base64 in ldap is just to transport binary ... so they are one and the same.
Either way, I think that you should check ensure str, and provide logs from
access and lib389 in verbose to show what the filter generator is doing,a nd
what the server is attempting to process so we can see where the
Main aim of the test case is filter user with binary search not the base64
.
(Pdb) six.ensure_str(crt)
*** UnicodeDecodeError: 'utf-8' codec can't decode byte 0x82 in position 1:
invalid start byte
On Thu, Jun 13, 2019 at 7:05 PM William Brown wrote:
> I'm really suspicious here that your
https://pagure.io/389-ds-base/pull-request/50444
—
Sincerely,
William Brown
Senior Software Engineer, 389 Directory Server
SUSE Labs
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to
I'm really suspicious here that your escape bytes is not needed for ldap as
much as to prevent python state leaking into the string and the data. I'm
wondering if there is a better approach
Can ldap filters take base64 instead? Perhaps the issue with your filter atm is
that you are
Yes, it is. but with escape_bytes function only.
(Pdb) Accounts(standalone,
DEFAULT_SUFFIX).filter(f"(userCertificate={crt})")
*** ldap.FILTER_ERROR: {'desc': 'Bad search filter', 'errno': 2, 'info':
'No such file or directory'}
And finally .
Accounts(standalone,
Is the test case *just* testing if binary searching of attributes works?
> On 13 Jun 2019, at 15:25, Anuj Borah wrote:
>
> @William Brown
>
>
> This is my test case in bash form . Hope this helps.
>
> dn: uid=user4F, ou=People, dc=example, dc=com
> uid: user4F
> cn: User 4F
> sn:
@William Brown
This is my test case in bash form . Hope this helps.
dn: uid=user4F, ou=People, dc=example, dc=com
uid: user4F
cn: User 4F
sn:
givenName:
ou: People
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass:
I'm sorry, you didn't answer my questions can you answer the below
questions, exactly and precisely, else I can't help you :(
>
> * WHAT is the test you are creating? What does it test? How? What steps from
> start to finish? Please list this exactly.
> * Use SSCA to make the user cert -
On Thu, Jun 13, 2019 at 6:05 PM William Brown wrote:
>
>
> > On 13 Jun 2019, at 14:27, Anuj Borah wrote:
> >
> >
>
> Okay, so:
>
> * WHAT is the test you are creating? What does it test? How? What steps
> from start to finish? Please list this exactly.
> * Use SSCA to make the user cert - it
> On 13 Jun 2019, at 14:27, Anuj Borah wrote:
>
>
Okay, so:
* WHAT is the test you are creating? What does it test? How? What steps from
start to finish? Please list this exactly.
* Use SSCA to make the user cert - it creates pem and der copies
* Have you looked at:
@William Brown
Please check the attached test case .
I want to put escape_bytes function to lib389 utils.py file .
Regards
Anuj Borah
On Mon, Jun 10, 2019 at 2:18 PM William Brown wrote:
>
>
> > On 9 Jun 2019, at 03:40, Anuj Borah wrote:
> >
> > @William Brown
> >
> > Yes, it does.
> >
>
Hi there,
There have been a few changes to systemd files recently so I wanted to check
about how to correctly supply environment variables to the server. For example,
KRB5_KTNAME. Are we doing this still by EnvironmentFile? Or by another method?
—
Sincerely,
William Brown
Senior Software
Hi all,
During my packaging work I have noticed that suse is shipping extra schema for
compatability with openldap and some legacy applications. I have attached the
tar.gz to check.
What would we think about shipping this in the upstream to help ensure
compatibility between RH/SUSE/Others in
> On 12 Jun 2019, at 17:36, Mark Reynolds wrote:
>
> http://www.port389.org/docs/389ds/design/repl-agmt-status-design.html
Looks great!
Instead of "Success" we could use "Healthy" because replication isn't a
success/fail, it's a longterm "good/bad" IE healthy/failing state. So perhaps
https://pagure.io/389-ds-base/pull-request/50441
—
Sincerely,
William Brown
Senior Software Engineer, 389 Directory Server
SUSE Labs
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to
21 matches
Mail list logo
