Azure-docs: Does this work with new way Xero handles authentication (Oauth 2.0 vs 1.0)?

[otravers]

Just a couple of months ago I was able to authenticate my ADF connection against a Xero private app using your instructions, with the app set up with OAuth 1.0a.

Now Xero has a different model based on OAuth 2.0. When you create an app in the Xero developer website, you no longer see fields for Consumer Key and Consumer Secret, instead it's Client id and Client Secret. There is also no reference to public key certificates, unlike for apps set up with Oauth 1.0a.

I'm getting the following error in ADF trying to authenticate:
ERROR [HY000] [Microsoft][Xero] (1019) Unable to complete RSA Signature: error:0909006C:PEM routines:get_name:no start line ERROR [HY000] [Microsoft][Xero] (1019) Unable to complete RSA Signature: error:0909006C:PEM routines:get_name:no start line

Should anything be done differently under the Oauth 2.0 set up on the Xero side or ADF side?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 0f04a295-e4b9-a23b-02e7-232aab5db7ce
• Version Independent ID: cbcadc03-205b-c383-fd3d-7aa4d763f122
• Content: Copy data from Xero using Azure Data Factory - Azure Data Factory
• Content Source: articles/data-factory/connector-xero.md
• Service: data-factory
• GitHub Login: @linda33wj
• Microsoft Alias: jingwang

[ChiragMishra-MSFT]

@otravers Thanks for bringing this to our notice. We are investigating into the issue and will update you shortly.

[KranthiPakala-MSFT]

@otravers We have assigned the issue to the content author. They will evaluate and provide an update as appropriate.

@linda33wj Could you please have a look at the ask from @otravers ? - Thanks!

[wilsonjm-B]

I am waiting on this too. Can you please advise any updates?

[charlespickettau]

The authentication cycle for OAuth 2.0 is different to OAuth1. The connector in ADF will need updating. Is there a timeline on this MS?

[sam-loveridge]

Is this still outstanding? Keen to understand when this might be resolved. Any updates?

[charlespickettau]

+1 still an issue for us also

[linda33wj]

Thanks all for reporting the issue. We are now working on upgrading the connector to support OAuth 2.0. At the moment I don't have definitive release date to share yet, please stay tuned.

[PEGAH-SZ]

We are waiting for this for too long. Could you please update us if the connector will be upgraded anytime soon?

[wilsonjm-B]

Can we please have an update?

[calep]

FWIW we gave up waiting and wrote an Azure function to authenticate with Xero and pull data in.

[wilsonjm-B]

FWIW we gave up waiting and wrote an Azure function to authenticate with Xero and pull data in.

Thanks for the comment - that's what I was trying to avoid, but sounds like I'll need to spend some time working that one out. I can pull the data from Postman fine, but not get it into azure. Thanks.

[calep]

We tried to avoid it too and then gave up waiting as we had a deadline to hit!

In case it's helpful, we actually land the data direct from Node into blob storage as JSON and then ingest it from there. We also use elements of PowerApps to stitch together some of the process.

Perhaps you could trigger the Function to do the Xero download and dump the data into storage, and then have a Data Factory job that parses the JSON into whatever end state you need?

We land the data in blob, then ingest it using Azure SQL (mounting the json), and then parse it and load it into the final table using T-SQL (we had developers who were familiar with T-SQL and Azure SQL has good support for JSON now)

CP

[wilsonjm-B]

We tried to avoid it too and then gave up waiting as we had a deadline to hit!

In case it's helpful, we actually land the data direct from Node into blob storage as JSON and then ingest it from there. We also use elements of PowerApps to stitch together some of the process.

Perhaps you could trigger the Function to do the Xero download and dump the data into storage, and then have a Data Factory job that parses the JSON into whatever end state you need?

We land the data in blob, then ingest it using Azure SQL (mounting the json), and then parse it and load it into the final table using T-SQL (we had developers who were familiar with T-SQL and Azure SQL has good support for JSON now)

CP

Thanks - i appreciate the advice.

[linda33wj]

Thanks all for the feedback. The Xero connector has been upgraded to support OAuth 2.0. Refer to the doc on details: https://docs.microsoft.com/en-us/azure/data-factory/connector-xero

please-close