We are planning on using Web2Py in a 3 tier release model (Development, Acceptance, Production) but as the ID fields in the auth tables are used as primary and foreign keys, we are concerned that this will cause inconsistencies between the different pillars. We will be using SSO for access to web2py and users and groups need to be defined via our company's identity management system. We plan on running scripts to update the Auth users and group tables based on a daily file feed.
We may need to create groups and group memberships manually in the development pillar which will later be defined in our identity management and AD systems to have them also in acceptance and production and so the IDs may become a mess. One idea we had is to override the generated IDs in the USER and GROUP tables with the ID from our single source identity feed using its unique keys (user_id and group_id from our internal systems), but we are not sure if this will create problems down the line with the other tables which use the automatically generated sequential ID's, for example, the auth_permission table. Any recommendations on how to deal with this issue in Web2Py releases ? Would our idea of replacing the ids with the unique id's provided by our internal systems be a solution or cause other issues ? Kind Regards, David -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/web2py/00691d6d-7d15-47e0-a27e-d19b601bee96%40googlegroups.com.
