The Javascript is only a part of the application, the application is
actually just a service that sends a message to users from an account.
the application is built in C++. and we pull our tokens from the
database. The javascript builds the request and then gets sent off
through C++. the web requests in general work. i have been able to
send SOAP requests, and i was able to send the requests for basic,
this is more of an upgrade job.
for instance the previous script for authorization was:
var sUser = "";
var sPassword = "";
var sLogin64 = "";
var sAuthHeader = "";
sUser = nvGet("username");
sPassword = nvGet("password");
goNVOut.Duplicate(goNVIn);
goNVIn.Destroy("username");
goNVIn.Destroy("password");
sUser += ":";
sUser += sPassword;
sLogin64 = Base64.encode(sUser);
sAuthHeader = "Basic " + sLogin64;
goNVOut.Set("Header.Authorization", sAuthHeader);
On Jun 4, 12:15 pm, Taylor Singletary <[email protected]>
wrote:
> Debugging OAuth in Javascript is a very painstaking process. What kind of
> application are you writing? How is Javascript used to perform the OAuth
> requests? Is the Javascript running in a protected environment where the
> consumer secret and access token secrets will not be human readable?
>
> Taylor Singletary
> Developer Advocate, Twitterhttp://twitter.com/episod
>
> On Fri, Jun 4, 2010 at 11:06 AM, Michael Cameron <[email protected]> wrote:
> > I have added the info to a Paste Site to make it look cleaner and help
> > things be easier, the bottom of the page has my results, and token
> > info
>
> >http://paste2.org/p/864634
