Re: EWS API changes
jonathan sanders
Hi Jonathan,
I get the same error with and without logging in.
Can you also please tell me about how access token is obtained in the example code for an account which is passed to the method or stored in file? Is it using MSAL? Doesn’t the token have any expiry date?
Thanks,
Varsha
From: jonathan sanders <jonathan...@netcompss.com>
Sent: Tuesday, May 19, 2020 1:39 PM
To: Holla, Manoor Varsha <manoorvar...@cgi.com>
Cc: Garnaas, Jan <jan.g...@cgi.com>; Mehra, Shailja <shailj...@cgi.com>
Subject: Re: EWS API changes
You should be able to register.
Please let me know if you have any problems.
On Tue, May 19, 2020, 9:56 AM Holla, Manoor Varsha <manoorvar...@cgi.com> wrote:
That’s great. I will now add it.
I see that there is a google group for JEC.
Please provide access to this group to shailj...@gmail.com and in...@mvarsha.com, so that we are in the loop.
Thanks,
Varsha
From: jonathan sanders <jonathan...@netcompss.com>
Sent: Tuesday, May 19, 2020 12:02 PM
To: Holla, Manoor Varsha <manoorvar...@cgi.com>
Subject: Re: EWS API changes
Hi,
We added support for OAuth.
Please check the latest version.
On Tue, May 19, 2020, 8:34 AM Holla, Manoor Varsha <manoorvar...@cgi.com> wrote:
Hi Jonathan,
I am testing EWS API changes using an Office 365 account. I disabled basic authentication for Exchange and set setUseNTLMAuthentication true. Authentication fails and PFA logs.
1. I was not able to find a way to enable NTLM for Office 365 account and I read that it is not possible. Can you tell me if there is a way?
2. Can you please let me know how can I enable digest auth in office 365?
Any doc you can share for these would help me.
Thanks,
Varsha
From: jonathan sanders <jonathan...@netcompss.com>
Sent: Monday, January 13, 2020 1:53 PM
To: Holla, Manoor Varsha <manoorvar...@cgi.com>
Subject: Re: EWS API changes
Hi Varsha,
The Authentication methods available from EWSJ side are (order of strength):
NTLM, Digest, Simple.
They are available for Office 365, and local Exchange users.
Authentication methods can be disabled/enabled from Exchange side, and we respond to it accordingly.
On Mon, Jan 13, 2020 at 9:39 AM Holla, Manoor Varsha <manoorvar...@cgi.com> wrote:
Thanks Jonathan for the answers.
May I know what authentication methods are available from EWSJ for customers using Office 365 or exchange online?
Thanks,
Varsha
From: jonathan sanders <jonathan...@netcompss.com>
Sent: Monday, January 6, 2020 3:27 PM
To: Holla, Manoor Varsha <manoorvar...@cgi.com>
Cc: sup...@netcompss.com; Garnaas, Jan <jan.g...@cgi.com>; Mehra, Shailja <shailj...@cgi.com>
Subject: Re: EWS API changes
Hi,
Please see my comments below.
On Mon, Jan 6, 2020, 10:36 AM Holla, Manoor Varsha <manoorvar...@cgi.com> wrote:
Thanks Jonathan for your quick response and happy new year!
Please help us further by providing inputs to the below questions.
1. By digest authentication, do you mean SMTP? I couldn’t find this in their docs.
2. How is digest authentication supported by EWSJ?
It's automatically supported if it's available on your server, and higher authentication services are not available, or disabled using the enableNTLM false configuration.
3. We are only accessing EWS services through EWSJ from our application and an option to use NTLM is already added. If customers are running their own exchange server
a. They can still decide not to switch off basic authentication – Is this correct?
Yes.
b. What else should/can we do from the application standpoint apart from providing NTLM option to make services seamless to our customers who switch off basic auth?
It's enabled by default (you can disable it by using enableNTLM false.
4. Those customers who are using Exchange online / Office 365
a. NTLM authentication is only available for on-premises servers. So, NTLM option here has no use – Is this correct?
b. What should we do from the application standpoint to our customers who switch off basic auth?
Thanks,
Varsha
From: jonathan sanders <jonathan...@netcompss.com>
Sent: Tuesday, December 24, 2019 7:49 PM
To: Holla, Manoor Varsha <manoorvar...@cgi.com>
Cc: sup...@netcompss.com; Garnaas, Jan <jan.g...@cgi.com>; Mehra, Shailja <shailj...@cgi.com>
Subject: Re: EWS API changes
Hi,
Please see my answers below.
On Tue, Dec 24, 2019, 8:26 AM Holla, Manoor Varsha <manoorvar...@cgi.com> wrote:
Hi Jonathan,
According to this blog post, basic authentication will be decommissioned on 13-Oct-2020. Our customers are using basic authentication scheme to connect to outlook. Our application only uses email and appointment related APIs from JEC EWSJ SDK.
Please take some time to help me with below queries
1. EWS will no longer receive any feature updates. Will JEC EWSJ library still be maintained and provide security updates, bug fixes?
Yes.
2. This doesn’t affect customers with on-premises exchange. Customers who have exchange online are only impacted. – Is this correct?
The first effected will be the 365 users, It's possible that they will update local exchange server with this.
3. Customers with exchange online have below options instead of basic authentication
a. There are 2 options only that the customer can choose from – Oauth authentication or NTLM authentication – Is this correct?
There is also digest.
b. If the customer chooses NTLM - we will use setUseNTLMAuthentication - is this sufficient?
Yes.
c. If the customer chooses OAuth - what should we do to support this?
OAuth is not supported by EWSJ.
Thanks,
Varsha
--
Best Regards,
Jonathan Sanders,
Developer & Support Eng,
NetComps LTD
Jonathan Sanders,
Developer & Support Eng,
NetComps LTD