It's all right here:
https://docs.djangoproject.com/en/1.3/howto/auth-remote-user/
and other details in the mailing list thread you are reading/posting to
(this one!)
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To view this discussion on
HI I just like to know how to login to the django admin using remote
data (wherever it may be from)
On Jun 28, 1:28 am, Jeff Blaine wrote:
> Sorry, I have no knowledge of Oracle SSO, what it allows, how it works, etc.
--
You received this message because you are subscribed
Sorry, I have no knowledge of Oracle SSO, what it allows, how it works, etc.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-users/-/kFeKEvDSqZYJ.
To post to this
Hi
I have a problem in my application, we are implementing oracle single
sign on to our existing django application, I managed to implement SSO
for the application, but I can able use the same information to login
into Django admin.
I like to know how to use the SSO login User information to log
Thanks Jacob and Ramiro.
I finally figured it out, and unfortunately it was, of course, something
stupid :(
I had changed the directory name holding my WSGI app and had not changed the
Apache config's path reference in *both* places (ScriptAlias and
Directory). SIGH.
That was causing the
On Thu, May 19, 2011 at 6:02 PM, Jeff Blaine wrote:
> I'm kind of at the point where I consider this a bug in some fashion,
> regardless
> of my specific problem (which persists).
Well the auth application has a rather large set of tests that exercises
both creating,
I'm kind of at the point where I consider this a bug in some fashion,
regardless
of my specific problem (which persists).
AUTHENTICATION_BACKENDS = (
'mybackends.MyRemoteUserBackend',
)
If I define AUTHENTICATION_BACKENDS in settings, no default fallen
back on. If my hand-specified stuff
I'm failing so far.
I copied backends.py to my project root as mybackends.py
I edited it and renamed ModelBackend to MyModelBackend
I changed RemoteUserBackend(ModelBackend)
to MyRemoteUserBackend(MyModelBackend)
I changed settings.py to:
AUTHENTICATION_BACKENDS = (
Also, FWIW, the REMOTE_USER is definitely getting set to 'jblaine'
1xx.xx.xx.231 - jblaine [17/May/2011:16:12:41 -0400] "GET
/static/admin/img/admin/nav-bg.gif HTTP/1.1" 200 273
"http://rcf-hostdb.our.org/admin/; "Mozilla/4.0 (compatible; MSIE 7.0;
Windows NT 6.1; WOW64; Trident/4.0; SLCC2;
On Tuesday, May 17, 2011 3:10:03 PM UTC-4, Jacob Kaplan-Moss wrote:
>
> On Tue, May 17, 2011 at 2:00 PM, Jeff Blaine wrote:
> > That gets us somewhere, because authenticating to Apache/LDAP as jblaine
> > did NOT make a Django user jblaine.
>
> That's interesting - perhaps LDAP
On Tue, May 17, 2011 at 2:00 PM, Jeff Blaine wrote:
> That gets us somewhere, because authenticating to Apache/LDAP as jblaine
> did NOT make a Django user jblaine.
That's interesting - perhaps LDAP is reporting a different username?
You could check in the auth_user table to
[ *sigh* - I wish the web UI to google groups had an 80-column marker. ]
[ Sorry for the formatting in the previous message. I'm used to hitting ]
[ enter. ]
Thanks for the reply, Jacob.
That gets us somewhere, because authenticating to Apache/LDAP as jblaine
did NOT make a Django user jblaine.
On Tue, May 17, 2011 at 1:31 PM, Jeff Blaine wrote:
> Hi folks,
> I'm successfully using Apache with mod_authnz_ldap, WSGI, Django 1.3. If I
> hit
> '/admin', I get asked to authenticate (BasicAuth done through LDAP). I
> succeed.
> However, this just results in me then
Hi folks,
I'm successfully using Apache with mod_authnz_ldap, WSGI, Django 1.3. If I
hit
'/admin', I get asked to authenticate (BasicAuth done through LDAP). I
succeed.
However, this just results in me then seeing the Django admin login screen
instead
of logging me in to Admin.
What am I
14 matches
Mail list logo