Components

Archibus is deployed on Tomcat, with Apache as reverse proxy. It is configured with SSO.

1. SAML for accessing AXVW files etc.

   • OIDC connect for accessing the REST API via path /archibus/api.

   • The Apache server hosts the Archibus Outlook web add-in HTML and related files on path /outlookaddin.

2. Azure AD is the identity provider for SAML and OIDC.

3. Outlook can be running in a browser window, or as a desktop application. See platforms details in Install Outlook Web Add-in for End Users .

4. The room information view loads in a separate popup window.

Connections

• Outlook loads the Archibus Outlook web add-in HTML and related files from the Archibus server based on the information in the add-in manifest. The manifest is installed as described in Install Outlook Web Add-in for End Users .

• The Archibus Outlook web add-in relies on the Office JavaScript API to interact with Outlook.

  • To retrieve meeting details.

  • To retrieve an OIDC token. Outlook forwards this request internally to Azure AD as needed.

  • To add a location to the meeting.

• The Archibus Outlook web add-in calls the Archibus REST API using the OIDC token retrieved from the Office JavaScript API.

• The Archibus Outlook web add-in can display room information in a popup window. For each room, the corresponding AXVW path including URL parameters is retrieved from the Archibus REST API.

• The room information popup window connects to Archibus Web Central like a regular browser window. Authentication in this browser window is separated from the authentication used to access the REST API.

• The Archibus Outlook web add-in only specifies a path when calling the Archibus REST API and when opening the room info popup. Therefore, they are accessed via the same protocol, host and port specified in the add-in manifest for loading the add-in HTML files.