Integrations and access security
What is an integration?
An integration lets you secure access to a map by requiring authentication before it can be viewed, or connect ownMap to an external service. It is configured from the map's "Integrations" tab, at the same level as "Settings". Configuration is centralized at the account level: an integration already created for one map can be reused directly on another map in the same account.
CAS authentication
ownMap can restrict access to a map via a CAS (Central Authentication Service) server, commonly used by universities and large organizations.
Once the CAS integration is enabled and configured (server address, port, context), every visitor must authenticate with your organization's CAS server before accessing the map.
- Every login attempt (successful or failed) is logged, along with the date and usage statistics for the current month.
- An integration can be enabled, disabled or removed at any time from the same page.
When a visitor calculates a route leading to another building protected by CAS, they must first have authenticated with that building: otherwise, the message "CAS authentication required for this building" is displayed.
Other integrations
Other integration types are available in the interface:
- OAuth 2.0: available and configurable like the CAS integration.
- LDAP / Active Directory: shown in the interface as "Coming soon" — activation is not yet available.
The availability of each integration is indicated directly on the "add integration" screen.
Monitoring and statistics
For each active integration, a summary shows the number of logins for the current month and the date of last use, to help you monitor usage of secure access to your map.