If you add fields to auth_user than you can still use CAS. If you use your own authentication logic, than I cannot say without more details.
On Saturday, 22 November 2014 00:55:52 UTC-6, LoveWeb2py wrote: > > Hello, > > I'm trying to use Web2py's CAS feature and database cooperation. I tried > to follow this article: > http://www.web2pyslices.com/slice/show/1877/single-login-by-two-different-ways > > And it looks good, but what if I'm using custom authentication? The > appliance found here: > https://github.com/mdipierro/web2py-appliances/tree/master/PyForum2 uses > custom authentication and I'm not what the best approach would be to use > central authentication between two appliances. > > Main appliance: Uses web2py's basic authentication > Forum Appliance: Uses custom auth here is a sample of the db.py > > ## Authentication Schema (3 tables) > db.define_table('auth_users', > db.Field('auth_email', 'string', length=128, > required=True), > db.Field('auth_passwd', 'string', length=128, > required=True), > db.Field('auth_created_on', 'string', required=True), > db.Field('auth_modified_on', 'string', required=True), > db.Field('is_enabled', 'boolean', required=False, > default=True), > migrate='auth_users.table', fake_migrate=fake_migrate) > > > Is CAS an option here? > > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
