[DUG] Xero private API (OAuth)

Tue Jul 8 12:56:50 NZST 2014

You can ignore the ProcessTags() calls - essentially they just do variable
substitution within the strings involved.

There is no login for private Xero apps, which are tied to a specific Xero
organisation.  You need to setup your application on the Xero API end for
that specific organisation, to generate the required key and secrets etc
which you use to do the signing of your requests.

w.r.t Unicode, the code was written for deployment with a pre-Unicode
Delphi compiler.  Some of the code was either written for or adapted from
libraries which were or had been ANSI-fied to ensure consistent behaviour
for use with Unicode versions of Delphi, but the remaining code otherwise
assumes ANSI strings.  If you are using a Unicode Delphi version you should
change *all *declarations to ANSIString to maintain the intended behaviour
and be careful of implicit string conversions when making calls into the
routines.

To make it properly Unicode enabled may involve more significant change
than that.

On 8 July 2014 11:43, Robert Martin <rob at chreos.co.nz> wrote:

>  Hi Cameron
>
> Sorry to bug you but....  I have the code installed and compiling however
> I am a bit unsure as to the process involved.
>
> For Public apps you go through a process of logging in and getting a
> token.
>
> For private applications do you just call the API you want and encode the
> call using 'OAuthSignRequest(fHTTP.Request, 'POST', lURL);' or do you need
> to do some sort of log in as well?
>
> In the OAuthSignRequest method there are calls to a function called
> ProcessTags( as below...
>
>    conkey    := ProcessTags(OAuthConsumerKey,    Locals, Partner);
>     consecret := ProcessTags(OAuthConsumerSecret, Locals, Partner);
>     tok       := ProcessTags(OAuthTokenKey,       Locals, Partner);
>     toksecret := ProcessTags(OAuthTokenSecret,    Locals, Partner);
>
> I guess this function would be in the classFloCommon.pas (not included)
> that we 'can easily replace'.  Unfortunately I have no idea what this
> function does or what its inputs are asside from it returning a string and
> that all the parameters are globals !  Any hints?
>
> Sorry to be a pain but this OAuth stuff is like pulling teeth.
>
>
> Cheers
> Rob
>
>
>
> On 8/07/2014 9:54 a.m., Cameron Hart wrote:
>
>  this code has been shared with Xero a while ago on their forum.  there’s
> a copy on ftp://ftp.flow.net.nz/RELEASE/Code/
>
>
>
>
>
> *Cameron Hart *
>
>  *Flow Software Limited *
>
>
>
>  [image: Flow]
>
>  PO Box 302 768, North Harbour
>
> *P *
>
> +64 9 476 3569
>
>  Auckland 0751, New Zealand
>
> *M *
>
> +64 21 222 3569
>
>  www.flowsoftware.co.nz
>
> *E *
>
> cameron.hart at flowsoftware.co.nz
>
>
>
> This message is intended for the addressee named above. It may contain
> privileged or confidential information. If you are not the intended
> recipient of this message you must not use, copy, distribute or disclose it
> to anyone.
>
>   P Please consider the environment before printing this email
>
>
>
>
>
> *From:* delphi-bounces at listserver.123.net.nz [
> mailto:delphi-bounces at listserver.123.net.nz
> <delphi-bounces at listserver.123.net.nz>] *On Behalf Of *Jolyon Smith
> *Sent:* Tuesday, 8 July 2014 9:14 a.m.
> *To:* NZ Borland Developers Group - Delphi List
> *Subject:* Re: [DUG] Xero private API (OAuth)
>
>
>
> This was a nut I had to crack at Flow.  I was successful in this endeavour
> but I'm not at liberty to share the fruits of those labors.  If you ask
> nicely however, Cameron might be willing to help.
>
>
>
> On 8 July 2014 08:52, Robert Martin <rob at chreos.co.nz> wrote:
>
> Hi
>
> I have been doing some work with the Xero API and have public OAuth
> working fine.  However I actually need to use the private API which
> requires RSA-SHA1  which I believe just means RSA signing.  Is that
> correct?
>
> If so does anyone have any code examples of RSA signing, I have found
> LockBox 3 which is supposed to do it but I just cant get it installed,
> although the source has a XE2 project group the code is full of errors !
>
> I am looking at using the openSLL dll calls to do it myself as an
> alternative but sample code is scarce. I will continue looking but if
> anyone has any pointers I would be grateful :)
>
> Cheers
> Rob
>
> _______________________________________________
> NZ Borland Developers Group - Delphi mailing list
> Post: delphi at listserver.123.net.nz
> Admin: http://delphi.org.nz/mailman/listinfo/delphi
> Unsubscribe: send an email to delphi-request at listserver.123.net.nz with
> Subject: unsubscribe
>
>
>
>
> _______________________________________________
> NZ Borland Developers Group - Delphi mailing list
> Post: delphi at listserver.123.net.nz
> Admin: http://delphi.org.nz/mailman/listinfo/delphi
> Unsubscribe: send an email to delphi-request at listserver.123.net.nz with Subject: unsubscribe
>
>
>
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2014.0.4716 / Virus Database: 3986/7813 - Release Date: 07/07/14
>
>
>
> _______________________________________________
> NZ Borland Developers Group - Delphi mailing list
> Post: delphi at listserver.123.net.nz
> Admin: http://delphi.org.nz/mailman/listinfo/delphi
> Unsubscribe: send an email to delphi-request at listserver.123.net.nz with
> Subject: unsubscribe
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://listserver.123.net.nz/pipermail/delphi/attachments/20140708/22ba075b/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 4211 bytes
Desc: not available
Url : http://listserver.123.net.nz/pipermail/delphi/attachments/20140708/22ba075b/attachment.jpe 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 648 bytes
Desc: not available
Url : http://listserver.123.net.nz/pipermail/delphi/attachments/20140708/22ba075b/attachment-0001.jpe 