13

I think the only way you can use your Session ID for frontdoor.jsp is if it was generated in the context of a first class Salesforce session: ie $Api.Session_ID on a Custom Link or Custom Button appearing on a native page layout on the *.salesforce.com domain or *.my.salesforce.com (per 'My Domain' feature), or Developer Console (tooling API), Eclipse ...


10

The authentication mechanism seems to have a replication delay. Changing your user name results in an email being sent to you: Dear Mr. User, Your username has changed. New username: ABC Old username: XYZ The new username may take several minutes to become fully functional. We recommend you log in with the following link for the ...


9

You need to be an ISV and login to the customers org using Subscriber support to see any logging from the managed package, including the stack trace. See comments on Capturing process information with Apex


9

Generally speaking, you can control the logging level using the TraceFlags. TraceFlags have overriding authority over all other tracing methods. See Summer '15 Release notes - Receive Debug Logs Predictably. As per Does the Summer ’15 release remove the ability to set test logging levels with the DebuggingHeader?, the current modifications seem a bit off ...


8

That's an explicit error returned from the server, so you request made it to a server and back. did you deploy the config file for your app (is this a desktop app or a web app?), as normally the .NET tools put the server url into the config file. Perhaps your request is going to sandbox when it should be going to production or visa versa. (typically this, or ...


7

If you're registered as an ISV, you can log a case in the Partner Portal. Otherwise, there's nothing that support is willing to do for you. You'll have to build a new Developer Edition org from scratch, or try to convince your previous manager or someone in authority to change your email for you. Depending on the company, this may either be trivial, ...


6

