No, he don't, web2py will try each access method with the credentials... If
he provide the proper username and password he will log in one or the other
LDAP instance... Then you need to dertermine which instance it is beyound
the scene by querying the LDAP instance and determine which one it is and
The user should choose because he can have account on both server (and even
use the same credentials for both).
I will dig into the post you linked.
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.c
"to know", not "to no"
On Tue, Dec 15, 2015 at 4:54 PM, Richard Vézina wrote:
>
> http://stackoverflow.com/questions/749268/how-can-i-find-out-which-server-hosts-ldap-on-my-windows-domain
>
> This should let you query LDAP instance to no which one it is then you can
> manage you flag by updating
http://stackoverflow.com/questions/749268/how-can-i-find-out-which-server-hosts-ldap-on-my-windows-domain
This should let you query LDAP instance to no which one it is then you can
manage you flag by updating the authenticated user record...
This should work or I miss something?
Richard
On Tue,
Why user should decide? I was on the impression that the limitation was
more because one user may not be present in LDAP instance and you want them
to log despite that... Maybe I was wrong in my assomption...
Richard
On Tue, Dec 15, 2015 at 3:35 PM, Jonathan R wrote:
> The answer is actually in
The answer is actually in your question. like I said I'm using the solution
2 and I need a way to determine which instance I'm talking to.
I'm using a boolean in my queries to assign the correct information but I
need a way to set the value of the boolean accordingly.
that's the only purpose of
What is exactly you issue with option 2... It should be straigh forward...
It a matter of using python ldap properly... You need also a way to
determine which LDAP instance you are talking to ...
Richard
On Tue, Dec 15, 2015 at 2:58 PM, Jonathan R wrote:
> The thing is we want to keep informati
The thing is we want to keep information from each server separated. so
solution 1 is not good for me.
I already use a variant of your option 2 where I grab the user credentials
on login and use it to query the server.
We have 2 servers, "test" and "prod" and we want to have one app to query
bot
So, I see 2 options :
1) Define a common user that has the required level of access to both ldap
server so you can query both server doesn't matter which server user are
autheticated to...
2) Use user credentials to access data you need... This is actually is not
actually what ldap_auth is doing, b
It's what I'm using right now (I can log with users from both servers) but
I use the same credentials to process the queries that gather datas for my
app (list of users, list of computers,...) and I need to know on which
server the user is authenticated to in order to use the correct information
What about setting 2 ldap authentication ?
In web2py you can login with multiple login methods and web2py use them in
the order they are specified in auth.settings.login_methods... If password
fail for one it tries with the other...
Here my settings :
auth.settings.login_methods = \
[auth,
I have two distinct sources of authentication ( 2 ldap servers) and I use
the credentials provided by the user to perform the query that gather
information on the ldap server on which the user is authenticated.
In an effort to follow the DRY concept my function that gather information
can query
:)
For what...
On Tue, Dec 8, 2015 at 2:18 PM, Jonathan R wrote:
> I need to have this radio button,
> is there a variable that stores the value of the radio button before
> processing the form ?
>
> On Tuesday, December 8, 2015 at 11:03:40 AM UTC-5, Richard wrote:
>>
>> You should have a loo
I need to have this radio button,
is there a variable that stores the value of the radio button before
processing the form ?
On Tuesday, December 8, 2015 at 11:03:40 AM UTC-5, Richard wrote:
>
> You should have a look at web2py auth... I guess no one really need to
> customize login form... Th
You should have a look at web2py auth... I guess no one really need to
customize login form... There is surely a way to customize it, and you
seems to have found a way... You may also, ask yourself about why you do
that and if you really need to do it... Or could it be crafted
differently... For in
Yes I did, and nothing changed on the login screen, I still had None
displayed instead of the radio button.
I feel like there is a simple easy way to add a field in the login screen
and save it but I can't see it...
On Monday, December 7, 2015 at 9:42:51 PM UTC-5, Richard wrote:
>
> Did you
Did you try by simply specify :
Field('radio_button', ..., readable=True, writable=True)
?
Richard
On Mon, Dec 7, 2015 at 5:19 PM, Jonathan R wrote:
> I successfully added the radio button i wanted on my login page but
> instead of using a column in the auth_user table I only created a radio
I successfully added the radio button i wanted on my login page but instead
of using a column in the auth_user table I only created a radio button that
will assign its value in a session variable. To do so I need to modify the
if form.accepts(): block to gather the value on submission but I'm no
18 matches
Mail list logo
