Hello Shawn, Just to make sure that I understand, the UPDATE request was sent to a URL that looks like: https://www.google.com/m8/feeds/profiles/domain/<your_domain>/full/<alias>
Instead of https://www.google.com/m8/feeds/profiles/domain/ <your_domain>/full/<userName> If this is the case, please feel free to file an issue against the Google Apps APIs issue tracker so that it will be easier for other developers to track the status of it. Best, Alain On Tue, Sep 13, 2011 at 4:36 PM, Shawn Drape <[email protected]> wrote: > Hi, > > I recently encountered a change in our domain that was triggered where we > didn't expect it to be. A call had been made to update a profile using a > userName that wasn't the primary address of an account (we expected the > account to have been created, but it wasn't because the e-mail address in > question was being used as an alias). I would have expected it to fail, > since it was not the userName, but it passed and updated the information of > the wrong user. > > Is this a bug, or has it always been the case that you can use alias > addresses in the place of the primary e-mail address (a.k.a. userName) for > these API calls? > > Thanks in advance for your response. > > Shawn > > -- > You received this message because you are subscribed to the Google > Groups "Google Contacts, Shared Contacts and User Profiles APIs" group. > 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://code.google.com/apis/contacts/community/forum.html > -- Alain Vongsouvanh | Developer Programs Engineer -- You received this message because you are subscribed to the Google Groups "Google Contacts, Shared Contacts and User Profiles APIs" group. 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://code.google.com/apis/contacts/community/forum.html
