Identi.ca autentication error

[GoogleCodeExporter]

firestatus 1.10 (firestatus-20101124.xpi)

I have installed firestatus just now and I've tried to send one message to 
identi.ca but:
Failed to update identi.ca. Response was 401: {"error":"No ha sido posible 
autenticarte.","request":"\/api\/statuses\/update.json"}

Original issue reported on code.google.com by si...@simonbcn.net on 11 Feb 2011 at 5:25

[GoogleCodeExporter]

It seems that identi.ca does not ask for a password when one is not retrieved 
from firefox password manager.

Original comment by chstath on 12 Feb 2011 at 3:55

• Changed state: Accepted

[GoogleCodeExporter]

I don't use firefox password manager. I use LastPass.
I don't understand why don't you use the OAuth_authentication with identi.ca 
(http://status.net/wiki/Twitter-compatible_API#OAuth_authentication).

Original comment by si...@simonbcn.net on 12 Feb 2011 at 8:19

[GoogleCodeExporter]

Thanks for the link. The oauth authentication for identi.ca is almost ready. If 
you like, I could sent you a build to test it as soon as it is ready.

Original comment by chstath on 22 Feb 2011 at 1:36

• Changed state: Started

[GoogleCodeExporter]

Thanks.
Ok, could you publish the link here?
Should I delete the actual config? How?

Original comment by si...@simonbcn.net on 22 Feb 2011 at 1:41

[GoogleCodeExporter]

I will upload the build in the downloads section but I can also publish it 
here. You don't have to change anything, just install the xpi. I think that 
later today it will be ready.

Original comment by chstath on 22 Feb 2011 at 2:31

[GoogleCodeExporter]

ok, thanks. I'll wait for it.

Original comment by si...@simonbcn.net on 22 Feb 2011 at 3:02

[GoogleCodeExporter]

So, this is it. http://firestatus.googlecode.com/files/firestatus-20110222.xpi

Two things:
a) Ignore the username field in identica tab in preferences. We don't
need it and I just forgot to remove it.
b) I used the "out of band" oauth for desktop clients. That means that
identica (just like twitter) will present a PIN that the user has to
copy and paste
into the prompt displayed by firestatus. I will try to avoid this step
(it can be avoided I think) but for now it is like that.

Tell me if you encounter any problems.
Thanks

Original comment by chstath on 22 Feb 2011 at 8:55

[GoogleCodeExporter]

Thanks, but this isn't working:
I have sent an update to identi.ca, one javascript error:
"An error occurred during a connection to d30v64o1sch0yw.cloudfront.net:443.
Unable to communicate securely with peer: no common encryption algorithms.
(Error code: ssl_error_no_cypher_overlap)"

It shows me several times this error and then it shows me the window to 
authorize firestatus in identi.ca.
I authorize it and I write the PIN in firestatus window.
It shows me several times this error again and firestatus send the update.
The next updates work well, but I close the browser, when I open again and I 
try to send an update to identi.ca, it starts of "out of band" oauth with that 
javascript error.

Original comment by si...@simonbcn.net on 22 Feb 2011 at 11:52

[GoogleCodeExporter]

You are right that after closing and re-opening firefox, the authentication 
process starts over. I probably have forgotten to save the auth token.

About the javascript error: Are you sure that this error is related to 
firestatus? Firestatus does not attempt any connection to cloudfront.net (I 
actually have no idea what it is). Maybe identi.ca is hosted on cloudfront. 
Anyway I will make another build to fix the other problem and see what happens. 
Thanks again for your help in testing.

Original comment by chstath on 23 Feb 2011 at 8:26

[GoogleCodeExporter]

http://firestatus.googlecode.com/files/firestatus-20110223.xpi

Try this one. Now it won't ask again for authentication.

Original comment by chstath on 23 Feb 2011 at 8:36

[GoogleCodeExporter]

Thanks, it works now but the javascript error, in the oath process, is very 
annoying and it stills occurs.

Original comment by si...@simonbcn.net on 23 Feb 2011 at 12:43

[GoogleCodeExporter]

Ok. Could you send me a screenshot of the javascript error? It is very strange 
cause as I said before firestatus has nothing to do with cloudfront.

Original comment by chstath on 23 Feb 2011 at 12:49

[GoogleCodeExporter]

It's solved. It wasn't problem of firestatus, it was problem the ssl config in 
my firefox. ;-)
Thanks.

Original comment by si...@simonbcn.net on 23 Feb 2011 at 1:08

[GoogleCodeExporter]

Solved as of changeset bb89ab7877f1 (nightly build 2011-02-23)

Original comment by chstath on 23 Feb 2011 at 1:32

• Changed state: Fixed