Autodiscover works, but getting a 403 (forbidden) error

I am testing my app (currently with the java api) against a user on a corporate account.

On office365 , everything worked fine.

The funny thing. The autodiscovery was successful, but when I tried to issue an EWS call, I got an exception with a 403 error.

With the combination of:

email address:  roger@acme.com

password: 123

url: https://lonneymail.acme.com/EWS/Exchange.asmx

domain : northamerica


How should I: 

1) construct the webcredentials (either .net or java apis)

2) if I am using straight soap/https requests, do I need to include the domain in the mix? how exactly ?

I tried to look at the usual examples with "contoso" but there is a great deal of intermixing between user/email/domain/server, etc.... so in the above acme example, it is clear where each part belongs. 

thanks,

  Erez 


  • Edited by Erez Katz Monday, May 04, 2015 8:22 PM
May 4th, 2015 8:21pm

The first thing I would do is use https://testconnectivity.microsoft.com/ and do some testing with this this will tell you if the EWS endpoint from autodiscover is usable. You can restrict EWS access https://msdn.microsoft.com/en-us/library/office/ff406134%28v=exchg.140%29.aspx but if you are getting a firewall response it maybe they have restricted it via IP (eg if they have other SAAS apps using EWS they may have just allowed the hosted IP range etc) I would talk to the local Network admin. (the other thing to try is if they OWA exposed externally just try the EWS endpoint on the OWA hostname they are both served of a CAS it maybe they have just misconfigured their EWS endpoint settings).

Cheers
Glen

Free Windows Admin Tool Kit Click here and download it now
May 6th, 2015 12:19am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics