Salesforce Stack Exchange is a question and answer site for Salesforce administrators, implementation experts, developers and anybody in-between. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a number of hyperlinks for logging into various orgs that look like:

https://www.salesforce.com/login.jsp?pw={password}&un={username}

When I left work on Friday they were working fine. Today when I tried to use one I was redirected to https://login.salesforce.com rather than being logged in.

Why have these links stopped working?

share|improve this question
1  
Ah, I see now the www subdomain as opposed to the login subdomain. – bigassforce Mar 6 at 20:21

I think this is still supported if you drop the login.jsp and put the query string after the slash:

https://login.salesforce.com/?un=daniel@example.com&pw=hunter12

Note to other readers wrapping the login process in this way, be VERY particular to use HTTPS!

share|improve this answer
2  
Interesting, I didn't know the login.jsp part could be omitted. The note about https is definitely important. – Daniel Ballinger Mar 6 at 21:14

I believe this is related to Knowledge Article 000229717 - www.salesforce.com API Endpoint Retirement.

Essentially, you need to use https://login.salesforce.com for production and developer edition orgs.

https://login.salesforce.com/login.jsp?pw={password}&un={username}

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.