DOMI Oauth Application
The web application uses Eclipse Vert.x. This was a technology choice because Vert.x removes the need for deployment to a web server, provides pre-built Java libraries for OAuth integration and there was in-house expertise to allow rapid development.
Project Documentation
You can access the project documentation generated by Maven (including a JavaDoc) by opening the Product Documentation
Endpoints Available
For each provider, this application provides endpoints for retrieving a token, callback for short-term code (only for use from OAuth providers), refreshing a token and (where supported by the online meeting provider) revoking a token. The endpoints in use are:
- If a Zoom Client ID and secret are passed into the application
- /dominoZoom/index.html
- /zoomCallback
- /dominoZoomRefresh
- /dominoZoomRevoke
- If a Teams Client ID and secret are passed into the application
- /dominoTeams/index.html
- /teamsCallback
- /dominoTeamsRefresh
- If a GoToMeeting Client ID and secret are passed into the application
- /dominoGTM/index.html
- /gtmCallback
- /dominoGTMRefresh
- If a Webex Client ID and secret are passed into the application
- /dominoWebex/index.html
- /webexCallback
- /dominoWebexRefresh
- /index.html - a catch-all landing page
Table of contents
- Meeting Provider OAuth Apps
- Running from Eclipse
- Running from Docker
- Metrics
- Configuration
- Development