FME Version
Introduction
This article will walk through the additional configuration steps required to get your functional FME Form OneDriveConnector web connection working in FME Flow.
Please note that Microsoft Azure is subject to change at any time, so the instructions and screenshots in this article may not exactly reflect those relevant to your Azure Portal. The overall concepts, however, will be the same.
Requirements
- A single tenant or multitenant OneDriveConnector web connection that is working in FME Form. Please see one of the following articles to first build your OneDriveConnector web connection in FME Form:
- Access to your Azure Portal and permissions to manage the Azure App Registration tied to your working FME Form OneDriveConnector single tenant or multitenant web connection
- FME Flow must be configured for HTTPS. Please see Configuring FME Flow for HTTPS.
Step-by-step Instructions
Part 1: Modify the Azure App Registration
To successfully use your functional FME Form OneDriveConnector web connection with FME Flow, your related Azure app registration must include the web as a platform, with a valid Client Secret and FME Flow redirect URI. The following steps detail how to modify your single tenant or multitenant Azure app registration to meet these requirements.
1. Open Your Single Tenant or Multitenant App Registration in Azure Portal
Login to Azure portal and go to App Registrations.
Click on the app registration tied to your functional FME Form OneDriveConnector web connection to access its configuration options.
2. Add the Web Platform and Redirect URI
Click the Authentication menu at left, and then select 'Add a platform'. Choose Web.
For the redirect URI, enter your FME Flow URL followed by /fmeoauth. For example, https://myfmeserver.mydomain.com/fmeoauth. Note that your FME Flow instance must be configured to use HTTPS.
Click Configure.
You should now see Web added with the redirect URI. You can add additional redirect URIs for other Instances of FME Flow that you plan to use with your OneDriveConnector web connection.
3. Create a New Client Secret
To connect to Microsoft OneDrive from FME Flow, you must have a client secret applied to your Azure app registration. This is not required in FME Form; it is only required in FME Flow.
Microsoft requires a client secret for confidential web apps (and this should not be used in a native app, like FME Form).
Click Certificates & secrets from the left-side menu, and then select 'New client secret'.
Give your client secret a description and expiry. Click Add.
Once your client secret expires, you will need to create a new one and update your FME Flow web service with the new Client Secret value to continue connecting to OneDrive.
After clicking Add, make sure to copy the secret value (not the Secret ID) and store it in a safe place, like a password manager. You will only get one chance to save the secret value! You can create another secret if needed.
Your Azure app registration is now ready for use with FME Flow.
Part 2: Publish the FME Form OneDriveConnector Web Service and Connection to FME Flow and Modify
1. Publish to FME Flow
In FME Form, open a workspace that makes use of the OneDriveConnector and your working OneDriveConnector web connection. Ensure that this web connection's web service makes use of the same Azure app registration that you modified in Part 1, above. Click the publish button.
Confirm that the web connection you are about to publish is tied to the Azure app registration you modified in Part 1, above. If you are not confident on this point, cancel out of the publish wizard, and confirm that the Client ID value of your FME web connection's web service matches the Application (client) ID value of the Azure app registration you modified. The Client ID value of the web service can be accessed in FME Workbench by navigating to Tools > FME Options > Web Connections > Manage Services, and then selecting the web connection's web service from the list of web services displayed.
Proceed through the publish wizard. On the Upload Connections step, make sure to select the check box next to the OneDriveConnector web connection in use in your workspace. This action will upload both the web connection and its underlying web service to FME Flow.
Click Publish to publish the workspace with the web connection to FME Flow.
2. Modify the Web Service on FME Flow
Log in to the Web UI of the FME Flow instance you published to in Step 1. From the side menu, click Connections & Parameters. If you’re using a version of FME Flow prior to 2023, click Files & Connections. You should see the connection(s) you published from FME Workbench and their associated web services. Click Manage Web Services.
Click on the web service you want to edit (i.e the web service that was published along with your OneDriveConnector web connection).
Fill in the details for your web service:
- Description (optional): it’s recommended to update the description so that it reflects at minimum the name of the Azure app registration used by this web service
- Client Id: this value should already be present and match the Application (client) ID from the Azure app registration that you modified in Part 1, above
- Client Secret: the client secret value from your Azure app registration, found in Certificates & Secrets. If you did not save the value when you first created the secret, you will need to create another in Azure.
- Redirect URI (or Authorization URL): the Redirect URI, ending in fmeoauth, for your FME Flow instance. This was added to the web platform in your Azure app under Authentication in Part 1 - Step above. For example, https://myfmeserver.mydomain.com/fmeoauth
Click OK to save the changes.
3. Authorize the Web Connection on FME Flow
Return to the Web Connections page. Click on the web connection associated with the web service.
Click Authorize. You will be prompted to log in with your Microsoft credentials and may be prompted to grant consent to the Azure app registration. Once authorized successfully, the web connection will have a green checkmark. Click OK to close the web connection.
The OneDriveConnector web connection is now ready for use on FME Flow.
Repeat this same process of modifying the web service and authorizing the web connection for any other OneDriveConnector web connections that you publish from FME Form to FME Flow. The process is the same for single tenant or multitenant-based OneDriveConnector web connections.
Related Resources
How to Create a OneDriveConnector Single Tenant Web Connection in FME Form
How to Create a OneDriveConnector Multitenant Web Connection in FME Form
Comments
0 comments
Please sign in to leave a comment.