You can write a remote application for this. At least that's what I did.

Sure I can, but would be nice to have in standard installation :).

I agree on that

One hard part with implementing this is that Teaming does not store the user's password in clear text. So, it has to generate a new one for the user when they request it. This becomes a big Denial of Service problem (or at least a super annoyance problem). If I know your login name (which isn't hard in many cases), I can pretend to be you and claim I do not to know the password. Then, Teaming generates a new password and mails it to the user. The (proper) user will get the mail with the new password. But until they go through the process of restoring the password, they have to remember the new one. A "bad guy" could do this every hour for someone. It would drive them crazy. And, there is no way to figure out who is doing it since they are not logged in.

Also, we don't (at this point) have any way to store passwords back into the LDAP server. So this would only work for locally defined users.

The first problem can be solved with asking user for a answer to a secret question. The second way: when user clicks "I forgot password" he gets an email (on address defined in profile) with secret link to page where he can define new password in Teaming. With the second way it's possible to flood user with unwanted emails so it's better to combine both solutions.

You right: it can work only for local users.

Peter,

Does this mean there is a plan to sync passwords back to a LDAPed user?  It would be useful if both password and Email can be set via Teaming for a LDAP user!