Andrea,
Point #2 was about this:
--- agilo/utils/usermanager.py (revision 578)
+++ agilo/utils/usermanager.py (working copy)
@@ -47,12 +47,16 @@
if not password:
password = user
self.accMgr.set_password(user, password)
- self.perm.grant_permission(user, Role.TEAM_MEMBER )
+ self.set_user_as_team_member(user)
What happens is that you can add permissions without FIRST adding
users. So if you try to blindly insert a row into the permission
table, you get an exception. So the one line patch that adds the
permission only if it didn't already exist. The function
usermanager.py::set_user_as_team_member does just that.
If your target user is the corporate user with a Windows AD
deployment, I feel that you should package the accountmanager plugin
with Agilo. I know this is not an Agilo problem, but current solutions
are really really bad (and this is a euphemism!).
I uploaded my accountmanager-ldap-agilo patch to trac-hacks:
http://trac-hacks.org/attachment/ticket/1147/acct_mgr_ldap_agilo.patch
I am interested in getting a dev account, but I am not sure what
changes that I have made will be useful to you guys. I can submit my
patches and you can probably put it on a branch or in a contrib/ area.
-Ashwin
On Apr 27, 3:59 am, Andrea Tomasini <[email protected]>
wrote:
> On 24 Apr, 2009, at 22:13 , cybernytrix wrote:
>
>
>
> > I reworked some Agilo-AccountManager related features:
> > 1. Delete user (not remove user) deletes the user via
> > acct_mgr::delete_user as well
>
> Ok, thanks :-)
>
> > 2. Fixed grant permission bug that raises exception if user with same
> > credentials is present and you try to create the user again.
>
> This is what trac is doing as well... may be it is as design?
>
> > 3. Do not assign to team_member.full_name team_member.email since it
> > creates the user in the DB and acct_mgr::has_user will always return
> > true.
>
> So may be we can set it after the user has been created... the whole
> Admin needs rework, we are going to Open the Agilo for Agilo
> development at the end of this sprint, probably this week, we are not
> yet done with the 0.8 but we need your help :-) And we count on the
> community support to fix and move forward the project... so if you
> want to have a "dev" account, please contact us :-)
>
> > 4. Since I am using LDAP to get user info, I made the full name /
> > email fields as read only after the account is created. I have
> > acct_mgr patches for those interested (it works with windows AD as
> > well).
>
> That would be interesting... we can create a contrib area, and put
> there all the "extra" patches... or may be we find a way to do it at
> runtime, and detect on the fly which authentication is set ;-)
>
> Thanks, I'll take the patch in, I think I'll need to modify something
> though, the 0.8 is already pretty changed ;-) Thank you very much for
> the improvements ;-)
>
> Best
> ANdreaT
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Agilo for Scrum" group. This group is moderated by agile42 GmbH
http://www.agile42.com and is focused in supporting Agilo for Scrum users.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/agilo?hl=en
-~----------~----~----~----~------~----~------~--~---
