Possible bug with renaming accounts

[tsihh]

Hi,

We are on the process of changing the usernames from short to full
address and we have 7 subdomains. While using command "python gam.py
update user x123 username x123.y123 GAM also creates an alias of the
old username (i do not know when this feature was added). This alias
seems to work only for the primary domain, sending to subdomains ends
with error "The email account that you tried to reach does not exist"

Possible solutions:
Use the older GAM and create these aliases manually
Use current version but delete and recreate the alias
Use Web interface to delete and recreate the alias

Rgds,
Ahti

[Gerard Duerrmeyer]

When I first found GAM, I was looking for it with the express purpose
of wanting to rename an account. The version was gam-0.010b
If memory serves, after renaming the account I also found the
"unadvertised" alias feature. I didn't mind it but it surprised me
enough that it happened without indication that it would happen that I
still remember it.
I believe this "feature" you talk about has thus existed since at
least gam-0.010b.
Personally I would vote for the addition of an --argument that would
disable the alias creation, much like the recently added --argument
for disabling the rename of account upon deletion, this being a fourth
solution to the three you mentioned.

Good luck!

> --
> You received this message because you are subscribed to the "Google Apps Manager" group.
> To post to this group, send email to
> google-ap...@googlegroups.com
> To unsubscribe from this group, send email to
> google-apps-man...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/google-apps-manager
>

[Jay Lee]

Hi Ahti,

When an account is renamed, the alias/nickname pointing to the old
username is created by Google's servers as part of the rename call,
GAM does not directly create the nickname and it would be necessary
for GAM to make an additional call to delete the nickname. Since
Google does this automatically, GAM also leaves it to the admin to
delete the nickname if they deem necessary. See the API docs note at:

http://code.google.com/googleapps/domain/gdata_provisioning_api_v2.0_developers_protocol.html#Rename_Account_Example

and GAM's documents the behavior at:

http://code.google.com/p/google-apps-manager/wiki/ExamplesProvisioning#Update_(and_Rename)_a_User

I could add an additional command parameter to GAM, something like
"noalias" which would remove the alias but that would be an additional
API call after the rename so it's really no different than doing a
"gam delete alias" command after the rename. There is no way to
prevent Google from creating the alias in the first place.

I was however able to reproduce the issue with the created alias not
working on the alias domain. I'll file a bug report with Google on
this.

Jay

[tsihh]

Hi all,

On Nov 14, 3:57 pm, Gerard Duerrmeyer <g.duerrme...@gmail.com> wrote:

> I believe this "feature" you talk about has thus existed since at
> least gam-0.010b.

Then it is probably Google who has disabled this feature for a while
and then enabled it again as when i first tested GAM in september i
had to manually recreate the alias for the old username

> Personally I would vote for the addition of an --argument that would
> disable the alias creation, much like the recently added --argument
> for disabling the rename of account upon deletion, this being a fourth
> solution to the three you mentioned.

Yes it could be an argument but at the moment it should be noted in
documentation

On Nov 14, 4:21 pm, Jay Lee <jay0...@gmail.com> wrote:
>   When an account is renamed, the alias/nickname pointing to the old
> username is created by Google's servers as part of the rename call,
> GAM does not directly create the nickname and it would be necessary
> for GAM to make an additional call to delete the nickname. Since
> Google does this automatically, GAM also leaves it to the admin to
> delete the nickname if they deem necessary. See the API docs note at:
>

> http://code.google.com/googleapps/domain/gdata_provisioning_api_v2.0_...

I know that documentation but as this is more like "unknown language"
for me then i did not read it :) Anyway thank you for pointing it out

> I could add an additional command parameter to GAM, something like
> "noalias" which would remove the alias but that would be an additional
> API call after the rename so it's really no different than doing a
> "gam delete alias" command after the rename.

I do not know how many GAM users have domain aliases to worry about :)
In the beginning just a note about that issue would be enough for me

> There is no way to
> prevent Google from creating the alias in the first place.

I believe that

> I was however able to reproduce the issue with the created alias not
> working on the alias domain. I'll file a bug report with Google on
> this.

Thank you.

Rgds,
Ahti