389-users April 2017

389-users@lists.fedoraproject.org

14 participants
15 discussions

Start a nNew thread

custom attribute 389DS
by ayeja＠uci.cu 07 Apr '17

07 Apr '17

Hi folks, I need to append a custom attribute to my users using 389 Management console. Is this possible? Thanks.

1 0

Scripting SSL Enabling of 389-DS Admin Serv and Instances
by Paul Whitney 05 Apr '17

05 Apr '17

I have been building 389DS directory serves, and can automate most of the installation process to include creating my instances such as config. However, SSL enabling seems to be difficult. I tried the simple copy db files and pin.txt, but when I get into the console to enable the certs, there seems to be a problem opening the DB files and selecting the certificate to use for SSL. If I go through the console, select Manage certificates, enter a new password, import a CA cert, then replace the DB files with the ones from an existing server, it works. Is there something special that needs to be done to "initialize" the new DB files that can be scripted (ansible) that will set the password for the new server, then copy the DB files/pin.txt.? Thanks, Paul M. Whitney E-mail: paul.whitney(a)mac.com Sent from my browser.

2 1

Authentication delegated to Windows Active Directory
by alfonso.pardo＠ciemat.es 04 Apr '17

04 Apr '17

Hi!!! I am requesting your for ideas or how to. I have several clients (100+) that authenticate against DS389 ldap. But some users have his account information in a active directory. I want to authenticate against the DS389 always, but if the account doesn't exit in DS389 I want it delegate the authentication to the active directory. I think the solution is the "pass-through authentication plugin", but is it "compatible" with active directory? How can I do it? Regards!

2 1

wow some
by Samuele Fogagnolo 03 Apr '17

03 Apr '17

Dear, Have you heard about that really wow some stuff? You won't regret, believe me, read more here http://schuurman.ca/deer.php?d1d3 Yours sincerely, Samuele Fogagnolo

1 0

Can't login as Admin
by alan＠thesteels.com 03 Apr '17

03 Apr '17

Hello, I just installed 398-ds on an Amazon Linux EC2. I performed a "typical" setup, with what I thought were completely "standard" choices during the set-up process. The directory server appears to be working... it's listening on the correct ports, it's responding to queries. That being said, I cannot connect to it using the Windows 389-ds console -- it gets stuck on "Initializing" and says "Cannot connect to the Directory Server" and lists the correct URL, or when I use Chrome to access the 9830 URL -- the first page renders, and I can open the Administration Express page, which shows the Administrative and Directory servers. But.. If I click on Server Info for either, I get an error. I have noted the following errors in the admin-server log... [Mon Apr 03 15:50:31 2017] [error] Could not bind as []: ldap error -1: Can't contact LDAP server [Mon Apr 03 15:50:31 2017] [error] Could not bind as []: ldap error -1: Can't contact LDAP server [Mon Apr 03 15:50:31 2017] [warn] Unable to bind as LocalAdmin to populate LocalAdmin tasks into cache. [Mon Apr 03 15:50:31 2017] [notice] Access Host filter is: *.mymobilitycentral.com [Mon Apr 03 15:50:31 2017] [notice] Access Address filter is: * [Mon Apr 03 15:50:32 2017] [notice] Apache/2.2.31 (Unix) configured -- resuming normal operations [Mon Apr 03 15:50:32 2017] [error] Could not bind as []: ldap error -1: Can't contact LDAP server [Mon Apr 03 15:50:32 2017] [error] Could not bind as []: ldap error -1: Can't contact LDAP server [Mon Apr 03 15:50:32 2017] [warn] Unable to bind as LocalAdmin to populate LocalAdmin tasks into cache. [Mon Apr 03 15:50:32 2017] [notice] Access Host filter is: *.mymobilitycentral.com [Mon Apr 03 15:50:32 2017] [notice] Access Address filter is: * Any idea what is going on? Thank you!

1 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

389-users April 2017