Don't know whether @Frog means the same, but in my setup (Vanilla 2.0.18b2, Proxyconnect 1.97, WordPress 3.1.3), I am unable to log out properly from Vanilla. Whenever I sign out by clicking vanilla's link, I remain signed in into wordpress, while i…
Latest version (1.92) dos not change anything to the better, appears to me as if cookies are not properly cleared or invalidated upon logout. I noticed that I can sign in again without providing any credentials after logging out.
Furthermore, the Wo…
Just updated my Vanilla test-installation to 2.017.9 and luckily I cannot confirm that ProxyConnect does not work at all. Seems to be no change from earlier version: SSO integration with WP 3.1 generally appears to be working quite well, except for …
Basically, Vanilla 2.0.17.8 and Proxyconnect 1.84 appear to be working with WordPress 3.1 in my setup. However, when trying to log out from Vanilla, I always encounter that WP nag-screen asking if I really want to log out. Seems to be some nonce-iss…
@Tim Regarding WordPress integration: Redirecting to the dashboard, which is usually at 'domain.com/wp-admin/', or the profile page at 'domain.com/wp-admin/profile.php' would both be perfectly fine, I guess.
@dan39 I guess sharing cookies across different domains is always problematic. Furthermore, AutoConfigure doesn't seem to work in a localhost environment, whereas it works fine when both WP and Vanilla are on the same domain (Vanilla in a subfolder).
@rio That really sounds weird, however I don't think that it relates to a major security issue in either Vanilla or ProxyConnect. If you can access your Admin-Dashboard, try disabling ProxyConnect, properly clear your cookies and then maybe start an…
@Raize In older versions of the plugin, the 'Apply for Membership' button redirected the user to the wordpress registration page, which only makes sense since there is a respective settings field. It seems as if in the current version this functiona…
The plugin definitely has no effect on the registration process, however I found out that manually setting a registration URL in config.php has the desired effect:
$Configuration['Garden']['Authenticator']['RegisterUrl'] = 'REGISTERURL';
Can someone please confirm if the integration of the registration process is working?
While the sign-in / out process appears to be working as intended, the registration from within Vanilla is not affected at all. Regardless of settings (manual / au…
The latest release of ProxyConnect (1.8) or at least the combination of vanilla 2.0.9 and ProxyConnect 1.8 in particular seems to be a tad flawed. You might also have a look at this discussion:
http://vanillaforums.org/discussion/12933/proxyconnect-…
Alright, decided to give manual integration a try, but it seems as if the settings are not saved. Whenever the page reloads or I click on activate, all the fields are blanked out.
Unfortunately things seem to get even worse:
After disabling an re-enabling the plugin, the error described before disappeared and the add-on would save authentication settings, however, the signin / signout URLs seem to be totally messed up.
My va…
On a brand new, clean installation of 2.0.7 and ProxyConnect 1.8, I get the following error message when I choose 'WordPress Integration' in the Authenticator panel:
Unable to create wordpress proxyconnect provider entry in GDN_UserAuthentication…