Thank you Ryan. I will provide feedback on this solution
On Saturday, September 7, 2024 at 5:45:59 PM UTC+4 Ryan Nowakowski wrote:
>
>
> On September 5, 2024 9:06:38 PM CDT, Asoma Samuel
> wrote:
>
> >I’ve overridden socket.getfqdn to return a specific local hostname in my
> >Django settings,
development server,
and I’m also unable to send emails from within the Django shell.
Additionally, we are experiencing issues with email delivery related to
user authentication with Djoser and JWT.
Problem Description
I’ve overridden socket.getfqdn to return a specific local hostname in my
Django
ption as e:
messages.error(request, e)
context = {
'form': form,
'value': demo
}
return render(request, 'index.html', context)
else:
context = {'form': form}
return render(request, 'index.html', context)
this is my code...I want to show failed mail to the
Hello everyone,
I want to create a user authentication app using ReactJS and django. But
facing problems in authenticating with the jsonwebtokens in ReactJS. Can
anybody provide correct guide of implementing DjangoRestFramework
simple-jwt and ReactJS jet ?
--
You received this message because
Use the relationship in this way
Product -> Seller-> User
Instead Product -> User -> Seller
On Wed, Aug 24, 2022, 7:18 PM MAHESH KUMAR
wrote:
>
> 1. User Authentication APIs:
> 1. get or create user by phone number, params: “phone_no”, response
> {“user_id”,”auth_
1. User Authentication APIs:
1. get or create user by phone number, params: “phone_no”, response
{“user_id”,”auth_token”},
2. get or create user by email, params: “email”, response
{“user_id”,”auth_token”},
how to write this i was try but i didn't get plz help sir
On Friday, Augu
Thank you for your response, I really appreciate this hope this helps me.
On Mon, 23 Nov, 2020, 7:36 pm mike vickers, wrote:
>
> https://simpleisbetterthancomplex.com/tutorial/2016/07/22/how-to-extend-django-user-model.html
>
> This is a nice reference that goes over the pros/cons of the differe
https://simpleisbetterthancomplex.com/tutorial/2016/07/22/how-to-extend-django-user-model.html
This is a nice reference that goes over the pros/cons of the different
approaches to your problem.
On Mon, 23 Nov 2020 at 08:41, Neeraj Rana wrote:
> I am trying to create two different types of users
I am trying to create two different types of users, prime and one prime
with that it also consist of email verification and custom username.
Now, my question is should I use the user auth model, and django.forms and
extend the form for email, phone no or should i build a completely new
model and
Hi all, pretty excited about our new guide to Django User authentication on
the Kite Blog <http://kite.com>.
Nice to have a reference if authentication maybe isn't your *favorite* part
of webdev.
https://kite.com/blog/python/django-authentication/
--
You received this message beca
hello django's
i am having an error while doing user authentication
plz have a look and respond asap
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an e
On Wed, Feb 12, 2014 at 4:02 PM, Ethan Lowry wrote:
> Hi Cal, first off thanks for the detailed response.
>
> Regarding your second reply I'm not sure I understand the question? The
> csrf issue I described *is* the reason I was unable to use POST requests,
> which is what I originally wanted to
Hi Cal, first off thanks for the detailed response.
Regarding your second reply I'm not sure I understand the question? The
csrf issue I described *is* the reason I was unable to use POST requests,
which is what I originally wanted to do.
I will look in to all the options in the links posted an
On Wed, Feb 12, 2014 at 3:17 PM, Cal Leeming [Simplicity Media Ltd] <
cal.leem...@simplicitymedialtd.co.uk> wrote:
> Hi Ethan, comments in-line;
>
>
> On Wed, Feb 12, 2014 at 1:41 PM, Ethan Lowry wrote:
>
>> Hi there,
>>
>> I have a bare-bones Django app set up and am planning on using the built
Hi Ethan, comments in-line;
On Wed, Feb 12, 2014 at 1:41 PM, Ethan Lowry wrote:
> Hi there,
>
> I have a bare-bones Django app set up and am planning on using the built
> in Django user auth to manage log in and registration via the Android app
> I'm developing.
>
> I've tried this a number of
>> Obviously this isn't an ideal or secure way of doing things and what I
originally tried was sending a POST request, but this gets denied with a
403 and a message about not having a CSRF cookie attached.
I haven't developed anything with Android but it sounds like you need to
send a CSRF in y
Hi there,
I have a bare-bones Django app set up and am planning on using the built in
Django user auth to manage log in and registration via the Android app I'm
developing.
I've tried this a number of ways and can, for example, log in by sending a
GET request such as ([url]/login?username=[us
On Monday, 20 January 2014 05:35:40 UTC, Chen Xu wrote:
>
> Hi Everyone,
> I am wondering how request.User get set during the authentication, do we
> have to do anything like:
>
> request.User = User() or it will have value by itself?
>
>
> Thanks in advance.
> --
> ⚡ Chen Xu ⚡
>
Did you try
on your view the request object will be populated already, it is meant for
read only, including the user object so you could check for example if the
current user is authenticated using the request.user object
good luck
On Mon, Jan 20, 2014 at 7:35 AM, Chen Xu wrote:
> Hi Everyone,
> I am wond
Hi Everyone,
I am wondering how request.User get set during the authentication, do we
have to do anything like:
request.User = User() or it will have value by itself?
Thanks in advance.
--
⚡ Chen Xu ⚡
--
You received this message because you are subscribed to the Google Groups
"Django us
Hi Everyone,
I am using sqlalchemy instead of Django's ORM for my new website, and I am
running into the incompatible user authentication issue, I am wondering if
there are any good python authentication library that allows both facebook,
google, twitter,etc login and its own email registr
On Thursday, July 4, 2013 11:30:06 PM UTC+5:30, vijay shanker wrote:
>
> *Hi*
> *I am using django 1.5 and created my own user model by AUTH_USER_MODEL=
> 'account.User' in settings.*
>
> *my user model is like this:*
>
> from django.db import models
> from django.contrib.auth.models import Abst
*Hi*
*I am using django 1.5 and created my own user model by AUTH_USER_MODEL=
'account.User' in settings.*
*my user model is like this:*
from django.db import models
from django.contrib.auth.models import AbstractBaseUser, UserManager,
PermissionsMixin
# Create your models here.
GENDER = (
Thanks for opening the ticket and thanks so much for the explanation as
well!
-evan
On Wednesday, June 19, 2013 7:13:04 PM UTC-5, Russell Keith-Magee wrote:
>
>
> On Thu, Jun 20, 2013 at 4:16 AM, Evan Stone
> > wrote:
>
>> Sure thing. Here are the snippets that gave me pause:
>>
>> "Think ca
On Thu, Jun 20, 2013 at 4:16 AM, Evan Stone wrote:
> Sure thing. Here are the snippets that gave me pause:
>
> "Think carefully before handling information not directly related to
> authentication in your custom User Model.
>
> It may be better to store app-specific user information in a model th
Also, thank you again!
On Wednesday, June 19, 2013 3:16:05 PM UTC-5, Evan Stone wrote:
>
> Sure thing. Here are the snippets that gave me pause:
>
> "Think carefully before handling information not directly related to
> authentication in your custom User Model.
>
> It may be better to store app-s
Sure thing. Here are the snippets that gave me pause:
"Think carefully before handling information not directly related to
authentication in your custom User Model.
It may be better to store app-specific user information in a model that has
a relation with the User model. That allows each app t
On Tue, Jun 18, 2013 at 11:37 PM, Evan Stone wrote:
> Russ,
>
> Thanks so much for getting back to me! I shouldn't have posted that
> without my code in front of me... (was posting from my phone, in bed)
>
> It turns out that I did NOT have AUTH_USER_MODEL set. I had
> AUTH_PROFILE_MODULE set.
>
Russ,
Thanks so much for getting back to me! I shouldn't have posted that without
my code in front of me... (was posting from my phone, in bed)
It turns out that I did NOT have AUTH_USER_MODEL set. I had
AUTH_PROFILE_MODULE set.
I changed it to AUTH_USER_MODEL and followed the custom user mo
On Mon, Jun 17, 2013 at 10:31 PM, Evan Stone wrote:
> Per the docs for Django 1.5, I have attempted to broaden the range of data
> held in the default user model by making an extended user model with the
> AbstractUser class. I made the model (called "Client") and listed it in
> settings.py as th
Per the docs for Django 1.5, I have attempted to broaden the range of data
held in the default user model by making an extended user model with the
AbstractUser class. I made the model (called "Client") and listed it in
settings.py as the AUTH_USER_MODEL. Syncdb took it and it worked great.
Spe
This helped alot and solved the issue.
Thanks
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, s
On Fri, Jun 14, 2013 at 3:29 PM, shashank sandela
wrote:
> As you can see in the views.py I did import the class
> EmailOrUsernameModelBackend.
OK. But you mustn't import that class, you must allow django to import
it itself, and then django will use it when authenticating users.
You do this by
Sorry. The error was:
AttributeError at /authentication/
'User' object has no attribute 'backend'
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users
As you can see in the views.py I did import the class *
EmailOrUsernameModelBackend.*
*
*
Now when I used " *user =
EmailOrUsernameModelBackend().authenticate(username=username,
password=password) *"
It gave an error saying:
AttributeError at /tangle/auth/
'User' object has no attribute 'backen
El 14/06/2013 07:26 a.m., shashank sandela escribió:
unbound method authenticate() must be called with EmailOrUsernameModelBackend
instance as first argument (got nothing instead)
Hi. Remember that you must import a function before you call it. This is
a reference to authentication in Django
h
On Fri, Jun 14, 2013 at 12:56 PM, shashank sandela
wrote:
> Hi,
>
> I created a backends.py in my project folder.
>
> backends.py ::
>
> from django.conf import settings
> from django.contrib.auth.models import User
>
> class EmailOrUsernameModelBackend(object):
> def authenticate(self, userna
Hi,
I created a backends.py in my project folder.
backends.py ::
*from django.conf import settings*
*from django.contrib.auth.models import User*
*
*
*class EmailOrUsernameModelBackend(object):*
*def authenticate(self, username=None, password=None):*
*if '@' in username:*
*
On 31 May 2013, at 12:36, tony gair wrote:
>
> I'm trying to write my first django app using cbv's and good practice ala 2
> scoops!
>
> (thanks for all the help so far in this forum btw!)
>
> I have constructed the app using django braces and CBV's and have noticed
> that I can only authent
I'm trying to write my first django app using cbv's and good practice ala 2
scoops!
(thanks for all the help so far in this forum btw!)
I have constructed the app using django braces and CBV's and have noticed
that I can only authenticate into my app through the admin panel.
I suspect that dj
Thanks Frank, will look into this set of openid providers.
Pratik
On Wed, Mar 13, 2013 at 4:28 PM, Frank Bieniek <
frank.bien...@produktlaunch.de> wrote:
> Hi Pratik,
> we have glued something together for openid.
>
> git+git://github.com/openid/python-openid.git@7d65da5987
> django-tastypie
>
Hi Pratik,
we have glued something together for openid.
git+git://github.com/openid/python-openid.git@7d65da5987
django-tastypie
django-guardian
hg+http://bitbucket.org/jezdez/django_openid_provider/@746ab34a974a
django-social-auth
oauth2
# iptools/netaddress tools for the api access based on ip
Thanks for reminding about OAuth2.
The API use case I'm currently dealing with includes authenticating my own
clients with my server, not third party apps. Hence Oauth2 seems a bit
weird here in terms of usability since it will ask user for permission to
access the backend service when they visit
NO! - THERE IS RESTFUL METHOD OF AUTHENTICATION!
Use OAuth2.
RFC6749. There are a bunch of server implementations for Django. Use
one of them.
On Wed, Mar 13, 2013 at 8:06 PM, Pratik Mandrekar
wrote:
> Thank you for the response!
>
> As Nick & Jani have pointed out, I figured out that there is
Thank you for the response!
As Nick & Jani have pointed out, I figured out that there is no RESTFul way
for authentication. Neither is there one good way all clients could access
the api i.e Browsers can use Session Based Authentication while Mobile
clients are better of using API based/digest aut
On 12/03/2013 01:06 μμ, Jani Tiainen wrote:
There is not exactly "RESTful way to authenticate", since after all
REST is just an architecture to represent different resources and thus
it's totally agnostic what comes to authentications and such.
Simplest one (if you're use HTTP(S)) is to use
10.3.2013 22:54, Pratik Mandrekar kirjoitti:
Hello,
I'm trying to figure out what would be the best way to integrate django
with ember.js/backbone from the user authentication point of view. I'm
using Tastypie for creating RESTful resources.
I have no problem creating APIs once a use
You'll want to setup an OAuth2 server for this.
On 11/03/2013 7:54 AM, "Pratik Mandrekar" wrote:
> Hello,
>
> I'm trying to figure out what would be the best way to integrate django
> with ember.js/backbone from the user authentication point of view. I'm
al security > use Dajngo API key Authentication
More secure > use OAuth mechanism
hope it helps!
On Sunday, March 10, 2013 4:54:10 PM UTC-4, Pratik Mandrekar wrote:
>
> Hello,
>
> I'm trying to figure out what would be the best way to integrate django
> with ember.js/
to integrate django
> with ember.js/backbone from the user authentication point of view. I'm
> using Tastypie for creating RESTful resources.
>
> I have no problem creating APIs once a user has been authenticated using
> the Session based authentication but I am wondering wh
On 10/03/2013 10:54 μμ, Pratik Mandrekar wrote:
Hello,
I'm trying to figure out what would be the best way to integrate
django with ember.js/backbone from the user authentication point of
view. I'm using Tastypie for creating RESTful resources.
I have no problem creating APIs o
Hello,
I'm trying to figure out what would be the best way to integrate django
with ember.js/backbone from the user authentication point of view. I'm
using Tastypie for creating RESTful resources.
I have no problem creating APIs once a user has been authenticated using
the Ses
Hello.
I want to register users.
So I made a RegisterForm(ModelForm):
Class Meta:
model=User (from django.auten.contrib.User)
no i display that form in a view and submit it.
When i do form.is_valid(), i get this validation error: Your username
and password didn't match. Please try again.
According to the docs you just need to add
{% csrf_token %}
to each form.
sorry for the noise.
On Dec 30, 5:15 pm, aaron wrote:
> okay, so I added a url directing accounts/login requests to a view
> which in turn directs it to the login.html template suggested at
>
> http://docs.djangoproject.
sword
{% endif %}
{% csrf_token %}
User name:
Password:
{% endblock %}
Any ideas?
Cheers,
Aaron
On Dec 30, 4:33 pm, aaron wrote:
> Hi guys,
>
> I'm attempting to follow the very simple setup for user authentication
> in Django as detailed in
okay, so I added a url directing accounts/login requests to a view
which in turn directs it to the login.html template suggested at
http://docs.djangoproject.com/en/dev/topics/auth/
Which is:
{% extends "base.html" %}
{% load url from future %}
{% block content %}
{% if form.errors %}
Your use
Hi guys,
I'm attempting to follow the very simple setup for user authentication
in Django as detailed in the documentation here:
http://docs.djangoproject.com/en/dev/topics/auth/
I've got a database synced, the apps installed as detailed, but when I
attempt to access a password protec
Long story short have several django projects running
I log in ok and the projects run fine using the admin interface.
However :
I have added users and given them access to only certian applications
on the django site using the admin interface, however when i log in
with out supervisor access ch
Is there a recommended way of implementing object permissions with
Django's User authentication systems (i.e. a way of enforcing access/
authorisation restrictions on an object-basis)?
The Django documentation states that there is "a foundation for object
permissions, though t
I have a budgeting application I created at inzolo.com. I want to
create an affiliate program to offer commissions to those who refer
paying users to the site. I will basically have a different login and
just for affiliates. I'm wondering how to best handle this situation.
Can I copy the auth.use
>
> There are a few different suggestions in this [1] stack overflow
> question. Since request.COOKIE['session'] didn't work, you might try
> one of the others.
>
> [1]http://stackoverflow.com/questions/526179/in-django-how-can-i-find-ou...
That was very helpful, Xiong. Thanks. I'm getting clos
On Jul 8, 9:40 am, Jarmo wrote:
> > You need to send the 'sessionid'. It's in request.COOKIES.
> So I have to send the sessionid in the HttpResponse back to the client
> for it to use, right? I tried getting it from the Request object
> after I successfully logged in. But it wasn't in the COOKI
>
> You need to send the 'sessionid'. It's in request.COOKIES.
Thanks for the quick reply, Jashugan.
So I have to send the sessionid in the HttpResponse back to the client
for it to use, right? I tried getting it from the Request object
after I successfully logged in. But it wasn't in the COOK
On Jul 8, 6:29 am, Jarmo wrote:
> If someone can help me understand what I need to send up in the HTTP
> headers, I would greatly appreciate it.
You need to send the 'sessionid'. It's in request.COOKIES.
--~--~-~--~~~---~--~~
You received this message because yo
I'm writing my client using GWT and my back-end is being written with
Django. I've had no issues making the two work together - they've
tied together very nicely.
I've just added my login functionality (as I'm getting to the point
where "who" you are matters) and I've written a a view method to
Hello.
I'm trying to log a user in using the @login_required decorator. I've
followed the examples on
http://docs.djangoproject.com/en/dev/topics/auth/#topics-auth but I can't
get it to stop spiraling into a redirect loop. I've tried everything I can
think of but I'm out of ideas. Please help.
My
Hi
Further to the above discussion,
I did implement the code and it worked for me for the authentication
while using the email id as the username
(username=emailid ; valid_user = authenticate (username=username,
password=password )
# django-admin.py --version
1.1 beta 1 SVN-10957
1.) The pro
On 11 mai 09, at 23:16, Bobby Roberts wrote:
> The question is, is there anyway to take the hashed password and
> work it back to plain text so it can be used in login? Is there
> another way to do this? Can it even be done at all?
>
No.
For what it's worth, a better option might be to loo
*hashed
On May 11, 5:16 pm, Bobby Roberts wrote:
> hi group -
>
> i've read the docs but can't find an answer to a particular question.
> In theory it's quite simple but I need help. Our company has a
> central database system from which we authenticate. The idea is to let
> employees have a ce
hi group -
i've read the docs but can't find an answer to a particular question.
In theory it's quite simple but I need help. Our company has a
central database system from which we authenticate. The idea is to let
employees have a central login across websites. In other words, if
they login as
nvoices/84 and Bob can see invoice 84 but that invoices isn't
> registered to him, its for a different customer entirely.
>
> Obviously I'm missing some authentication magic to stop that
> happening. Question is I'm not sure how to go about that - is there a
> straightforw
ferent customer entirely.
Obviously I'm missing some authentication magic to stop that
happening. Question is I'm not sure how to go about that - is there a
straightforward way I can implement more robust user authentication so
a customer only sees the invoices they are destined to view!?
You please check the satchmo package there they are using email as
username in satchmo-registration using
user=generate_id(email,firstname)
On Apr 13, 9:44 am, pkenjora wrote:
> Malcolm, <- Remembered the 'l' this time!
>
> To keep things simple and avoid fragmenting this discussion into a
> mi
Malcolm, <- Remembered the 'l' this time!
To keep things simple and avoid fragmenting this discussion into a
million different dead end tit for tats , I'll try to reign in the
main points.
1. The default authentication method in Django should have no inherent
restrictions. Such as blocking '@'
On Sat, 2009-04-11 at 07:52 -0700, pkenjora wrote:
> Malcom,
Well, I'm not "Malcom" (sic), but I'll reply anyway.
>Google, FaceBook, and LinkedIn have been using email authentication
> for how long now? With the default constraints you've put on Django a
> developer would have to "work arou
On Sat, Apr 11, 2009 at 10:52 AM, pkenjora wrote:
>
> You are correct, username authentication has always been around.
> However, the explicit banning and obfuscating of email authentication
> in the default module has not. That is the part that worries me, that
> is where things are going wron
Malcom,
Google, FaceBook, and LinkedIn have been using email authentication
for how long now? With the default constraints you've put on Django a
developer would have to "work around" the out of the box code to make
the project behave like the big 3 names on the web. In this light it
sounds
On Tue, 2009-04-07 at 10:16 -0700, pkenjora wrote:
> Hi,
>
> Why not remove the '@' filter and allow the specific project
> developer the freedom to use email as username? What was the
> reasoning behind this?
One reason is that usernames can be made to be unique, since you're
selecting a new
I use an EmailBackend for auth, found on django snippets
http://www.djangosnippets.org/snippets/74/
(though the one pkenjora posted looks the same but slightly better.)
and a generate_username to create a clean unique username when creating
accounts,
also found on django snippets
http://www.djang
Hi Again,
Here is what we used to get around the email restriction. It works
very well for authenticating through your application, Admin is a
different story. In our case the users who register online never need
to log into admin. If yours do, then you will have to strip logic
from several
Hi,
Why not remove the '@' filter and allow the specific project
developer the freedom to use email as username? What was the
reasoning behind this?
I always like Django because it didn't try to force development down
a specific path. All developers have their own way and every project
is
The slugify function may also provide you with valid usernames, if you
feed it with first and last name for example. But always be certain,
that the username is unique, just as malcolm described.
--~--~-~--~~~---~--~~
You received this message because you are subscr
On Thu, 2009-04-02 at 19:04 -0700, Timboy wrote:
> What's the best way to add users with an auto generating username? ie:
> Taub.John, Smith.Tim, Smith.Tim2
You can do it however you like, since the user will never see it.
Something as simple as taking the email address, replacing "@" with "AT"
a
What's the best way to add users with an auto generating username? ie:
Taub.John, Smith.Tim, Smith.Tim2
On Apr 1, 3:37 am, johan.u...@student.hpi.uni-potsdam.de wrote:
> Best way is to write your own authentication backend I think.
>
> Check the
> docs:http://docs.djangoproject.com/en/dev/topic
Best way is to write your own authentication backend I think.
Check the docs:
http://docs.djangoproject.com/en/dev/topics/auth/?from=olddocs#writing-an-authentication-backend
This article might also give you a good idea:
http://scottbarnham.com/blog/2008/08/21/extending-the-django-user-model-wit
The authentication model provided along with django is based on
username.
What to do to change the authentication based on email instead of
username?
To be more specific
~~~
With username authentication , to login user we do the following
user = authenticate(name,password)
The authentication model provided along with django is based on
username.
What to do to change the authentication based on email instead of
username?
To be more specific
~~~
With username authentication , to login user we do the following
user = authenticate(name,password)
Peter,
I don't disagree with you. However, based on Glen's security report
( I suspect they are using Nessus/Retina to produce the scan result
i.e. CVE - Common vulnerabilities and exposure ),his question was:
Does anyone know where to find such "stamp of approval" or "denial"
from HIPAA's point
> You speak
> of HIPAA which translates to FISMA requirements.
I suspect they are complementary, not equivalent.
> I assume your web
> application i.e MYSQL will be storing Personal Identifiable
> Information (PII) such SSN, etc... In this case, you may have tough
> battle getting your web appl
them to ask about that system specifically.
> The data is stored in a MySQL database and the standard
> Django User Authentication model is used (out of the box with no changes).
> Since security is a concern for the customer, I wanted to find all
> information from HIPAA regarding the Dja
s software in a more public arena. He
> has to get HIPAA approval. The data is stored in a MySQL database and
> the standard Django User Authentication model is used (out of the box
> with no changes). Since security is a concern for the customer, I
> wanted to find all
I have a customer who has a Django application that I have upgraded to
Django 1.1.
The customer wants to take this software in a more public arena. He
has to get HIPAA approval. The data is stored in a MySQL database and
the standard Django User Authentication model is used (out of the box
ad777 wrote:
> Hi there,
>
> I am new at django and I was wondering what is the best way of
> redirecting users to their own customized page after they get
> authenticated. I have extended the user model to include a unique
> user id for each user... is it somehow possible to use this?
The user
Hi there,
I am new at django and I was wondering what is the best way of
redirecting users to their own customized page after they get
authenticated. I have extended the user model to include a unique
user id for each user... is it somehow possible to use this?
Thanks.
--~--~-~--~~
ur settings?
> > "django.core.context_processors.auth"
>
> > Alfonso wrote:
> > > Hey,
>
> > > I've implemented a user login widget on my site. A simple 'Sign in'
> > > at top of every page that turns into 'Welcome John, View you
n your settings?
> "django.core.context_processors.auth"
>
> Alfonso wrote:
> > Hey,
>
> > I've implemented a user login widget on my site. A simple 'Sign in'
> > at top of every page that turns into 'Welcome John, View your profile'
> > following successful
lcome John, View your profile'
> following successful user authentication. Works great - only issue
> I'm having is that on home page the text reverts to 'Sign In' even
> when user is logged in, only happens on this page. Not sure why this
> is occurring. Code below
Hey,
I've implemented a user login widget on my site. A simple 'Sign in'
at top of every page that turns into 'Welcome John, View your profile'
following successful user authentication. Works great - only issue
I'm having is that on home page the text reverts t
this works, Thanks!
On Jun 27, 7:24 pm, Alex Slesarev <[EMAIL PROTECTED]> wrote:
> On Jun 28, 1:13 am, hyde <[EMAIL PROTECTED]> wrote:
>
> > How to control thesessiontimeoutvalue if using Django's default
> > user authentication?
>
> Look in django docs
On Jun 28, 1:13 am, hyde <[EMAIL PROTECTED]> wrote:
> How to control the session timeout value if using Django's default
> user authentication?
Look in django docs (available in svn trunk). You should set
SESSION_COOKIE_AGE variable (in seconds) in the
1 - 100 of 153 matches
Mail list logo
