[389-users] Adding additional optional attritubes

Hi All, I'm running 389-ds-1.2.2-1.el6. I would like to add two optional attributes for something like Supervisor/Advisor Name and Email. This is what I have now. Looking for some info on how to go about testing and making this change. # ldapsearch -xLLL uid=ldapfoo dn:

[389-users] Re: Track constraint violation due password policy

On 10/31/18 10:37 AM, Alberto Viana wrote: Hi Mark, In access log the behavior is exactly how you said (small description): "invalid password syntax" Yeah a bit vague :-( I opened this RFE ticket: https://pagure.io/389-ds-base/issue/50002   -->  Feel free to add any comments, requests, or

[389-users] Track constraint violation due password policy

Hi Guys, There's any way to log or track constraint violation reason? Once We have 2 environments I need to track when an user could change password on windows side but this password could not be replicated to 389 due to password policy . I can see this on passsync log: 10/30/18 18:43:38:

[389-users] Re: Track constraint violation due password policy

Hi Alberto, Did you check the access log?   There "should" be a small text message that said what syntax was violated on the RESULT line in the access log.  Just grep for err=19 in the access logs.  Let me know if you find it.  But that's all there would be for troubleshooting this.  

[389-users] Re: Adding additional optional attritubes

Hi Tina, Sounds like you want to add new/custom schema to the server.  So here in a link to the documentation on how to do it: https://access.redhat.com/documentation/en-us/red_hat_directory_server/10/html/administration_guide/extending_the_directory_schema HTH, Mark On 10/31/18 10:25

[389-users] issues with password encryption changes after upgrade

Hi list, we upgrade from1.3.5.15-1.fc24, to 1.3.7.5-24.el7 , this a multi master replication environment we are seeing the paswd encryption for new users in new 389-DS has been changed and is causing some grief , both version have the start of passwd same string :'e1NTSE" , BUT the

[389-users] Re: issues with password encryption changes after upgrade

On 10/31/18 1:25 PM, Ghiurea, Isabella wrote: Hi list, we upgrade from1.3.5.15-1.fc24, to  1.3.7.5-24.el7 What platform are you on now?  Do you see any errors in the errors log when the server starts up? , this a multi master replication environment  we are seeing the paswd encryption

[389-users] Re: issues with password encryption changes after upgrade

here are more details from DS cfg *389-DS 1.3.5.15 fc 24 dn: cn=encryption,cn=config objectClass: top objectClass: nsEncryptionConfig cn: encryption nsSSLSessionTimeout: 0 nsSSLClientAuth: allowed sslVersionMin: TLS1.1 nsSSL3Ciphers: default allowWeakCipher: off nsKeyfile:

[389-users] Announcing 389 Directory Server 1.3.9.0

389 Directory Server 1.3.9.0 The 389 Directory Server team is proud to announce 389-ds-base version 1.3.9.0 Fedora packages are available on Fedora 27. https://koji.fedoraproject.org/koji/taskinfo?taskID=30581994 Bodhi

[389-users] Re: issues with password encryption changes after upgrade

Mark thank you for reply , we are running Cent OS 7 with 389-DS 1.3.7.5-24.el7 and getting the following : passwordStorageScheme: SSHA512 should we change the ldap passwd encrytion to: PBKDF2_SHA256 than for 'safety ' reason ? The grief is caused : we have two systems each with own