Hi Brian.
Glad you've figured it out. This is good to know.
If we can support both, or provide an option to choose the mode, I'll
definitely take a patch for this.
Christian
--
Christian Hammond - [EMAIL PROTECTED]
VMware, Inc.
On Mon, Nov 3, 2008 at 8:40 PM, Brian Hill <[EMAIL PROTECTED]> w
I found the problem. I am using OpenLDAP for UNIX systems, the
combination which generally uses RFC2307bis mappings (also called the
NIS schema sometimes). Anyway, the reviewboard code assumes RFC2307 AD
mappings, which usually offers the first and last names as 'givenName'
and 'sn'. In the UNIX w
I may have the terminology wrong. To be honest, I have very little
experience with LDAP and didn't write our LDAP support, so I'm just trying
to figure things out from the source.
It might be worth poking around in reviewboard/accounts/backends.py and see
where it fails. It could be in the INVALID
I supplied it - no luck. I am little confused, though, How is this
supposed to be a mask? It seems to me that it is only supposed to be
the DN for a user that can do lookups:
cn=proxyagent,ou=profile,dc=corp,dc=domain,dc=tld
Is this not the case?
Brian
On Nov 3, 5:51 pm, "Christian Hammond" <[
The empty anonymous fields may be the problem. Looking at the code, it looks
like they're very much needed.
They're basically used to be able to look up the user's info when doing a
query for a User object, and the authentication code calls into this as
well. So once you supply the anonymous field
There isn't much to it, but I have reviewed it pretty carefully:
uid=%s,ou=People,dc=corp,dc=domain,dc=tld
I also tried with cn (which would be the same), in case it has to be a
DN:
cn=%s,ou=People,dc=corp,dc=domain,dc=tld
And the host spec is:
ldap://10.20.30.40:389
I left the anon fields e
So, the one LDAP exception handler I didn't add logging to was the
"INVALID_CREDENTIALS" handler. This is thrown if the user's login/password
are invalid, *or* if the user mask string isn't correct. I'd imagine it's
probably the latter. Sure there's no typos or anything?
Christian
--
Christian H
I checked out the latest reviewboard and enabled logging. I see the
log, but it contains very little detail - only INFO lines and nothing
related to my failed LDAP logins. Is there some way to increase the
verbosity that I missed?
2008-11-03 17:10:43,002 - INFO - Logging to /tmp/reviewboard.log w
Okay, these are in. Hopefully it will tell you what's going wrong, or at
least give you some error message you can use as a basis in your diagnosis.
Let me know.
Christian
--
Christian Hammond - [EMAIL PROTECTED]
VMware, Inc.
On Thu, Oct 30, 2008 at 5:42 PM, Christian Hammond <[EMAIL PROTECTED
I don't know how your python knowledge is, but it might be useful to open up
accounts/backends.py and do some logging in the error handlers, find out
what it is that's failing.
I'll try to get some logging in for the error cases later today.
Christian
--
Christian Hammond - [EMAIL PROTECTED]
VM
1) If I repeatedly clear the browser cache (Firefix 3.0.3 / Windows &
IE 7), the settings appear as the defaults, but it is seems pretty
clear that caching is causing a lot of this.
2) In any case, I cannot get an LDAP users to authenticate. I clearly
see the LDAP traffic generated by reviewboard
Okay, so the wrong settings are showing up after hitting Save, but if you
navigate back to that page what do you see? What about after restarting the
server?
LDAP users don't need an existing account on Review Board. Assuming the LDAP
configuration is correct, the LDAP backend should Just Work, cr
Actually, I see the settings in the siteconfig_siteconfiguration table
now, but it isn't clear to me that they are being used, since I can't
seem to get any LDAP users to successfully login. How do I get
reviewboard to actually use LDAP to look a user's password? Does that
user have to be added to
It still doesn't work. I _do_ get the "settings saved" geen check mark
now, but the default settings come back. It seems worse now, because
now none of the settings actually save. Before the email settings did
save.
Brian
On Oct 30, 3:15 pm, "Christian Hammond" <[EMAIL PROTECTED]> wrote:
> Every
Everyone, go ahead and update. See if it works better now. There was a newly
introduced bug preventing settings from being saved.
If you're still encountering the problem, I have some debugging I'll commit
that might help track this down.
Really sorry for the inconvenience :/
Christian
--
Chri
Okay, I have something I'm looking into that may be the cause.
Can you go onto, say, the Diff Viewer form and see if settings save properly
there?
Christian
--
Christian Hammond - [EMAIL PROTECTED]
VMware, Inc.
On Thu, Oct 30, 2008 at 2:34 PM, Brian Hill <[EMAIL PROTECTED]> wrote:
>
> 1) I c
1) I change to LDAP, fill in the values, click save, and immediately
restart apache.
I then click on General and the default values appear.
2) mod_python-3.2.8-3.1(bundled with CentOS 5.2 x86_64 w/ most recent
rpm updates)
3) mysql-5.0.45-7.el5 (bundled with CentOS 5.2 x86_64 w/ most recent
rpm
It's troublesome that people are all seeing this problem... For each person
who hit this, please answer the following:
* If you set the setting and then restart Apache, do you see the proper
setting?
* Are you using mod_python or something else?
* What database are you using?
Christian
--
Chr
I've noticed that I'm unable to save any edits to the General Settings
page, for instance setting the Administrator user name will not save
either.
--Jennifer
On Oct 30, 2:14 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
wrote:
> I'm having the same issue, the settings are not saved. Is there any
I'm having the same issue, the settings are not saved. Is there any
workaround or values that I can configure directly in the database?
Thanks!
--Jennifer
On Oct 29, 8:32 pm, Brian Hill <[EMAIL PROTECTED]> wrote:
> I am still having the same problem Kevin did. I tried it in IE and
> Firefox sa
I am still having the same problem Kevin did. I tried it in IE and
Firefox same result. You don't get the green 'saved' checkmark.
Instead, the same form just returns...
Has anyone figured this out yet?
Brian
On Sep 12, 3:02 pm, "Christian Hammond" <[EMAIL PROTECTED]> wrote:
> Very strange. I'm
Very strange. I'm glad it's working for you now. We'll definitely want to
know if it happens again so we can figure out if this was just some browser
caching issue or something else.
Christian
--
Christian Hammond - [EMAIL PROTECTED]
VMware, Inc.
On Fri, Sep 12, 2008 at 10:32 AM, [EMAIL PROTEC
Christian,
It seems to be working now, thanks. Not sure what was going on --
perhaps some sort of caching issue. It just kept half-remembering
what I typed in, and then I'd refresh and it would be some different
combination of the settings I'd tried, and then it would change again
when I refres
Hmm, I'm having trouble reproducing this. Can you go into Database -> Site
Configurations -> the only entry and send me (privately if you wish) the
contents of the settings?
Christian
--
Christian Hammond - [EMAIL PROTECTED]
VMware, Inc.
On Wed, Sep 10, 2008 at 6:30 PM, [EMAIL PROTECTED] <[EMA
I can't seem to get it to remember my LDAP config! I go in and set it
in Admin | Settings | General | Advanced Auth by changing the type to
LDAP, setting the LDAP server, the email domain, and updating the user
mask. When the page refreshes it has these parameters, but when I go
to the E-Mail ta
Enabling LDAP is done by going into the Admin UI, clicking Settings,
General, and then changing the Auth Type to LDAP and filling in the fields.
We're going to begin moving the custom LDAP mods into our upstream LDAP
class pretty soon so that you don't have to maintain your own copy.
Christian
-
Hi Mate
in accounts/backends.py there is a class called LDAPBackend.
The ldap mods that are spoken of are placed in here.
The outcome of the mods we run on our system:
1. discover the DN to bind as (and check password) from the 'username'
2. on create user - get email from ldap too
3. o
hi,
I am new to this, would you mind providing a little howto?
I.e. how to install that file you created etc?
Thanks,
Martin
On Aug 11, 7:33 pm, teki <[EMAIL PROTECTED]> wrote:
> I am using a slightly modified LDAP backend:http://gist.github.com/4967
> With this settings:
>
> LDAP_URI='ldap://1
28 matches
Mail list logo
