Thomas Bechtold wrote:
> Public bug reported:
>
> Actually to use the lp-team<->django-group mapping, you have to define the variable OPENID_LAUNCHPAD_TEAMS_MAPPING {} for every group you want to map.
> For loco.ubuntu.com, the teams change from time to time and it's impossible (or stupid) to change the django settings.py file every time the teams change.
>
> It would be cool if the mapping is automatic. So if there are 3 django-
> groups, theses group are mapped automaticlly to lp-teams (and both have
> the same name, then).
>
> ** Affects: django-openid-auth
> Importance: Undecided
> Status: New
>
This seems to be reasonable. I also don't see any security impact since groups have no meaning until permissions are
assigned to them.
Perhaps the LAUNCHPAD_TEAMS_MAPPING could be a way of restricting which groups get created so your database doesn't get
cluttered with groups.
Thomas Bechtold wrote: ->django- group mapping, you have to define the variable OPENID_ LAUNCHPAD_ TEAMS_MAPPING {} for every group you want to map.
> Public bug reported:
>
> Actually to use the lp-team<
> For loco.ubuntu.com, the teams change from time to time and it's impossible (or stupid) to change the django settings.py file every time the teams change.
>
> It would be cool if the mapping is automatic. So if there are 3 django-
> groups, theses group are mapped automaticlly to lp-teams (and both have
> the same name, then).
>
> ** Affects: django-openid-auth
> Importance: Undecided
> Status: New
>
This seems to be reasonable. I also don't see any security impact since groups have no meaning until permissions are
assigned to them.
Perhaps the LAUNCHPAD_ TEAMS_MAPPING could be a way of restricting which groups get created so your database doesn't get
cluttered with groups.