Ok, you might need to set the access hosts and addresses to "*":
You want to set:
nsAdminAccessAddresses and nsAdminAccessHosts to "*", then you need to restart the admin server: service dirsrv-admin restart
If that doesn't work, then I'm not sure what is wrong.
Sorry for the late reply, I was sick and didn't get back to work until today. Please find attached logs and configuration of my server. Let me know if you see how I can make this work with what I have. Thanks in advance,
On 8/25/23 2:20 PM, Omar wrote:
I'm sorry, didn't know that the dsgw was no longer supported. We are trying to create an LDAP service with a GUI so that our users can change their passwords.
I have installed and configured the following:
- 389-dsgwI have deployed all these on Centos-7 and the versions are:
- 389-dsgw-1.1.11-5Now that I know that the dsgw is no longer supported, what do you recommend I use as a GUI for all users?
Users can log into 389-console, but you might need to configure some settings in adm.conf to make that work with just using the user's RDN of their DN. Otherwise you need to use the entire DN of the entry to log in. There might be other config files you need to edit. Sorry it's so old I don't recall all the details, but I know it's possible.
But, did you look into the admin server error log? I would think dsgw could still work, but without knowing more about the failure it's hard to say.
Our wiki has a few docs on it, but not much:
There was an upstream project started by William Brown (https://pagure.io/389-ds-portal) many years ago, but I don't think it's been updated in a long time. I'm not sure if it's functional or not. Our team does not work on this project, but you might want to look into it. Otherwise you need to develop your own user portal. There is also Openldap's Apache Directory Studio: https://directory.apache.org/studio/ but I don't think this is exactly what you are looking for.
Thanks for the support.
On Thu, Aug 24, 2023 at 8:56 AM Mark Reynolds <email@example.com> wrote:
On 8/23/23 10:08 AM, Omar Pagan wrote:
> Getting the following error after following all the documentation for deploying 389ds and 389dsgw. Please help.
What documentation? dsgw (Directory Server Gateway) hasn't been
"supported/maintained" in over 10+ years so I am not surprised it's not
working. Also it was only provided to show what an LDAP webapp could
do. It was never a fully supported product.
Or, are you referring to the old java console? 389-console?
What platform are you trying to run this on? What is the rpm version of
What is in the admin server error log? Not sure where this log is
anymore(it's been so long since I looked at it), but its probably under
/var/log/dirsrv/admin-serv/ ? Something like that...
> Internal Server Error
> The server encountered an internal error or misconfiguration and was unable to complete your request.
> Please contact the server administrator at [no address given] to inform them of the time this error occurred, and the actions you performed just before this error.
> More information about this error may be available in the server error log.
> Apache/2.4 Server at 10.194.81.88 Port 9830
> 389-users mailing list -- firstname.lastname@example.org
> To unsubscribe send an email to email@example.com
> 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: https://firstname.lastname@example.org
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Directory Server Development Team
-- Directory Server Development Team
-- Directory Server Development Team