ℹ️ OpenFin Workspace: OpenFin Workspace is a commercial product and this repo is for evaluation purposes (See LICENSE.MD). Use of the OpenFin Container and OpenFin Workspace components is only granted pursuant to a license from OpenFin (see manifest). Please contact us if you would like to request a developer evaluation key or to discuss a production license.
OpenFin Workspace empowers you to browse and search your Microsoft 365 org data using OpenFin Home, via our Microsoft 365 integration API. OpenFin Home provides you with a fast and intuitive interface for discovering your Microsoft data. Low Code Integrations take this one step further by giving you an easy way to enable this integration through a few lines of code and some config.
To run this sample you can:
- Clone this repo and follow the instructions below. This will let you customize the sample to learn more about our APIs.
Before you can integrate your Microsoft 365 with OpenFin Home, you must following the required configuration steps for our Microsoft integration.
When configuring CORS, the URL that you need to add is: http://localhost:8080, corresponding to the hostname and port number that this sample uses.
Once you have completed the configuration steps, update the customSettings section in the sample app's manifest file as follows:
tenantId: the tenant id of your Microsoft 365 orgclientId: the client id of your application
With Microsoft 365 is configured and the sample custom settings updated, you can continue to run the sample.
- Install dependencies. Note that these samples assume you are in the sub-directory for the sample.
npm install-
Optional (if you wish to pin the version of OpenFin Workspace to version 20.0.0 and you are on Windows) - Set Windows registry key for Desktop Owner Settings. This example runs a utility dos.mjs that adds the Windows registry key for you, pointing to a local desktop owner settings file so you can test these settings. If you already have a desktop owner settings file, this script prompts to overwrite the location. Be sure to capture the existing location so you can update the key when you are done using this example.
(WARNING: This script kills all open OpenFin processes. This is not something you should do in production to close apps as force killing processes could kill an application while it's trying to save state/perform an action).
npm run dos- Start the test server in a new window.
npm run start- Start Your Workspace Platform (this starts Workspace if it isn't already running).
npm run client-
OpenFin Home will appear. Start typing into Home. At this point you will be prompted to log in to your Microsoft 365 org), and to authorize your App's request for permissions.
-
Assuming login and authorization was successful, OpenFin Home will now start returning results. Start typing a users name from your organization and the Microsoft 365 directory will be searched.
-
Build the project if you have modified the code.
npm run buildTo access some of data in the graph API you might need specific permissions that needs to be granted by an administrator.
Working with OpenFin's Microsoft Low Code Integration
This is an example of how to use our APIs to configure OpenFin Workspace. It's purpose is to provide an example and provide suggestions. This is not a production application and shouldn't be treated as such. Please use this as a guide and provide feedback. Thanks!