Multi Domain Rename (olddomain.com to newdomain.com) Causes new account

[Logi]

Problem: When submitting a rename for a user to change their domain some of the renames become new users. 

Example: jon...@foo.com needs to now be jon...@foobar.com

We submit a rename for the user using provisioning multi domain api. This user is not renamed and soon after we see a second account (NEW) created for jon...@foobar.com. 

Note: This occurs every once in awhile. Other renames using same code work fine. 

Additional Info: The code was created by the clients development team. They check their internal logs and see no errors or abnormal behavior between a rename that works and one that fails and creates second account. 

They ensure the code is fine. 

Wanted to know if this can actually happen (someone seen it before) as the new user xml and POST url are totally different from a rename user xml and PUT url... 

If their is a Googler on the dev team who can look at the accounts (i have examples) and see how it was submitted to Google .. etc.. to help me get to the bottom of this .. would be great.. 

I need to tread carefully as its a big client and their are very reliant on their internal dev team.

Thanks 

LOGI

[Alexandre Jacquet]

Hello Logi,

If you could share your code with us. The rename using MDM works fine for me.

PUT https://apps-apis.google.com/a/feeds/user/userEmail/2.0/foo.me/jon...@foo.com

In the XML you should up like this.

account.addProperty("newEmail", "jon...@foobar.com");

Ref. http://code.google.com/intl/en/googleapps/domain/gdata_provisioning_api_v2.0_developers_protocol.html#Renaming_a_User_Account

If you need anything else please let me know.

                                                                                           

Alexandre Jacquet Google Apps Deployment Specialst  São Paulo | SP | Brasil Tel.: 55 11 8064 6882

--
You received this message because you are subscribed to the Google Groups "Google Apps Domain Information and Management APIs" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-apps-mgmt-apis/-/BXlXIXNF9OEJ.
To post to this group, send email to google-app...@googlegroups.com.
To unsubscribe from this group, send email to google-apps-mgmt...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-apps-mgmt-apis?hl=en.

[Logi]

The point here is I have the client saying they are sending to rename. The management system they built does do a lot of them correctly.

However, they say they tell the management system they have its a rename.. and some how it ends up not renaming and a new account is added.

To me its a bit off as the two api calls go two different places and formatted differently.

So the question to others and Googlers is .. has this happened before or even possible as its two different api calls.

Possible as .. I call one API (rename) and the system does something totally different (new account).

-Logi

[Alexandre Jacquet]

Well, I have tested alot and I use alot for most of my deploys the rename user method, personally I have never seen this issue, and it makes no sense an API call for a HTTP request have two responses based on the same request, specially only for you customer.

However i think is better let Googlers answer this one :)

Best regards

                                                                                           

Alexandre Jacquet Google Apps Deployment Specialst  São Paulo | SP | Brasil Tel.: 55 11 8064 6882

--

You received this message because you are subscribed to the Google Groups "Google Apps Domain Information and Management APIs" group.

To view this discussion on the web visit https://groups.google.com/d/msg/google-apps-mgmt-apis/-/ChQyZCAWlZ8J.

[Claudio Cherubino]

Hi,

This is the first time I hear of rename calls leading to user creations and it is quite unlikely that this is a server-side bug. Given the amount of rename calls we receive each day I think we would get many more customers reporting the same issue.

Looking at the internal implementation, the two calls (POST and PUT) are handled separately and there's no way to create an user with a PUT call.

Anyway, if you can track down this issue to a specific user and timeframe we can go through our logs to understand what happened.

Thanks

Claudio

[Logi]

Claudio,

I sent some examples.

Thanks for the help ..

Whatever comes of this I will post back outcome for all ..