New Features in ADONIS 16.5
ADONIS 16.5 is a minor update built on the 16.0 LTS foundation with new capabilities for both users and administrators.
A key highlight for users is the integration of a Model Context Protocol (MCP) server, which opens the door to connecting ADONIS with AI systems such as large language models (LLMs).
For administrators, this release introduces several powerful improvements:
Super admins with unrestricted system access
Automatic audit log files for continuous tracking of administrative actions
Support for preauthorized scopes in OIDC client configurations
Additionally, this release includes fixes for issues discovered since the release of ADONIS 16.0 LTS.
New Features for All Users
MCP Services
ADONIS 16.5 now includes a Model Context Protocol (MCP) server, making it easier to connect with AI systems.
MCP is an open standard that enables AI applications to connect with external tools like ADONIS. This allows information and capabilities to be exchanged smoothly between ADONIS and systems such as large language models (LLMs), reducing the need for complex custom integrations.
Agent-based access: To use MCP, an agent is required that connects to the ADONIS MCP server and communicates with the AI system. Typically, such an agent is developed or provided by the customer.
LLM subscription: Integrating with an LLM usually requires a subscription to the chosen LLM provider (e.g., OpenAI).
Preconfigured tools: ADONIS comes with a set of ready-to-use tools that let you find models and objects by name and description, view their properties, and execute saved searches via natural-language prompts.
Extensibility: Additional tools can be configured to expose any functionality of the ADONIS REST API by BOC Solution Engineers as part of customising projects.
Context-sensitive execution: All tools operate in the context of the user account under which the MCP requests are executed, ensuring that permissions and repository restrictions are respected.
This new integration capability makes it easier to connect ADONIS to LLMs and other AI technologies for tasks such as natural-language queries, context-aware reporting, or AI-assisted analysis.
Customers who can provide their own agent (e.g., via internal developers) can enable MCP services in ADONIS and use the preconfigured tools immediately. For additional requirements or to extend MCP capabilities with custom tools, contact your ADONIS consultant. They can help assess your needs and initiate a customising project to configure the necessary tools for your use cases.
New Features for ADONIS Administrators
Enable MCP Services
In the ADONIS Administration, you can activate access to the new Model Context Protocol (MCP) server. To do this:
Enable access to the ADONIS REST API
Activate the MCP services
Optionally, configure IP restrictions to limit which IP addresses can access the MCP server
Once access to the MCP server is enabled, a local agent is required to manage communication between your chosen LLM and ADONIS. This agent is an independent component and is not provided out of the box.
With a properly configured agent, you can use the MCP services in ADONIS. For example, you can ask your agent questions in natural language, which are then processed using the preconfigured MCP tools.
For details on enabling the MCP services, please refer to the section "MCP Services" in the Administration Help.
Guidance on using the MCP services and a reference implementation in Python for creating an agent is available via the BOC Developer Portal.
Super Admins
Super admins have unrestricted access to the entire system, including all tool components and database contents. This enables them to perform all administrative tasks without limitation.
One such super admin account (the user Admin) is created automatically during ADONIS installation. To correlate administrative actions to specific individuals and track them in the audit log, additional users can be designated as super admins.
These users can then temporarily activate super admin mode to access to administrative functions and disable it again when it is no longer required.
For details on configuring administrators in ADONIS, including super admins, global administrators, and sub-administrators, please refer to the section "Configure Users as Administrators in ADONIS" in the Administration Help.
Audit Log Files
ADONIS now automatically records administrative actions in log files. Audit entries are written to *_audit.log files located in the default /logs folder within the application server installation directory. This functionality is always active and cannot be disabled.
By default, sensitive data (such as user names and user properties) is encrypted in the audit logs. If needed, however, audit data can be deanonymised. Audit log files are also automatically included in the support information package (SIP).
The existing audit log that can be enabled manually in the ADONIS Administration and exported as CSV still exists. However, it is scheduled for removal in a future ADONIS version.
For details on the new audit log files, please refer to the section "Audit Log Files" in the Administration Help.
OIDC: Preauthorized Scopes
ADONIS can act as an OpenID Provider (OP) and, in this role, authenticate users for external applications (OIDC clients), allowing them to sign in with their ADONIS credentials.
New in ADONIS 16.5: When configuring a client application to authenticate users via ADONIS, it is now possible to define preauthorized scopes.
If an authorization request is sent where all requested scopes are preauthorized, and the user is already logged in, the request is granted immediately without displaying a consent dialog. If at least one of the requested scopes is not preauthorized, the consent screen is still shown.
This enhancement is especially relevant for micro frontend scenarios, where seamless access without repeated authorization is desired.
For details, please refer to the section "Authentication > OIDC" in the Administration Help.
Migration from an Earlier Version of ADONIS to ADONIS 16.5
Changes to Software Requirements
Please note the following changes to the software requirements for running ADONIS when migrating from previous versions.
No longer supported
Tomcat 8 and Tomcat 9
Java 8 and Java 11
Added support for
Tomcat 10.1 and Tomcat 11
Java 17 und Java 21
Upgrade ADONIS
The Installation Manual contains a number of migration guides that will help you upgrade ADONIS from an older version to version 16.5. Each guide contains all the steps that need to be taken, with everything explained in detail:
Migration from All Other Versions to ADONIS 16.5
If you are using ADONIS 13.0 or earlier, please contact your ADONIS consultant for assistance with the required steps.
Install Hotfix
You are already using ADONIS 16.5 and want to install a hotfix? Here are step-by-step instructions: