OAuth 2.0 Configuration for MS Exchange
This support article provides instructions for configuring EMS Exchange Integration Web Service (EIWS) to access 365 mailboxes using OAuth with Microsoft Exchange Web Services.
Until now, Provar had been using basic authentication for Microsoft Exchange Web Service (EWS). Provar users can now access Microsoft Emails using OAuth 2.0 using Microsoft (EWS) by creating a new connection or updating an existing connection. And they can use Send, Subscribe, and Receive Message Test APIs with Microsoft Exchange for emails.
Provar Application registration in Azure Active Directory (AD)
To register an application in Azure AD:
- Log into aad.portal.azure.com with the appropriate admin account.
- Click Azure Active Directory in the menu.
- Under the Manage section, click App Registrations.
- Click New Registration.
- In the Name field, enter a name to register the new application.
- Set Supported account types as appropriate.
- Click Register.
The Provar Application is registered.
Configure permissions in Azure Active Directory
To configure permissions in the Azure Active Directory:
1. In App registrations, select the application registered in the previous section.
2. Under Manage, click API Permissions.
3. Click Add a permission.
4. Under my organization’s APIs, type “office” in the search box and select Office 365 Exchange Online.
5. Under Applications permissions, select full_access_as_app (Application) and EWS.AccessAsUser.ALL (Delegated).
If you previously created an application for Exchange-to-EMS Synchronization for EMS for Microsoft Exchange (formerly Exchange Room Integration), you can add the full_access_as_app and EWS.Access.AsUser.ALL permission to your existing application.
6. Click Done.
7. Under Grant Consent, select Grant admin consent for (your domain here).
8. Select Yes. The permissions are displayed in a list.
9. Under Manage, click Certificates & secrets.
10. Select New Client Secret. In the Expire field, select an appropriate expiration duration. Click Save.
11. A value is displayed. Copy this value and make a note since this is the only time this value is displayed.
12. From the Overview section, copy the Application ID and Tenant ID to add to the EMS configuration.
13. To get the Redirect URI, click on Redirect URIs, as shown in the above screenshot.
14. Click Add a Platform.
15. Select Web from the Web Application section.
16. Enter the Redirect URI e.g. https://oauth.pstmn.io/v1/browser-callback
18. Click Configure. The screenshot given below shows the Redirect URI.
- Provar Automation
- Installing Provar Automation
- Updating Provar Automation
- Using Provar Automation
- API testing
- Behavior-driven development
- Creating and importing projects
- Creating test cases
- Custom table mapping
- Debugging tests
- Defining a namespace prefix on a connection
- Defining proxy settings
- Environment management
- Exporting test cases into a PDF
- Exporting test projects
- Override auto-retry for Test Step
- Managing test steps
- Namespace org testing
- Provar desktop
- Provar Test Builder
- Refresh and Recompile
- Reintroduction of CLI license Check
- Reload Org Cache
- Running tests
- Searching Provar with find usages
- Secrets management and encryption
- Setup and teardown test cases
- Tags and Service Level Agreements (SLAs)
- Test cycles
- Test plans
- Testing browser options
- Tooltip testing
- Using the Test Palette
- Test Palette introduction
- Control test steps
- Generate Test Case
- List compare
- Page Object Cleaner
- Read test step
- String test steps
- UI Test Steps
- Using custom APIs
- Callable tests
- Data-driven testing
- Page objects
- Block locator strategies
- Introduction to XPaths
- Creating an XPath
- Label locator strategies
- Maintaining page objects
- Mapping non-Salesforce fields
- Page object operations
- Refresh and reselect field locators in Test Builder
- Using Java method annotations for custom objects
- Applications testing
- Database testing
- Document testing
- Email testing
- Mobile testing
- OrchestraCMS Testing
- Guide in Salesforce CPQ Testing in Provar
- Guide in ServiceMax Testing
- Skuid Testing
- Vlocity API Testing
- Webservices testing
- Introduction to test scheduling
- Apache Ant
- Configuration for Sending Emails via the Automation Command Line Interface
- Continuous integration
- AutoRABIT Salesforce DevOps in Provar Test
- Azure DevOps
- Running a Provar CI Task in Azure DevOps Pipelines
- Configuring the Automation secrets password in Microsoft Azure Pipelines
- Parallel Execution in Microsoft Azure Pipelines Using Multiple build.xml Files
- Parallel Execution in Microsoft Azure Pipelines using Targets
- Parallel execution in Microsoft Azure Pipelines using Test Plans
- Bitbucket Pipelines
- Gearset DevOps CI/CD
- GitHub Actions
- Integrating GitHub Actions CI to Run Automation CI Task
- Remote Trigger in GitHub Actions
- Parameterization using Environment Variables in GitHub Actions
- Parallel Execution in GitHub Actions using Multiple build.xml Files
- Parallel Execution in GitHub Actions using Targets
- Parallel Execution in GitHub Actions using Test Plan
- Parallel Execution in GitHub Actions using Job Matrix
- GitLab Continuous Integration
- Travis CI
- Execution Environment Security Configuration
- Provar Jenkins Plugin
- Parallel Execution
- Running Provar on Linux
- Salesforce DX
- Team Foundation Server
- Version control
- Provar Automation trial guide and extensions
- Salesforce Testing
- Adding a Salesforce connection
- Assert Page Error Messages on Add/Edit Product
- Internationalization support
- List and table testing
- Salesforce Release Updates
- Salesforce Lightning Testing
- Salesforce Lightning Web Component (LWC) locator support
- Salesforce console testing
- Visualforce Testing
- Provar Manager
- Best Practices
- Configurations and permissions
- Error messages
- Licensing, installation and firewalls
- Test Builder and test cases
- Release Notes