I suggest code like that below, where once the password verified login has succeeded you go on to check further factors (that you have added as fields to your login page): global with sharing class CustomLoginController { global String username{get;set;} global String password{get;set;} global String other1{get;set;} global String other2{...


5

It looks like other users have reported this on the Developer Boards, see: Invalid "icid" parameter in spring 13 sandbox login url syntax. It appears clearing your cookies will resolve the issue. "That will generally happen when you have corrupted cookies. Go to your browser's cookies and delete anything salesforce related. Then attempt to log in ...


5

This is actually a commonly known issue and the workarounds are listed here. Install security update patch for IE 8 for Windows XP will solve the problem. The patch was released back in 2011 and it is a security patch. OR Set browser to use Compatibility mode. OR Disable TLS1.1, 1.2 in browser


5

Debug statements shouldn't generally be used. Instead, in the console, go to the line of code where you want a snapshot, cluck the line number to create a checkpoint, then run the test. Afterwards, visit the checkpoint tab, and you can view the contents of memory when the checkpoint was reached. It will show you all the variables in memory during the unit ...


4

I have faced the same problem. Not sure why it's not working. But I was able to overcome that by creating a pageMessage in VF page as follows: <apex:pageMessage severity="error" summary="Login Failed.Check the userName or Password" rendered="{!isLoginFailed}"/> <apex:commandbutton value="Login" action="{!login}"/> In Controller: public ...


4

When you first click the User lookup field it only shows recently viewed Users, you need to search for a User, in your case searching for 'Riaz' should show your account.


4

This is a known issue still unfixed but in review and we are not alone (it affects at least 59 others). If you haven't already you should state there that it affects you, too. https://success.salesforce.com/issues_view?id=a1p30000000T4hLAAS Summary After a sandbox has been activated, it may take up to 5 hours for login attempts via the test....


4

Is your email going through a virus scanner that checks links within emails for malware etc. ? The password reset link you are being sent expires as soon as the link is visited. Having an admin send you a password reset link will most likely work as it uses a different format for the token and the link does not expire until the password is actually reset ...


4

There was an email sent by Salesforce on March 1 with the title "Identity Confirmation Change with Spring ‘16 Release". This goes over some changes, including a statement saying you'll expect more verification pages now. The core message in that email was (emphasis mine): At Salesforce, we understand that the confidentiality, integrity and ...


4

There is no trust site that I can find for workbench, but poking around the workbench menus turned up a help page that gives you a "report issue" link that takes you to a github issues page. There is a specific issue for this occurance, https://github.com/forceworkbench/forceworkbench/issues/820 so I'd say that it's not just you. The "answer" part of this ...


4

Expanding on Derek F's answer: Since Derek posted the link, a user has posted a solution on that page: Login into the org. Open up the Setup menu and navigate to Apps > Connected Apps > Connected Apps OAuth Usage. Look for Workbench in the list. Click on the number in the User Count column, which will open a new page. On that page, look for the "Revoke ...


3

From the end of the article you link to: Also, note that, currently, only tokens issued by OAuth can be revoked in this way; an attempt to revoke a session ID issued by SOAP login() or as a sid cookie will fail. A future release will allow all tokens to be revoked via the OAuth 2.0 endpoint, regardless of their issuing mechanism. So you can't currently ...


3

I'm going to take a wild guess that maybe you solved your own problem, and posted it on your own website? :) Either that, or another guy name Buyan found the answer. For anybody who stumbles on this, you'll probably find this helpful: http://betterapexprogramming.com/creating-a-custom-change-password-page-using-force-com-sites-and-solving-issues-with-...


3

Could you try using the problem credentials from another tool on the server that is throwing the error? You could use: The Data Loader Force.com Explorer Apex Explorer. While it has been replaced by the Force.com Explorer it was a .NET application. It could be hard to download now and the link appears to redirect to the newer tool. FuseIT SFDC Explorer - ...


2

Does the server's firewall allow your app? Assuming you are connecting to the correct instance, with proper credentials, it sounds like the traffic isn't making it to Salesforce. Have you tried watching the traffic with Wireshark or another similar tool?


2

While we thought this was a dev org it was actually a Partner Portal org which expires after 1 year. We filed a case on the partner portal and a representative there extended the org for another year. We're still trying to find a more permanent solution so we don't have this issue again next year.


2

Are you setting the client_id and secret ? Those are the parameters you should send: client_id=XXXXXX &client_secret=XXXX &password=passTOKEN &username=XXX &grant_type=password Ensure you are setting the header Content-Type: application/x-www-form-urlencoded. BTW, user-password flow doesn't support refresh_token flow. More info see this ...


2

Salesforce support are the only people that can help you. Usually they make you jump through some hoops for "security reasons" but this isn't uniformly enforced. Some will even tell you they can't do anything for you, so it takes some effort. The moral of the story is to never mess with a feature that can irrevocably lock you out unless you're willing to ...


2

And the answer was!! Internet Explore security settings. Turns out the particular user had some fairly restrictive security settings for untrusted sites. They had whitelisted *.salesforce.com but not *.force.com. Add *.force.com to their list of trusted sites fixed the issue.


2

OK, thanks to @ThomasTaylor, I found out that the answer turned out to be Connected Apps settings under Setup/Administration Setup/Manage Apps/Connected Apps. I'd never been to this page to my knowledge and I'm the only one who uses this SFDC account, so I'm not sure if this was a default setting or if was changed somehow. The Permitted Users for ...


2

This is definitely something wrong with your username and password.Please note you need security token appended to password like password+token to access salesforce unless your IP address is in network access .


2

I haven't tested this form of authentication yet, but from what I have read, I believe there should be a 'Can’t scan the QR code' link that will show a key that needs to be manually typed in, for the cases where you are on a device that cant scan the code. You can read more about it in the Winter 14 release notes http://docs.releasenotes.salesforce.com/...


2

This is usually a connection or computer/device problem. Try the following: Try getting to other websites to make sure that it's isolated to just salesforce.com. If you're having general intermittent problems, it's either your connection or your device. Try pinging the salesforce.com servers. See the online help for your operating system on how to ping. ...


2

If you use the the 6.0 connector, the problem is your studio + ESB version. I was having the same with the Studio of October and ESB v.3.5.2. Solution: - Studio 5.0.1 - ESB 3.6 EE


Only top voted, non community-wiki answers of a minimum length are eligible