search

vivekiyer / corporateaddressbook

1 stars 1 forks source link

Can't connect to server: Error message 403 #84

Closed vivekiyer closed 10 years ago

vivekiyer commented 10 years ago

From mcee...@gmail.com on April 26, 2012 03:04:29

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: http://code.google.com/p/corporateaddressbook/issues/detail?id=84

vivekiyer commented 10 years ago

From sindyleu...@gmail.com on May 17, 2012 20:55:14

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

vivekiyer commented 10 years ago

From dan.matt...@gmail.com on September 21, 2012 18:49:22

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.

Owner: dan.matt...@gmail.com

vivekiyer commented 10 years ago

From viveki...@gmail.com on October 01, 2012 14:37:13

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.

vivekiyer commented 10 years ago

From stephane...@gmail.com on October 04, 2012 08:43:39

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

vivekiyer commented 10 years ago

From dan.matt...@gmail.com on October 04, 2012 08:51:28

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#ANDROID_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.

Status: Accepted

vivekiyer commented 10 years ago

From dan.matt...@gmail.com on October 25, 2012 05:26:26

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.

Status: Started
Labels: Version-2.0.4

vivekiyer commented 10 years ago

From dan.matt...@gmail.com on November 06, 2012 12:32:50

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.

Status: Fixed