Windows Security

[James]

Hey all,

So for my latest project, I'm accessing the Twitter API (which has worked perfectly). Upon first install, the script asks for the username and password, then sends a check to the Twitter credential verification file. Which is fine, until a dialog box appears from "Windows Security" asks for the same information.

To the users who have been testing my script, they originally thought it was spyware of some sort, even though I've re-assured them, this is just Windows being safe. But... It then got a little worse. Not only did it ask for the same information once, sometimes it could be asking twice or three times.

The offending window looks like this:

I thank Windows for being this secure, but does it really need to do this and is there a way I can bypass this action?

For the record, I'm using the Microsoft.XMLHTTP object to send the data to Twitter.

Thanks,

James

I just had a thought I'm going to try elevating the users powers by running it as an admin. Perhaps this has a different effect.

Nope, that didn't work.

Edited January 23, 2010 by JamesBrooks

[James]

So Richard Robertson and I have discussed this and it seems logical that I need to write to the Credentials Manager. Taking a better look at the situation and it turns out not be as easy as first expected.

Credential Structure

CredWrite

Surely there must be a better way of going about this?

Edited January 24, 2010 by JamesBrooks

[seangriffin]

I would like your opinion James on the Twitter UDF I just published in the forums. Here's the link -> Twitter UDF. It includes OAuth authentication.

It sounds like you may have got a Microsoft.XMLHTTP object to work with the Twitter API. Was that with OAuth?? I tried for the best part of a day to get such an object to work with Twitter and OAuth but failed. Twitter always rejected my signature as invalid. I ended up going with a Javascript solution for my UDF that works.

Edited July 2, 2010 by seangriffin

[James]

seangriffin,

I've taken a quick look at it and was impressed. I never even thought about doing it the way you did.

It sounds like you may have got a Microsoft.XMLHTTP object to work with the Twitter API. Was that with OAuth?? I tried for the best part of a day to get such an object to work with Twitter and OAuth but failed. Twitter always rejected my signature as invalid. I ended up going with a Javascript solution for my UDF that works.

oAuth doesn't work via Microsoft.XMLHTTP - well that's a half lie, you still need to send the data some how. The problem I kept coming across when writing an actual UDF for Twitter oAuth was that it's basically impossible full stop.

So many things AutoIt can't do (without alot of digging anyway).

I ended up sending my web server parameters to send the data to Twitter using a PHP code.

James

[seangriffin]

oAuth doesn't work via Microsoft.XMLHTTP - well that's a half lie, you still need to send the data some how. The problem I kept coming across when writing an actual UDF for Twitter oAuth was that it's basically impossible full stop.

Yeah I feel your grief now, after spending many hours on the problem myself

Is it documented some where that OAuth doesn't work with Microsoft.XMLHTTP? Would put my mind at ease to see this is stated formally somewhere.

[James]

Is it documented some where that OAuth doesn't work with Microsoft.XMLHTTP? Would put my mind at ease to see this is stated formally somewhere.

Ignore what I said about that. That's the only way of sending data anywhere properly. And I completely forgot that I wrote a Javascript oAuth library which does the same thing - XMLHTTP.