I'm using custom .wsdl files. When I switched from the salesforce sandbox to the production account, I had to change the .wsdl file accordingly. At this point the API logins stopped working, on the watchdog, the error INVALID_LOGIN: Invalid username or password or locked out. appeared.

It took me a while to figure out that the problem was that SoapClient caches wsdl files.

I will shortly come up with a patch to README explaining this problem.

CommentFileSizeAuthor
#1 475914-1_cached_wsdl.patch1.33 KBalex_b

Comments

alex_b’s picture

alex_b commented
Assigned: alex_b » Unassigned
Status: Active » Needs review
StatusFileSize
new 475914-1_cached_wsdl.patch1.33 KB

- add information on how to add your own .wsdl file
- add warning that SoapClient caches wsdl
- add a tip on how caching can be turned off / controlled

joshk’s picture

joshk commented

Sweet! I will add this now. Good documentation is a major thing here.

joshk’s picture

joshk commented
Status: Needs review » Fixed

committed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.