Re: [WebDNA] Re: API Integration

This WebDNA talk-list message is from

2010

It keeps the original formatting. numero = 104326
interpreted = N
texte = --000e0cd1e2b459d441047ca3c30fContent-Type: text/plain; charset=UTF-8David,Looking at this page: http://code.google.com/apis/accounts/docs/AuthSub.htmlit would appear that you need WebDNA to generate three things for yourauthorization header:1. Unix timestampThere was a fair bit of discussion on the list about this recently, Briansubmitted a function library which will generate the timestamp for you2. Random 64bit NumberThis is a number with 20 digits, you should be able to cobble one togetherwith [cart] and countchars etc.3. SHA-1 encoded signatureThis may be a problem - Donovan showed how to generate an MD5 hash usingWebDNA [encrypt method=APOP] - but I haven't been able to successfullygenerate a SHA-1 hash using WebDNA and/or a shell script- Tom--000e0cd1e2b459d441047ca3c30fContent-Type: text/html; charset=UTF-8Content-Transfer-Encoding: quoted-printableDavid,=<=div>


- Tom



Looking at this page:

==C2=A0=C2=A0 =C2=A0http://code.google.com/apis/accounts/docs/AuthSub.html

it would appear that you need WebDNA to generate three things for your auth=orization header:

1. Unix timestamp=

There was a fair bit of discussion on the list about this recent=ly, Brian submitted a function library which will generate the timestamp fo=r you

2. Random 64bit Number

This is a number with =20 digits, you should be able to cobble one together with [cart] and countc=hars etc.

3. SHA-1 encoded signature

This may be a problem - Donovan showed how to generate an MD5 hash using We=bDNA =C2=A0[encrypt method=3DAPOP] =C2=A0- but I haven't been able to s=uccessfully generate a SHA-1 hash using WebDNA and/or a shell script

- Tom