BusProject / SalsaPress

SalsaPress connects WordPress to Salsa. Developed by the Bus Federation and Bus Project.
http://wordpress.org/extend/plugins/salsa-press/
8 stars 2 forks source link

Login issues #27

Closed bdub1976 closed 10 years ago

bdub1976 commented 10 years ago

I've installed the plugin but cannot seem to login. I've tried many login combinations without success. I've gotten the Jalepeno plugin working in WP, but no luck with SalsaPress. All but one of my attempts have given me the error Failed :-|

Below is the login page for my forward facing pages. I've tried any number of combinations of this link too without success. Am I missing something? I can login to this page (link below) no problem. But when I try to use the credentials to login to the page below within the plugin, and use afl.salsalabs.com as the salsa base url, it's "Invalid login, please try again". That's as close as I've gotten. Any suggestions would be greatly appreciated.

http://action.myaea.org/o/5908/profile/login.jsp?redirect=%2Fo%2F5908%2Fprofile%2Findex.jsp

mojowen commented 10 years ago

My guess is your API isn't turned on - contact salsa support

To confirm - log into your Salsa account and visit an API endpoint then visit any API page (like this one) https://wfc2.salsalabs.com/api/getObjects.sjs?json&object=supporter (assuming https://wfc2.salsalabs.com is your salsa root url).

If you see the following

[{"result":"error","messages":["Please upgrade to Salsa Enterprise to use
the Salsa API."]}]

you'll need to talk to Salsa about upgrading. Salsa is aware of this bug - that /api/authenticate.sjs returns success even if you can't access the api - but have not fixed it yet. You should tell them they should fix it.

bdub1976 commented 10 years ago

The first email from from salsa support was:

Thank you for your message. In order for this to work correctly, two things are required:
1. Your account needs the Enterprise package (which your account currently does)
2. The account manager login that you're using needs to have access to the Enterprise package. To set this up, change your role to 'no specific role':
http://screencast.com/t/Aq3tti4A
And then, you'd want to go to 'Account' and then 'Roles and Permissions' and change your default role to have access to the package:
http://screencast.com/t/fDy5hvFsJUMe

I took care of that and this is where we are:

Since you've done the configuration work that needs to be done, then the next step is to see the calls that you're making. Please reply at your convenience with the URLs (or code fragments) for both the authentication and the call that you are using that is getting the error.

I'm not sure what to tell them from here, do you have any recommendations?

bdub1976 commented 10 years ago

Ok, so I was able to log into Salsa, the backend, using my "campaign manager" credentials (system admin), then I browsed to https://hq.salsalabs.com/api/getObjects.sjs?json&object=supporter and I don't get an error, I get the supporter data, so the API is on.

Then I plugged https://hq.salsalabs.com/ as the SalsaPress base url, put in my FORWARD FACING login credentials, but I still get "Invalid login, please try again." If I put in my campaign manager creds I get Failed, so that can't be right.

mojowen commented 10 years ago

Hey bud, sorry for the slow reply.

Hmm that's very confusing. To confirm you:

And it still doesn't work? That is totally bizarre as SalsaPress is doing the exact same thing you're doing in your browser.

bdub1976 commented 10 years ago

No worries. I figured you were tied up.

Yep. I do exactly that and I get "FAIL! :|".

The only difference in error messages, I can put in SalsaPress the same site but forward facing salsa login credentials (what I would put in if I were just an activist) and I get "Invalid login, please try again".

I've got WP Jalepeno working fine. I've put in the same info for that plugin into this one too, but still fail. I'm really at a loss. I've updated WP to most recent version, updated all my plugins, changed passwords, uninstalled and reinstalled SalsaPress, and at this point don't know what else to try.

mojowen commented 10 years ago

Can you visit the following link:

http://hq-salsa.wiredforchange.com/api/authenticate.sjs?email=**your-email**&password=**your-password**

But substitute in your password / email - and paste-in what you seen?

bdub1976 commented 10 years ago

Using my admin username(email) and password (to access the dashboard and all that on the salsa back end) I get:

Unable to login. You must specify a login and password.

If I try my forward facing login info (to manage my subscriptions, see events and my action history etc.) I get:

Invalid login, please try again.

On Wed, Apr 2, 2014 at 8:04 PM, Scott Duncombe notifications@github.comwrote:

Can you visit the following link:

http://hq-salsa.wiredforchange.com/api/authenticate.sjs?email=**your-email**&password=**your-password**

But substitute in your password / email - and paste-in what you seen?

Reply to this email directly or view it on GitHubhttps://github.com/BusProject/SalsaPress/issues/27#issuecomment-39402546 .

mojowen commented 10 years ago

What if you substitute in your Salsa base URL in place of the hq-salsa.wiredforchange.com part?

If that's still returning an error (and you've replaced your-email with your email and your-password with your password) then Salsa doesn't appear to like your login. I have no idea how WP Jalapeno is working as it uses the same authentication method...

mojowen commented 10 years ago

What if you substitute in your Salsa base URL in place of the hq-salsa.wiredforchange.com part?

If that's still returning an error (and you've replaced your-email with your email and your-password with your password) then Salsa doesn't appear to like your login. I have no idea how WP Jalapeno is working as it uses the same authentication method...

bdub1976 commented 10 years ago

Son of a... The password was just too strong, or long one. I almost asked you about that the last time I posted. Anyway, I sincerely apologize for that taking so much of your time.

Thank you for your help!!

On Thu, Apr 3, 2014 at 4:35 PM, Scott Duncombe notifications@github.comwrote:

What if you substitute in your Salsa base URL in place of the hq-salsa.wiredforchange.com part?

If that's still returning an error (and you've replaced your-email with your email and your-password with your password) then Salsa doesn't

appear to like your login. I have no idea how WP Jalapeno is working as it uses the same authentication method...

Reply to this email directly or view it on GitHubhttps://github.com/BusProject/SalsaPress/issues/27#issuecomment-39507995 .

mojowen commented 10 years ago

So we're all good? Hot dog.

On Fri, Apr 4, 2014 at 10:49 AM, bdub1976 notifications@github.com wrote:

Son of a... The password was just too strong, or long one. I almost asked you about that the last time I posted. Anyway, I sincerely apologize for that taking so much of your time.

Thank you for your help!!

On Thu, Apr 3, 2014 at 4:35 PM, Scott Duncombe <notifications@github.com

wrote:

What if you substitute in your Salsa base URL in place of the hq-salsa.wiredforchange.com part?

If that's still returning an error (and you've replaced your-email with your email and your-password with your password) then Salsa doesn't

appear to like your login. I have no idea how WP Jalapeno is working as it uses the same authentication method...

Reply to this email directly or view it on GitHub< https://github.com/BusProject/SalsaPress/issues/27#issuecomment-39507995> .

Reply to this email directly or view it on GitHubhttps://github.com/BusProject/SalsaPress/issues/27#issuecomment-39592307 .

lcreative commented 9 years ago

I am also having issues on this end with authenticating domain is action.securefamily.org. I have verified the feed and also the username/password via api, but the plugin status keeps kicking up a fail. We are on enterprise with salsa.

mojowen commented 9 years ago

So https://action.securefamily.org/api/getObjects.sjs?json&object=supporter&limit=1&json returns a valid response?

mojowen commented 9 years ago

Also you should open a new issue