Can't connect to server: Error message 403

[GoogleCodeExporter]

Hello

I try to connect to my companies sync server but it does not connect and gives 
me the above error message.
I use Samsung Galaxy S2.
Can anyone help me here?

Thank you very much.
Marc

Original issue reported on code.google.com by mcee...@gmail.com on 26 Apr 2012 at 10:04

[GoogleCodeExporter]

Hi,
I also try but show error message 403.  I am using HTC Wildfire.  Anycone can 
help? Thanks. 
SY

Original comment by sindyleu...@gmail.com on 18 May 2012 at 3:55

[GoogleCodeExporter]

Error 403 means "forbidden" which typically means that you are authorized but 
not allowed to acces the service. This error might depend on a number of 
server-dependant factors that we just can't figure out without having access to 
the server ourselves.

We might include some kind of error logging in the future which could allow you 
to submit errors like these but that's not available at the moment.

Original comment by dan.matt...@gmail.com on 22 Sep 2012 at 1:49

[GoogleCodeExporter]

Can you please try the latest version of the app? Certain keyboards (SwiftKey 
for instance) adds spaces to the end of words, which causes authentication 
errors. This has been fixed in the latest version of the app. Please download, 
install and try it and let us know how it goes.

Original comment by viveki...@gmail.com on 1 Oct 2012 at 9:37

[GoogleCodeExporter]

Same problem here. I cannot connect to my company Exchange server. I get a 403 
error.
Before authorising access to our Exchange server, company is asking to 
registered the phone IMEI inside an internal database.

I don't know exactly how Exchange authentication is working but I'm pretty sure 
that it is able to include phone IMEI inside the auth request. I think that it 
is missing in your application.

We are using the stock email application just pushing some admin of the 
terminal to force a pin code so it must be a standard behavior.

Stephane

Original comment by stephane...@gmail.com on 4 Oct 2012 at 3:43

[GoogleCodeExporter]

I see. The way that this is implemented today is that the ID is made up. At 
http://developer.android.com/reference/android/provider/Settings.Secure.html#AND
ROID_ID there's a description of the Android device ID that could be used 
instead. That is cerated at first boot and then (supposedly) not changed during 
the lifetime of that install. It would be re-randomized which is acceptable.

Original comment by dan.matt...@gmail.com on 4 Oct 2012 at 3:51

• Changed state: Accepted

[GoogleCodeExporter]

Thanks, all!

We've now looked into the case and the case you're describing is not completely 
uncommon. However, using the IMEI poses two problems:
1) Reading it requires READ_PHONE_STATE permission which some users get annoyed 
by
2) Not all devices have a radio, hence no IMEI.

We have now implemented the changed described in the comment from Oct 4th so 
the DeviceId should now be a unique and permanent way of identifying your 
device, much like the IMEI. We will also implement a user message that displys 
this DeviceId in case of error 403 to guide towards a solution.

Original comment by dan.matt...@gmail.com on 25 Oct 2012 at 12:26

• Changed state: Started
• Added labels: Version-2.0.4

[GoogleCodeExporter]

Version 2.0.4 and later includes functionality that presents the Device ID to 
the user in case of Error 403. This can be copied to the clipboard and sent to 
a systems administrator for updating the Exchange configuration. Please report 
back whether this actually solves the issue.

Original comment by dan.matt...@gmail.com on 6 Nov 2012 at 8:32

• Changed state: Fixed