Semiweb
Back to Nagano

API and interoperability

A platform that fits into your institutional environment.

Nagano offers several authentication and data exchange mechanisms to ease its integration into the technology environments of research institutions.

Conceptual illustration: Nagano at the centre, linked to institutional authentication, to other Nagano installations and to the institution's systems.

Authentication

Authentication suited to your institution.

Nagano can use LDAP / Active Directory, OAuth2 — including Microsoft Entra ID depending on the configuration — or its own authentication mechanism.

  • LDAP / Active Directory

    Users sign in through the institutional directory.

  • OAuth2 / Entra ID

    Authentication through a configured provider, including Microsoft Entra ID depending on the deployment.

  • Nagano authentication

    Accounts and passwords managed directly in the platform.

These mechanisms concern how users sign in. The application exchanges presented below rely on their own authentication mechanisms.

Inter-Nagano

Exchanges between Nagano installations.

Nagano installations can communicate with each other to support certain inter-institutional processes, including exchanges of information, statuses, forms and documents related to multicentre projects, depending on the supported configurations and scenarios.

Each exchange links specific installations around projects linked to each other: it is not an automatic synchronisation of all data.

Conceptual illustration: the Nagano installation of institution A exchanges forms, statuses and documents with those of institutions B and C, around a multicentre project.

Technology environment

Several ways to link Nagano to your environment.

Depending on the context, Nagano can fit into an institution's technology environment in different ways: through institutional authentication, through exchanges between Nagano installations or through interfaces developed for a specific need.

  • Institutional authentication

    LDAP / Active Directory or OAuth2, including Microsoft Entra ID depending on the configuration.

  • Exchanges between Nagano installations

    Some installations can exchange information in configured contexts, notably for multicentre projects.

  • Targeted interfaces

    Interfaces can be developed to link Nagano to an institutional system when the need warrants it.

Integrations

Interfaces that match the institution's needs.

Nagano also has integration mechanisms intended for certain external systems. The possibilities and terms are assessed according to the context and technical environment of each institution.

Integrations suited to the context

Each interface is developed or adapted case by case, according to the institution's needs and the systems involved.

Conceptual illustration: the connected systems vary from one institution to another. Nagano linked to a few generic external systems: a database, settings, a cloud service and documents.