Departmental fire and rescue services that already use a heterogeneous application portfolio face a recurring question: how to integrate a new tool without dismantling what works. The arrival of Grovop in the operational ecosystem, combined with the Artemis portal of SDIS61 and its central authentication service AUTH2, concretely poses this problem.
The Artemis SDIS61 portal relies on a centralized login screen, with username and password, and offers a notification option before redirecting to other services. This mechanism suggests a path for integration that does not involve replacing each application, but rather aligning with this single entry point.
Centralized AUTH2 Authentication: The Technical Pivot to Exploit
The central authentication service AUTH2 of the Orne SDIS is the building block on which any integration strategy should be based. Instead of connecting Grovop directly to each existing business tool, the logic is to go through this common portal.
In practice, AUTH2 functions as a single control point. An agent identifies themselves only once, then accesses the authorized services without re-entering their credentials. The option “Notify me before connecting to other services,” visible on the Artemis login screen, confirms that redirection to third-party services is already planned in the architecture.
It is on this basis that it becomes feasible to integrate Grovop and Artemis SDIS61 without starting from scratch. If Grovop can be registered as a declared service in AUTH2, the agent does not need a new username-password pair. The portal manages the session.
The available data does not confirm which authentication standards AUTH2 supports (SAML, OAuth2, CAS, or other protocols). This point needs to be verified directly with the publisher or the information systems department of SDIS61, as it conditions the technical feasibility of the connection.
Grovop and Separate Access Rights: Managing Coexistence Without Migration
The main issue is not strictly technical. It is organizational. Integrating Grovop into an existing authentication portal is not enough if access rights are not thought out separately for each tool.
A professional firefighter, a duty officer, and an administrative agent do not have the same needs in Artemis or Grovop. Access profiles must remain independent from one tool to another, even if authentication is common. Merging roles under the guise of simplification would create security vulnerabilities or inappropriate access.
The separation of rights involves maintaining two distinct permission repositories, each linked to the unique identity of the agent in AUTH2. Here are the elements to clarify before any deployment:
- Map existing profiles in Artemis (operational roles, administrative roles, consultation roles) and ensure they will not be overwritten by the addition of Grovop
- Define in Grovop autonomous permission groups, without dependence on Artemis roles, to prevent changes in one tool from inadvertently affecting the other
- Plan an access audit mechanism that separately tracks connections to each service, in order to maintain clear visibility in case of an incident
Field feedback varies on the actual difficulty of this separation. Some SDIS that have integrated third-party tools into their authentication portal report role conflicts during updates. Others have encountered no friction. The risk largely depends on the granularity of the rights model already in place.
Progressive Deployment Strategy for SDIS: Where to Start
The classic temptation is to plan a general switch, with a target date and group training. In the context of an SDIS, where operational continuity does not tolerate any interruption, this approach is risky.
A more cautious strategy relies on deployment in concentric circles. The first circle targets a pilot service or fire station, with a limited number of volunteer agents. The pilot must last long enough to cover at least one complete operational cycle (shifts, interventions, handovers).
During this phase, both systems coexist. The pilot group agents access Grovop via AUTH2, while the rest of the staff continues to use only Artemis and the usual tools. No data is forcibly migrated. The old tool remains the reference until the new one has proven its reliability in the field.
Points of Caution During Coexistence
The prolonged coexistence of two tools on the same authentication portal generates concrete questions. Who provides first-level support when an agent no longer knows which tool to search for information? How to avoid double entry if Grovop and an existing tool partially cover the same functional scope?
- Designate a reference person for each fire station or service, trained on both environments, capable of answering daily questions without systematically escalating to the IT department
- Document the functional scopes of each tool in a shared table, accessible from the portal, so that each agent knows where to go according to their task
- Set a clear switch criterion (for example: the pilot group uses Grovop for a given function without resorting to the old tool for several consecutive weeks)
Known Limits and Gray Areas of Grovop-Artemis Integration
The publicly accessible content on Artemis SDIS61 does not document either the interoperability standards supported by AUTH2 or the connectors available for third-party applications. This lack of public technical information complicates any attempt at precise evaluation before direct contact with the SDIS teams.
Similarly, no public documentation describes the management of roles at the AUTH2 portal level. It is known that a centralized login screen exists, but the level of granularity of the rights it allows to manage remains opaque.
These gray areas do not mean that integration is impossible. They indicate that any estimation of cost, timeline, or complexity without access to internal documentation would be speculative. The prerequisite for any integration project remains a technical meeting between the Grovop publisher, the IT team of SDIS61, and the business referents, to confront the actual capabilities of each component.
Centralized authentication offers a viable entry point. The separation of rights protects existing uses. Progressive deployment limits operational risks. But without access to the technical specifications of AUTH2, the roadmap remains conditional.