Documentation

Communication and Routing

Our Retrieval Suite needs to have some mandatory and optional routes to function well. All communication is by default encrypted in transit. Some routes come with optional configuration parameters (for instance for LDAP communication) where the administrator has the choice on which port and protocol to use. We strongly recommend also in such scenarios to use encrypted communication.

For the base setup the following routes are needed. On the following pages, you find the routing information for indexing and query time scenarios.

Routing for Connectors and Indexing

Routing for Search and Query Scenarios

Base Setup

Database

Routes

  1. Suite → Database Server

Explanation

For productive scenarios, our Suite must have access to a SQL database, i.e., either Microsoft SQL, Postgres SQL or Oracle. The database is used to store configurations and the internal state.

Authentication

Routes

  1. Suite → Entra Id

  2. Browser → Entra Id

Explanation

The administration interface is a registered Entra Id application and users must be able to execute OIDC flows against Entra Id, when accessing the administration interface. This does not mean that the administration interface is exposed to the internet. But the browser, e.g. on the same VM, must be allowed to execute this flow. Also the Suite must be able to access https://graph.microsoft.com to verify the user identity and token.

Update Checks

Not mandatory is the following route.

Route

  1. Suite → https://www.rheininsights.com

Explanation

Our Suite performs update checks every once in a while Update Check . The API endpoint is part of our public website.