Hi Pablo,
I can't paste the exact source code, because I have specifics in the code
that match up to my company. However, explaining my approach is fairly
simple:
a) I have a cron job that runs regularly (hourly/daily, I don't remember)
which grabs the list of users that are supposed to be act
Hi Joe,
Sorry I've not responded yet. Not near my computer at the moment. Hopefully I
can send a useful tidbit later today or tomorrow. Putting it on my todo list.
Eric
On Jun 5, 2013, at 3:54 PM, Joe Reyna wrote:
> Hi Eric, can you post your modified custom authenticator?
>
> On Wednesday,
Hi Eric, can you post your modified custom authenticator?
On Wednesday, March 23, 2011 1:02:10 PM UTC-7, Eric Johnson wrote:
>
> I achieved your aim for our local copy of ReviewBoard by snagging the
> existing LDAP code, and modifying it slightly. I then used the modified
> code as a custom auth
Which part? LDAP, or auth backends?
Django provides basic support for auth backends. We provide extended
support, and the LDAP, NIS, AD, etc. auth backends.
Django also provides the basic stuff like database storage for users,
active/inactive flags, etc. But it's up to us to make use of it all fo
Christian,
Is this a Reviewboard "feature" or a Django one? I would have guessed
this was a Django behavior. I'm not even a Django (auth) novice, let
alone expert, so sorry if this is a dumb question!
Chris
Christian Hammond wrote:
Hi Pablo,
No, there's no way to do this out of the box. Y
I achieved your aim for our local copy of ReviewBoard by snagging the existing
LDAP code, and modifying it slightly. I then used the modified code as a custom
authenticator.
That way, unauthorized people- not in the reviewboard DB - don't get
authenticated.
Eric
On Mar 23, 2011, at 8:29 AM, P
Thanks for your reply. I created this enhancement request:
http://code.google.com/p/reviewboard/issues/detail?id=2048
--
Want to help the Review Board project? Donate today at
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~
Hi Pablo,
No, there's no way to do this out of the box. You would need to write
a custom auth backend that augments the LDAP backend to so this.
There are plans in 1.6 to e-mail admins for new users. It'd make sense
to have an option to disable new users until the admin approves them.
If you want
Hi guys.
I have a RB installation validating against an LDAP server. It looks like RB
creates users in the local database whenever a user is correctly
authenticated with LDAP. What I need is a way to disable this automatic user
creation, so the site admin can decide which users in the full LDAP
