SSO with jsconnect 1.4.1 and Vanilla Forum 2.1.3 - "Whoops provider not found"

luigi

I've been using Vanilla Forum 2.0.18 with jsconnect previous version succesfully so far.

After the succesful SSO login I used to redirect my embedded forum page to

$landing_vanilla='/vanilla/entry/jsconnect?client_id=123456789&Target=%2F';
header("Location:$landing_vanilla");

This worked well until upgrade to 2.1.3

Now I get "Whoops provider not found" BUT I'm properly logged in on my site and on embedded Vanilla Forum as it is shown if I go to forum discussions page.

It seems that jsconnect cannot found the appropriate link

Now I changed the link to my php embedded page:
$landing_vanilla='forum.php';

This does not rise error BUT I have to click on

"Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
your_username
Sign In with your_website"

Then, even without entering the password I'm properly logged in....

In add, if I copy and paste the link I see on the above signin message on the browser, it AGAIN give the whoops error... so I think the magic is made by Javascript

What am I doing wrong?

Thanks a lot!

Luigi

luigi

Here the debug output

/web/htdocs/www.my_site.com/home/vanilla/plugins/jsconnect/class.jsconnect.plugin.php(345): NotFoundException('Provider')
[internal function]: JsConnectPlugin->EntryController_JsConnect_Create(Object(EntryController), '', '')
/web/htdocs/www.my_site.com/home/vanilla/library/core/class.dispatcher.php(337): call_user_func_array(Array, Array)
/web/htdocs/www.my_site.com/home/vanilla/index.php(46): Gdn_Dispatcher->Dispatch()
{main}

Luigi

Bleistivt

You seem to be using an older version of jsconnect.
Try this one:
https://github.com/vanilla/addons/tree/master/plugins/jsconnect

luigi

Ok, thanks.
Updated to 1.4.3

What is weird now is that with Opera it works correctly (only signout is not in sync, but not a big issue for me, at least for now).

With Firefox and Chrome and Safari I get the same error of missing provider if I direct my browser to:
http://www.my_site.com/vanilla/entry/jsconnect?client_id=1741364457&Target=/

Strange that only on Opera it works properly... anything to do with Javascript part?

luigi

Additionally:
1)
not sure if related by I get error in embed.js at line 280

if (container) {
var loaded = function() {
container.removeChild(img);
Uncaught Error: NotFoundError: DOM Exception 8 (repeated 2 times)
}

2)
Plus I get in the console this error:

failed to load resource: the server responded with a status of 400 (Bad Request)

related to link

http://www.my_site.com/vanilla/index.php?p=/entry/jsconnect&remote=http %3A %2F %2F www.my_site.com %2F forum.php&locale=

Bleistivt

Could you check your Browser console (F12) for js errors when trying to log in and post them here?

Also make sure the authentification provider delivers the data as "application/javascript"

luigi

Error I get is

Data e ora: 05/10/2014 21:25:05
Errore: NotFoundError: Node was not found
File sorgente: http://www.my_site.com/vanilla/js/embed.js
Riga: 280

luigi

and...

Data e ora: 05/10/2014 21:27:00
Errore: fbcdn-profile-a.akamaihd.net : server does not support RFC 5746, see CVE-2009-3555

and

my auth.php file output is:
test({"email":"luigi@my_site.com","name":"luigi","photourl":"","uniqueid":"555","client_id":"1234567890","signature":"abcdefgh123456789"})

is this file which should deliver the data as "application/javascript"?

If yes, how can I do that?

Thanks

Bleistivt

Unfortunately, I am not familiar with the first error, also it seems to be in parts in a language I don't understand.

To your second question: yes, you can do it with

header('Content-type: application/javascript');

luigi

Ok sorry: here in English

1. error message is in embed.js
   Date and time: 05/10/2014 21:25:05 Error: NotFoundError: Node was not found
   Source File: http://www.my_site.com/vanilla/js/embed.js
   Row: 280

and

2. is
   Date and time: 05/10/2014 21:27:00 Error: fbcdn-profile-a.akamaihd.net : server does not support RFC 5746, see CVE-2009-3555

I added the header on top of the auth.php file but still no luck...

vrijvlinder

This is something your host needs to look into

http://blogs.technet.com/b/srd/archive/2010/08/10/ms10-049-an-inside-look-at-cve-2009-3555-the-tls-renegotiation-vulnerability.aspx

https://wiki.mozilla.org/Security:Renegotiation

peregrine

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-3555

peregrine

no idea - but perhaps the master embed.js may work better, but it might cause different problems.

you would need to try at your own risk

https://github.com/vanilla/vanilla/commits/master/js/embed.js

luigi

@vrijvlinder said:
This is something your host needs to look into

http://blogs.technet.com/b/srd/archive/2010/08/10/ms10-049-an-inside-look-at-cve-2009-3555-the-tls-renegotiation-vulnerability.aspx

https://wiki.mozilla.org/Security:Renegotiation

It looks an old thing right? Everything worked fine here until the upgrade to Vanilla 2.1 so
I tend then to exclude that problem...

@peregrin said:
no idea - but perhaps the master embed.js may work better, but it might cause different
problems.

I can give it a try. In effect it looks like the missing node eventual case has been covered there:

if (container) {
var loaded = function() {
if (img) {
container.removeChild(img);
img = null;
}

peregrine

@luigi said:

@peregrin said: no idea - but perhaps the master embed.js may work better, but it might cause different problems.

I can give it a try. In effect it looks like the missing node eventual case has been covered there:

I'm feeling lucky today, how about you

7's are in the air.

luigi

So, so,
Bad news is that the error persist...

Good news is that my backup was working fine and I could go back to version 2.0 without too much pain...
:#

It's a shame as the 2.1 version solved several issues and it's looking very nice...

vrijvlinder

You should create a second test forum in a subdirectory and try to figure it out. Then once all is working you can switch.

luigi

@vrijvlinder said:
You should create a second test forum in a subdirectory and try to figure it out. Then once all is working you can switch.

Right, thanks. I will give it a try asap. I'm just curious to know if anyone could migrate successfully the single sign on (SSO) from 2.0.18 to 2.1.3 ...