EWS OAuth: Misconfigured client secret field (error?code=7000215)
Getting the below alert after entering the mailbox credentials in the popup.
{"error":"invalid_client","error_uri":"https:\/\/login.microsoftonline.com\/error?code=7000215"}
Reason: The configured client secret in the application is incorrect. Either the value is incorrect (configured the value from different application) or users might have configured the secret id value in the client secret field.
Resolution: The text under "Value" should be configured in the client secret field. If this value isn't stored anywhere (viewable once and it will be masked after that), create a new client secret and configure it in the application.
Preferably try saving the settings in Firefox browser.
New to ADSelfService Plus?
Related Articles
Troubleshooting Oauth configuration for mail server settings
Oauth in ServiceDesk Plus / AssetExplorer for Mail SDP supports Oauth configuration for Office365 and GSuite mailboxes since 11106 build. Office365 mailboxes can be configured with Oauth authentication using EWS (since 11106) and IMAP / SMTP (since ...EWS OAuth configuration with screenshots from Azure
In order to configure EWS OAuth configuration successfully, please follow the exact steps in the below link, https://help.servicedeskplus.com/configure-azure-as-authentication-server Note: For client secret, there would be a field called 'Value' as ...OAuth Mail fetching Error
While trying to configure the mails during OAuth Configuration if you get the following error in the logs -> microsoft.exchange.webservices.data.core.exception.service.remote.ServiceRequestException: The request failed. The request failed. The remote ...Account based outgoing mail sever settings post build 14001
ACCOUNT-BASED OUTGOING MAIL SERVER FEATURE: Introduction: Account-based outgoing mail server feature was introduced in build 14001. This feature ensures that users receive notifications and responses from the specific email address associated with ...Office 365 basic Auth deprecation - Solution
If you are using Office 365, please note that the issue could be due to Microsoft depreciating basic authentication. You have to configure mordern authentication (Oauth) to fix it. Please refer the below article for reference Office 365 basic Auth ...