Google and Microsoft will soon withdraw basic authentication support for mail servers by February 2021 and October 2020, respectively. Therefore, it is advisable for users to switch to OAuth authentication.
You can also connect to a different service provider, but SupportCenter Plus provides support only for Microsoft Azure (for O365) and G Suite (for Gmail).
For outlook, we support EWS only.
For Gmail, we support IMAPS, SMTP, and SMTPS protocols.
Currently, the OAuth support is available only for Windows variants of SupportCenter Plus.
For Microsoft Outlook, your application must be running in HTTPS mode.
For Gmail, your hostname must end with a public top-level domain (TLD) such as .com, .org, etc.
Yes. You can configure OAuth for an existing account.
Yes, you can use the Client Details of your existing App/Project in your authorization server to authenticate SupportCenter Plus. Make sure that you add the Redirect URL of SupportCenter Plus to the App/Project and save it.
Redirect URL or Reply URL is the URL to which the Authorization Server sends confidential response data. Copy-paste the Redirect URL to the application details in the Authorization Server and save it.
Check if you have added the application server's redirect URL to your authorization server's list of redirect URLs. Learn how to do this here. Ensure that you have saved the settings.
A popup should appear, but browsers usually block popups. Make sure to look out for alerts or check the browser's URL bar if the popup is blocked. If yes, choose the option to allow pop-ups and try again. If it still fails, try using a different browser.
If the user details are incorrect, you will not be able to connect. Click Save to retry signing in.
Check if the hostname you are accessing is the same as in the redirect URL. For example, when the redirect URL is https://helpdesk.zylker.com/ but you are accessing the application using the IP address, you will be redirected to the redirect URL from where you might not have signed in.
When your access token gets expired, a new access token will be automatically generated using the refresh token.
Users will not be notified on the expiry of an access token. The application automatically generates a new access token.
Refresh Tokens may or may not expire depending on the configurations of your service provider.
When your refresh token expires, the corresponding portal's mail fetching/sending will fail as the application cannot authenticate the mail server.
If your refresh token has expired, you must generate new tokens from the authorization server by repeating the configurations given here.
Check whether the account specified in the Mail Server Settings page and the one you signed in with are the same.
You will not be allowed to configure the same account for mail fetching in more than one portal. However, you may configure the same account for mail sending in different portals.