Hello folks ... There is a bit of similarity with another thread below regarding 2 auth_user tables ( for 2 different logins or authentification methods in the same app) ! but before I dive in the question I want to ask, I need to share a bit of the nature and the genesis of the project that I am working on !
for my very first project dev in web2py .. it is a big one ! ( it is very important to me ! ) What I am building on my free time is this : The only full fledge online social network platform ( like facebook, myspace and others ... ) for all soccer players, contributors, actors and fans but ...... this online social network has soccer management tools embedded for different management levels ( team level, game level, club level. league level ... ) ! So this means that : players, coaches, referees, parents, fans, volunteers, teams, clubs, schools, leagues will have their own profile page ( and in the future, certain of these profile pages will need to have customization capabilities ( such as for clubs, schools etc ... ) .. and hopefully, in a near future certain amateur clubs will stop having websites that are not cared for and that nobody knows about their existence !! .. Now, in an application like this, I will need 2 login methods .... there is the normal login for the app ( the one that every one will use to access the app, its contents, its articles and news, its blogs, pics, fixtures, results, goal clips etc ! ) with the email address and password. ... and then ... once you are a member ....let's say - if you are the coach of a team, or a club administrator, or a league admin ... in order to have access to the admin panel of the adminsoccer modules for your team ( or the embedded soccer management application ) available to your category, or assigned to you, then you, as the user will have to login again somewhere else, with different credentials ( once you are in the main app ) for example for a coach, once he logs in, he will have to log in again to socceradmin by using his team_id and a password; And once the season is over ... by next season that same login information will dissolved .. the informations previously entered throughout the previous season will remain as archived information. .. and that same coach will have another team with another team_id and a new password on order to access the socceradmin panel !! Bref ! You get the idea !! .... You see the need to have 2 login schemes ...... does any one have any idea on how to have 2 auth_user tables in an app like this ... I was thinking of 1 auth_user - the main one ! and 1 auth_admin in a module for the socceradmin panel, that is renewed every year... giving access to various levels of admin tools depending on who you are or what you are registered as by the proper league authorities ! I am not there yet in my app dev initiative ! ... I wander how I will be able to have 2 auth_user tables in the same app in order to have 2 login scheme in web2py ???? ... any suggestion anyone ??? .. thank you ... Don --
