Please upgrade here. These earlier versions are no longer being updated and have security issues.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
Options
Basic Problems with Vanilla 2.0.11 and ProxyConnect 1.8.3
I basicly installed many times a new Vanilla 2.0.11 Version and ProxyConnect 1.8.3. I want to make it work with ModX CMS. So I also installed a basic ModX Version. The forum is installed on forum.domain.de and the CMS on www.domain.de.
I completly do what you write in all your documentation. I also think I understand everything. My CMS gives me a correct Authenticate URL if i am logged in:
If I am logged out, its correctly empty. Now I log in on www.domain.de and after this I load forum.domain.de, it is not logged in. if I click "Sign In" it correctly links to my cms login page.
It seems that Vanilla or the ProxyConnect still not get notice that I am logged in. Or maybe the path is not accessable or empty from forum.domain.de? Is there any debugging chance behind-the-scene? Do somebody else have that problem or can help me? Test installation would be accessable on demand. I really getting crazy about this.
I completly do what you write in all your documentation. I also think I understand everything. My CMS gives me a correct Authenticate URL if i am logged in:
UniqueID=1
Name=siteadmin
Email=you@example.comIf I am logged out, its correctly empty. Now I log in on www.domain.de and after this I load forum.domain.de, it is not logged in. if I click "Sign In" it correctly links to my cms login page.
It seems that Vanilla or the ProxyConnect still not get notice that I am logged in. Or maybe the path is not accessable or empty from forum.domain.de? Is there any debugging chance behind-the-scene? Do somebody else have that problem or can help me? Test installation would be accessable on demand. I really getting crazy about this.
Tagged:
21
Comments
Loading failed:: http://forum.domain.de/index.php?p=/entry/signin&Target=discussionsMaybe somebody understand this under the posted problem?
My developer knowledge is sparse at best, for what it's worth, so it could be something I'm doing wrong.
It seems that the proxyconnect has problems getting the data from the authentication url(it reads it well, it gets the username and all that) but somewhere beyond that it loses all data and does what he wants...
Did your also check the CURL extension on your webserver, this seems to be a requirement of Proxyconnect. You have to enable it. By default it is maybe disabled. Check it with phpinfo().
(cURL support enabled
cURL Information libcurl/7.19.2 OpenSSL/0.9.7e zlib/1.2.3 )
The code of the authenticacion url should be OK, I have tried lots of options and didn't worked any of them. Now I am trying with the same text(gotten from the sourcecode) of the example and still nothing.
Vanilla Forums COO [GitHub, Twitter, About.me]
http://vanillaforums.org/discussion/13491/proxyconnect-entries-in-gdn_authentication-gets-empty-foreignuser-column
could stand in relation with this thread. Is it so?
I'm using CodeIgniter PHP and figured out the required custom code/cookies to have a page called /vanillaProxyConnect that produces the correct plaintext variables (with the correct linebreaks).
Nothing seems to happen though.
Does anyone know how to solve this?
I've spent hours and hours and need to get this figured out right away.
Thanks!!
(The following is preliminary. It's now 12:40am....I'll check my work and do more on this in the am.)
I believe the problem is that the response from the SSO supplier (your website) is not being correctly parsed by the plugin.
The plugin is receiving
ueID=2
Name=Larry K
Email=larry.....
Instead of
UniqueID=2
Name=Larry K
Email=larry.....
from
function ProxyRequest in file vanilla/library/core/functions.general.php
I think the function is not parsing the html response from the server correctly. It's chopping off the first 4 characters.
The function has two modes: one where the php curl lib is installed, one where it is not. My guess is that the problem occurs in only one of the modes.
Stay tuned, more in the morning.
Larry
If it was something like
UniqueID=2
Name=Larry K
Email=larry.....
it would work fine.
Or any response where the first 4 characters were not needed.
Patch posted, see http://vanillaforums.org/discussion/13698/patch-for-proxyconnect-problems
Edit: sorry, I meant to post this in a different thread (http://vanillaforums.org/discussion/15492/)
One of the problems I faced initially was the use of cookies by vanilla whereas I was using session in my website. I realized that coookies were being created whether or not you are logged on whenever you go to the vanilla forums.
Here's a description of the error I encountered.
Scenario A
I am not logged in. I click on the vanilla forums as a public user, then clicked on sign in via sso, and headed back to the vanilla forums. I find myself not logged in to the forums.
Scenario B
I am not logged in. I click on the vanilla forums as a public user, cleared my cookies via "clear history" in FF, then clicked on sign in via sso, and headed back to the vanilla forums. I find myself logged in to the forums.
Scenario C
I am not logged in. I head straight to the sso page, and proceeded to the vanilla forums. I now find myself logged in to the forums correctly.
I am not entirely sure why it behaves this way as I have not dug deep enough to look at the core codes at the moment, what I did to fix this was to remove the cookie created whenever the user is signing in.