Thinking about Kevin's idea (2).
What if I make plone export to the right mysql table
(auth_user, DATABASE_NAME 'myapps' for example) the fields:
id | username | first_name | last_name | email | password
| is_staff | is_active | is_superuser |
last_login | date_joined
Hi there, thanks for your replies.
Yes, Malcolm, I am reading this doc and following some discussion about ldap
authentication, but Kevin got the right point.
I will read more about backend authentication in django and then I will
check in plone (even plone-list) about ideas besides the ones
Tricky...how do you write a method in Django that can query Plone for
the existence of a user? A couple of thoughs:
1. Design an external method in Plone that takes a username/password
and returns true/false
2. Extend Plone to copy the users to a SQL table that you can then
access natively in
On Thu, 2009-02-19 at 10:20 +, Alan wrote:
> Hi There,
>
>
>
>
> We have Plone/Zope site for CMS and users registration. It came before
> django for us. But now we are developing portal applicatons done with
> django (much better to develop and maintain) and we have this question
> now:
Hi There,
We have Plone/Zope site for CMS and users registration. It came before
django for us. But now we are developing portal applicatons done with django
(much better to develop and maintain) and we have this question now: how to
allow a user to login in django portal using his/her login and
5 matches
Mail list logo
