[SOLVED] Salesforce Zimlet Does Not Auth in ZCS 6.0.1 + Enterprise SF

[gb3]

I've tried to bring this back up an existing thread but it seems to have fallen into the cracks.

The zimlet appears, but we're not able to connect and it errors out with the following error:

 Login to Salesforce failed!
    INVALID_LOGIN: Invalid username, password, security token; or user locked out.
 
Check your internet connection and review your preferences. 
  

Logging into our salesforce account indicates that a connection was tried but failed with an Invalid Password:
(This password works just fine when logging into SF though)

 1/23/2008 8:28:24 AM PST    209.xxx.xxx.xxx     Other Apex API    Invalid Password 
  

For the password, we're using "normalpasswordSECURITYTOKEN"

Are there any other settings that I've overlooked? Any help would be greatly appreciated.

[JoshuaPrismon]

Can you open it up with firebug and watch the traffic across the wire? What password is it sending? Do you see any 404 errors (usually red)?

[gb3]

FireBug Results are the following when I try to login to SF using the SF zimlet?

 POST proxy?target=http://x.hostname.com/service/proxy?target=https%3A%2F%2Fwww.salesforce.com%2Fservices%2FSoap%2Fc%2F7.0
 
500 Internal Server Error [I]x.hostname.com[/I]       658 B 
  

The Response Headers look like this:

 Response Headers
Date    Thu, 15 Oct 2009 23:53:39 GMT, Thu, 15 Oct 2009 23:53:33 GMT
Content-Type    text/xml; charset=utf-8
Content-Length    658
Proxy-Connection    Keep-Alive
Request Headers
Host    x.hostname.com
User-Agent    Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.14) Gecko/2009082706 Firefox/3.0.14
Accept    text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language    en-us,en;q=0.5
Accept-Encoding    gzip,deflate
Accept-Charset    ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive    300
Connection    keep-alive
SOAPAction    m
Content-Type    text/xml; charset=UTF-8
Referer    http://x.hostname.com/zimbra/
Content-Length    411
Cookie    __utma=134422248.930212134022705700.1225312101.1255143659.1255457909.357; __utmz=134422248.1250174644.313.23.utmcsr=twitter.com|utmccn=(referral)|utmcmd=referral|utmcct=/hostname; __qca=1184376346-35954458-5364736; __utmc=134422248; ZM_AUTH_TOKEN=0_63cbf8315aaa5fa33c4e9353e06f1cbf18238505_69643d33363a62633363623439612d323961392d346463642d386435362d6466383266656334353236363b6578703d31333a313235353732373636353834323b747970653d363a7a696d6272613b; ZM_TEST=true
Pragma    no-cache
Cache-Control    no-cache 
  

The error would suggest a proxy issue however I am not using a proxy nor did I install the Zimbra proxy. Also note that on the Salesforce.com "Login History" log show my attempt to login.

Any ideas?

[JoshuaPrismon]

Zimlet's have to proxy most http requests because of the same site origination security policy that most browsers enforce.

[JoshuaPrismon]

This strongly suggests that either the authentication system changed, or the proxy is generating a error (unlikely, because it appears that a cookie from salesforce is getting through).

Check the outbound response. Does it have the correct username/password?

[gb3]

Actually, it seems that the last character is getting cut off from my password. I reentered the correct password and checked again and it seems to continue to remove the last character which is not a special character or anything similar to that.

Thoughts?

[JoshuaPrismon]

Try adding a additional character to the end of the correct password. If it still gets truncated, and suddeny works, file a bug

[gb3]

Ha! I thought the exact same thing but then I went and looked at the POST data in Firebut when updating my password (including the security token) and noticed that it cut off both ending characters. It seems there may be a DB field limit of 32 characters.

I just changed my SF password and re-sent new Auth Token and paired them together. It should be 34 characters but it cut it to 32 during the updating (POST) of my password into the zimlet.

Thoughts on a fix?

[gb3]

I have successfully changed my password and Auth Token to a total of 30 characters in order to test the connection between the SF Zimlet and SF. However my numerous attemtps has temporarily locked me out of my SF API account so I have to wait 30 minutes before testing again.

NOTE: This zimlet uses the SF API VER 7.0
Currnet API rolled out by SF is API VER 10.0

This may make not diffference at all, just an observation.

[gb3]

OK! It works as long as you use both your salesforce.com password + auth token.

if your password is pass123 and your auth token (secuirty token) is k7T422bzkJadd31z then you would enter "pass123k7T422bzkJadd31z" into the password field (nothing new here). The catch is the following;

The entire password cannot be more than 32 characters

This should most definitely be fixed in the Zimlet as this cut process is done when it POSTs your data into the Zimlet login credentials NOT when it is sent to Salesforce.com.

NOTE: This is not a good idea as your actual salesforce.com password is very weak as a direct result of this "hack".