Answers.Body: <p>we’re almost done moving over xero to oauth 2.0 and can share the code/instructions in the next few days if that works for you?</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-03-02T18:48:05.227Z
Answers.Text: absolutely. v happy to help with testing. i have 2 'test/demo' sites to set up so would be excellent timing to help.
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-12-14T14:41:22.710Z
Answers.Text: Parvez and you able to share the instructions here / on the documentation?
Answers.UserDisplayName: Heather O.
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-03-02T08:06:45.980Z
Answers.LastActivityDate: 2020-03-02T08:06:45.980Z
Answers.UserDisplayName: Parvez Saleh
Body: <p>Seeing some changes in the Xero process of creating a "new App" to use for synching with CiviCRM.</p>
  
  <p>Specifically it now requires an</p>
  
  <ul>
  <li>OAuth 2.0 redirect URI</li>
  </ul>
  
  <p>but also, unless my eyesight is failing, i no longer see where we are meant to upload the .cer we create on our hosting server.</p>
  
  <p>Thoughts?</p>
  
Tags: <civixero>
Title: Xero integration with OAuth 2.0 credentials
ThreadText: # Xero integration with OAuth 2.0 credentials
  
  (Asked by: username_0 on 2020-03-02)
  
  Seeing some changes in the Xero process of creating a "new App" to use for synching with CiviCRM.
  
  Specifically it now requires an
  
  * OAuth 2.0 redirect URI
  
  but also, unless my eyesight is failing, i no longer see where we are meant to upload the .cer we create on our hosting server.
  
  Thoughts?
  
  **Tags:** civixero
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2020-03-02. Score: 2
  
  we’re almost done moving over xero to oauth 2.0 and can share the code/instructions in the next few days if that works for you?
  
  > **Comments:**
  > **username_0**: absolutely. v happy to help with testing. i have 2 'test/demo' sites to set up so would be excellent timing to help.  
  > **username_2**: username_1 and you able to share the instructions here / on the documentation?  
  
  ---
  
  