Open Moko and Linux Based Phones

[jjzhuang]

The error quoted means the user account doesn't exist. There's not much else to it. Please check with your system admin to make sure you are pointing to the right server. Thanks!

[keithop]

Originally Posted by jjzhuang

The error quoted means the user account doesn't exist. There's not much else to it. Please check with your system admin to make sure you are pointing to the right server. Thanks!

I really don't think it's that simple :/

With the "correct" user setup on the A1200 phone which seems like it SHOULD work, pointing to the correct server on which the user has an account, the phone seems to give the credentials to the zimbra server in slightly the wrong format. Enough to throw off authentication and ok yep, return that error.

I do think it's a phone problem not a zimbra problem, but still I think it's worthy of looking into by the mobile team just to see if it's possible to allow for that form of authentication handshake

Keith

[jjzhuang]

OK I took a closer look at the error message, and it does appear the phone is encoding the user wrong. Mobilesync picks up user credential from HTTP basic auth. In the HTTP request the client is supposed to send a header like this:

Authorization: Basic <credential>

where <credential> is base64 encoded user auth data. The auth data can be any of the following:

userass
user@domainass
domain\userass
domain\user@domainass

It looks like when the phone encodes the auth data, it mistakenly used a forward slash '/' instead of '\' to separate domain from user.

If the phone allows omitting domain, you can try to leave the domain empty and make username in the form of user@domain. Hope this will workaround the phone problem. If not, you'll need a fix in the phone software.

[pyite]

Thank you for the reply!

It is unfortunately not possible to omit the domain, from what I can tell. I will try to contact Motorola to see if they will respond.

However, Motorola is huge and it may be easier to get the code changed in Zimbra - if it is just a slash character, how hard would it be to make this change? I wonder if it is possible to hack up an HTTP proxy to do a workaround.

Thanks,
Mark

[cesarcardoso]

Originally Posted by jjzhuang

It looks like when the phone encodes the auth data, it mistakenly used a forward slash '/' instead of '\' to separate domain from user.

So Microsoft Exchange accepts '/' and '\' to separate domain from user? A1200 works flawlessly with it...

[pyite]

Well I hacked up a quick HTTP::Proxy script and substituted \ for / and it gets a bit further -

DeviceId=MOTOEZX0e08faf18bd52b5f87af67654;DeviceTy pe=MotEzx;SyncCmd=FolderSync;] sync - HTTP/1.1 200 OK

However, the proxy is going very slow, I will need to do some more testing. It doesn't get as far as actually exchanging any data.

If Exchange accepts either \ or / then I really think this should be fixed by the Zimbra Mobile folks - is there anything I can do to help? It seems like it wouldn't be a huge job for the right person.

Thanks,
Mark

[jholder]

File a bug

[pyite]

Still no word back from anyone at Zimbra on making the Motorola phones work... I guess this is typical with non-open-source products. @#%^

[jholder]

I don't see a bug.

If you're the one having the problem, then you should file the bug. I don't have the logs or the phone.

We're more than eager to help, but if you want action, please see my post above:

File a bug

[pyite]

ok, the bug is 21118.

Thanks,
Mark