Hello,
one of our clients wants to use GOSA (https://oss.gonicus.de/labs/gosa/) as a frontend for the 389 DS.
I found a number of postings that configuring GOSA to work with the 398 DS isn't easy.
Therefore my question is whether anyone has a working combination and might publish a howto on it?
Otherwise I would have to find my way through it and write the docu on it.
Thanks for any hints & suggestions,
Stefan
Hi Stefan, GOsa² uses its own combination of objectClasses to store information plus its own set of ACL's to control access to the GUI but this ACL's does not translate into protection for other access methods that does not go through the GUI.
I think you will get much better support from the GOsa² mailing list with regards to get it working with 389. The developer of GOsa² actively responds and I have got answers to all my GOsa² related questions there.
The GOsa² team is also busy rewriting a lot of the documentation of which a lot is in French currently so there might be something available already that covers implementation with 389.
Best Regards
From: 389-users-bounces@lists.fedoraproject.org [389-users-bounces@lists.fedoraproject.org] on behalf of Stefan-Michael Guenther [389ds@in-put.de] Sent: 18 August 2010 21:29 To: 389-users@lists.fedoraproject.org Subject: [389-users] GOSA as a frontend for the 389 Directory Server?
Hello,
one of our clients wants to use GOSA (https://oss.gonicus.de/labs/gosa/) as a frontend for the 389 DS.
I found a number of postings that configuring GOSA to work with the 398 DS isn't easy.
Therefore my question is whether anyone has a working combination and might publish a howto on it?
Otherwise I would have to find my way through it and write the docu on it.
Thanks for any hints & suggestions,
Stefan
________________________________________________________________________ In order to protect our email recipients, Betfair Group use SkyScan from MessageLabs to scan all Incoming and Outgoing mail for viruses.
________________________________________________________________________
I am curious if anybody knows of a bug with the password history limit?
I have the limit set to 20 passwords, and due to debugging I have cycled through 20 passwords. From that point forward I cannot set any more passwords. Regardless of what I put in it claims it is in the password history, which is not true since they are completely randomly generated passwords.
If I disable password history checking in the policy, I can set my password again.
-Brandon
On 09/01/2010 05:50 PM, brandon wrote:
I am curious if anybody knows of a bug with the password history limit?
I am not aware of a bug like this. What version of 389-ds-base are you running?
I have the limit set to 20 passwords, and due to debugging I have cycled through 20 passwords. From that point forward I cannot set any more passwords. Regardless of what I put in it claims it is in the password history, which is not true since they are completely randomly generated passwords.
If I disable password history checking in the policy, I can set my password again.
-Brandon
389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
Nathan Kinder wrote:
On 09/01/2010 05:50 PM, brandon wrote:
I am curious if anybody knows of a bug with the password history limit?
I am not aware of a bug like this. What version of 389-ds-base are you running?
Versions:
389-ds-console-1.2.0-5 389-admin-1.1.9-1 389-admin-console-1.1.4-2 389-console-1.1.3-5 389-ds-base-1.2.3-1 389-admin-console-doc-1.1.4-2 389-adminutil-1.1.8-4 389-ds-console-doc-1.2.0-5 389-dsgw-1.1.4-1 389-ds-1.1.3-5 RHEL 5.5
We have one master and two replica's.
-Brandon
Brandon G wrote:
Nathan Kinder wrote:
On 09/01/2010 05:50 PM, brandon wrote:
I am curious if anybody knows of a bug with the password history limit?
I am not aware of a bug like this. What version of 389-ds-base are you running?
Versions:
389-ds-console-1.2.0-5 389-admin-1.1.9-1 389-admin-console-1.1.4-2 389-console-1.1.3-5 389-ds-base-1.2.3-1 389-admin-console-doc-1.1.4-2 389-adminutil-1.1.8-4 389-ds-console-doc-1.2.0-5 389-dsgw-1.1.4-1 389-ds-1.1.3-5 RHEL 5.5
We have one master and two replica's.
See if you get the problem with the newly released 389-ds-base 1.2.6 and related packages.
-Brandon
-- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
On 09/14/2010 12:41 PM, Rich Megginson wrote:
Brandon G wrote:
Nathan Kinder wrote:
On 09/01/2010 05:50 PM, brandon wrote:
I am curious if anybody knows of a bug with the password history limit?
I am not aware of a bug like this. What version of 389-ds-base are you running?
Versions:
389-ds-console-1.2.0-5 389-admin-1.1.9-1 389-admin-console-1.1.4-2 389-console-1.1.3-5 389-ds-base-1.2.3-1 389-admin-console-doc-1.1.4-2 389-adminutil-1.1.8-4 389-ds-console-doc-1.2.0-5 389-dsgw-1.1.4-1 389-ds-1.1.3-5 RHEL 5.5
We have one master and two replica's.
See if you get the problem with the newly released 389-ds-base 1.2.6 and related packages.
There was a bug that I fixed a few months back that was related to password history. I'll have to dig up the details. It may very well fix this issue.
-NGK
-Brandon
-- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
-- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
On 09/14/2010 02:00 PM, Nathan Kinder wrote:
On 09/14/2010 12:41 PM, Rich Megginson wrote:
Brandon G wrote:
Nathan Kinder wrote:
On 09/01/2010 05:50 PM, brandon wrote:
I am curious if anybody knows of a bug with the password history limit?
I am not aware of a bug like this. What version of 389-ds-base are you running?
Versions:
389-ds-console-1.2.0-5 389-admin-1.1.9-1 389-admin-console-1.1.4-2 389-console-1.1.3-5 389-ds-base-1.2.3-1 389-admin-console-doc-1.1.4-2 389-adminutil-1.1.8-4 389-ds-console-doc-1.2.0-5 389-dsgw-1.1.4-1 389-ds-1.1.3-5 RHEL 5.5
We have one master and two replica's.
See if you get the problem with the newly released 389-ds-base 1.2.6 and related packages.
There was a bug that I fixed a few months back that was related to password history. I'll have to dig up the details. It may very well fix this issue.
Here is the bug I was referring to.
https://bugzilla.redhat.com/show_bug.cgi?id=511112
-NGK
-Brandon
-- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
-- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
-- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
On 09/14/2010 03:02 PM, Nathan Kinder wrote:
See if you get the problem with the newly released 389-ds-base 1.2.6 and related packages.
There was a bug that I fixed a few months back that was related to password history. I'll have to dig up the details. It may very well fix this issue.
Here is the bug I was referring to.
Nice, thanks! I will upgrade in our Lab environment and see if it improves things.
-Brandon
389-users@lists.fedoraproject.org
-
brandon -
Gerrard Geldenhuis -
Nathan Kinder -
Rich Megginson -
Stefan-Michael Guenther