Swapping out authentication logic in byteflow?

[Devye]

Hi,

I am not sure if this is more of a django question, but here is the
situation. We have an in-house built webapp that runs with a set of
use data. Byteflow is setup and runs on its own database perfectly.
But I wonder if it is possible to completely overwrite the login
authentication logic in byteflow to use an existing users table and
some already built login authentication / session logic? We like the
byteflow as a blogging engine but my boss is concerning about the
users integration and session /logs management integration between our
existing webapp and byteflow.
If we can somehow overwrite the login / authentication part of the
code and use our own python libs to manage users, authentication and
logs, it would be ideal; otherwise, do I have to maintain two copies
of user data?

Any pointers on how this may work would be appreciated!

[Alexander Solovyov]

On 2008-12-01, Devye wrote:

Built-in webapp means it is not django project? Then you should write an
authentication backend:

http://docs.djangoproject.com/en/dev/topics/auth/#other-authentication-sources

And then... uhm, you should either replace
django.contrib.auth.models.User model with something which point to your
user database (just with monkey-patching) or maybe creation of User in
your backend. Not sure what will be better in your situation.

--
Alexander