Release notes of Invantive Connect
Release Note - Hosted
Invantive Connect, new in 27.0
| Build | Date | Description |
|---|---|---|
| – | – | the product did not exist |
27. |
01-11-2026 | latest build of release 27.0 at the time of writing |
Invantive Connect is the OAuth 2.1 and OpenID Connect server of Invantive. It takes over from AWS Cognito as the issuer of tokens and as the page where people log on. End users meet it when they log on, sign up or set up a second factor. Administrators run it and manage its clients. Developers of clients, such as AI assistants, register a client and request tokens with it. One log-on serves Invantive Cloud, Bridge Online, the forum and MCP Server. The product is new in release 27.0: there is no older release to compare with, so this note lists what the product can do instead of what changed.
- 41 enhancements
- 0 bug fixes
- 16 things to check before upgrading
This Note
- Before You Upgrade
- Top 25 Changes
- All Enhancements 2
- All Bug Fixes 0
- What It Builds On
- More Information
Enhancements
Before You Upgrade
These changes ask for a check:
- Authorization code flow with a proof key (S256) for every client
- A client has to send a code challenge with method S256 in every authorisation request.
- Every access token carries an audience that the resource server checks
- A client of MCP Server has to send the resource parameter with the address of its database.
- Access tokens are signed JWTs that servers can check without calling Connect
- After switching or retiring a key, every node has to be restarted.
- Password rules and an optional check against leaked passwords
- Set Connect:Credentials:BreachedPasswordCheck to Online to use the leaked password check; it is off by default.
- Password log-on for Bridge Online and UniversalSQL Server
- Each of these servers needs its own client and secret at Connect, set in its own settings.
- Internal check of credentials for servers that cannot ask a user
- Name the addresses of the calling servers in Connect:Internal:AllowedAddresses; without them nothing can reach this endpoint.
- Single log-on for the support forum
- The forum administrator has to point the OpenID Connect plugin at the discovery document and register the forum callback address at Connect.
- Create and maintain clients without a restart
- Register the redirect and log-out addresses of every product at its client before it uses Connect; a client name or address that differs on one side only is refused.
- Management accounts with a second factor, an address limit and a short life
- Create a management account per support engineer with the administration tool after installation.
- Migration of accounts, passwords and second factors from AWS Cognito
- Run the migration, first as a dry run, before any product switches to Connect.
- Users who were not migrated are taken over at their first log-on
- Provide the Cognito settings and an access key limited to reading one account and setting a password, for the duration of the transition only.
- Accounts and secrets in a database of their own
- Create the database, roles, tables and views with the delivered scripts; PostgreSQL 18 or later is the workspace minimum.
- Installation scripts for the database, with a script per environment
- Run the scripts in the order given in the rollout plan and fill in the addresses of the environment.
- Several nodes behind a load balancer with a shared key directory
- Behind a load balancer, name its addresses in Connect:ForwardedHeaders:KnownProxies on every node.
- Mail for confirmation, reset and password changes over SMTP with retries
- Name a mail server in Connect:Mail:Smtp and give every node its own node name; with delivery on, a node does not start without a mail server.
- Checks at start-up and a sample file that lists every setting
- Place the licence file and the database definitions in the AppData/Config folder before the first start.
Top 25 Changes
- OAuth 2.1 and OpenID Connect server with discovery document and key set
- Enhancement
- A capability that the new product offers from release 27.0.
- Dynamic client registration for AI assistants without a client secret
- Enhancement
- A capability that the new product offers from release 27.0.
- Every access token carries an audience that the resource server checks
- Enhancement
- A capability that the new product offers from release 27.0.
- One log-on for all products, with silent renewal and log-out
- Enhancement
- A capability that the new product offers from release 27.0.
- A second factor is required for every account
- Enhancement
- A capability that the new product offers from release 27.0.
- Authorization code flow with a proof key (S256) for every client
- Enhancement
- A capability that the new product offers from release 27.0.
- Strict rules for clients that register themselves
- Enhancement
- A capability that the new product offers from release 27.0.
- Consent page for clients that registered themselves
- Enhancement
- A capability that the new product offers from release 27.0.
- Refresh tokens are replaced on every use, and reuse is detected
- Enhancement
- A capability that the new product offers from release 27.0.
- Access tokens are signed JWTs that servers can check without calling Connect
- Enhancement
- A capability that the new product offers from release 27.0.
- Log-on page with e-mail address, password and an option to stay signed in
- Enhancement
- A capability that the new product offers from release 27.0.
- Sign-up with e-mail confirmation and return to the application
- Enhancement
- A capability that the new product offers from release 27.0.
- Password reset by mailed code and password change
- Enhancement
- A capability that the new product offers from release 27.0.
- Password log-on for Bridge Online and UniversalSQL Server
- Enhancement
- A capability that the new product offers from release 27.0.
- Single log-on for the support forum
- Enhancement
- A capability that the new product offers from release 27.0.
- Management pages for users, clients, scopes, resource servers, keys and audit
- Enhancement
- A capability that the new product offers from release 27.0.
- Create and maintain clients without a restart
- Enhancement
- A capability that the new product offers from release 27.0.
- Administration tool for clients, users, management accounts, mail and migration
- Enhancement
- A capability that the new product offers from release 27.0.
- Migration of accounts, passwords and second factors from AWS Cognito
- Enhancement
- A capability that the new product offers from release 27.0.
- Accounts and secrets in a database of their own
- Enhancement
- A capability that the new product offers from release 27.0.
- Scopes per Invantive product: cloud-api, mcp, bridge-online and connect-internal
- Enhancement
- A capability that the new product offers from release 27.0.
- Users can see and withdraw the applications they allowed
- Enhancement
- A capability that the new product offers from release 27.0.
- Token lifetimes can be set per installation
- Enhancement
- A capability that the new product offers from release 27.0.
- Lockout after failed log-ons, per user and per address
- Enhancement
- A capability that the new product offers from release 27.0.
- Password rules and an optional check against leaked passwords
- Enhancement
- A capability that the new product offers from release 27.0.
All Enhancements
Changes to behaviour, platforms, drivers and settings, grouped by area.
Importance: all | 2 and higher | 3 and higher | 4 and higher | 5
Platform: all | AWS Cognito (2) | Discourse (1) | PostgreSQL (2)
2 of 41 shown.
Installation and platform
Installation scripts for the database, with a script per environment
Delivered scripts create the roles, the tables, the views and the first resource servers and clients. The views can be created again after an upgrade, and an upgrade script adds the indexes to an older database. The environment script never changes an existing row.
What to Do
Run the scripts in the order given in the rollout plan and fill in the addresses of the environment.
- PostgreSQL
- importance 3
Security
Accounts and secrets in a database of their own
Connect keeps its accounts, clients, grants, tokens, sessions, secrets, audit trail and mail queue in its own PostgreSQL database with its own roles. It reads nothing from the Customer Service database. Secret values are encrypted with a key that exists on the Connect hosts only.
What to Do
Create the database, roles, tables and views with the delivered scripts; PostgreSQL 18 or later is the workspace minimum.
- PostgreSQL
- importance 4
All Bug Fixes
Defects of the older release that are repaired.
None.
Announced, Not Yet Available
- The discovery document is built by the protocol library, and no code in the repository adds a registration endpoint address to it, so clients that look for registration in the discovery document would not find it.
- The switch of production to Connect, with the order T-0 to T-6 of the rollout plan, is not recorded as done; the walk on the test environment is still an open step.
- Administrators other than named management accounts cannot yet open the management pages; the provisioning of administrators is not designed.
- A page with the log-on events of a user for the user themselves is not built; the events are only visible to support staff and in the administration tool.
- The log-on, sign-up, password, consent and management pages are English only, and the Dutch texts of the new translation keys are not written.
- AWS Cognito is still referenced for the transition: the fallback, the mirror of password changes and the removal of the migration data at step T-6 are not done.
- The design asks for a refresh token that slides for 30 days with an absolute limit of 90 days; only one configurable lifetime of 30 days exists in the code.
- Management of a registration after the fact (RFC 7592) is not offered; a client registers again.
- Front-channel and back-channel log-out are not offered; only the end-session endpoint exists.
- OAuth or personal access tokens for BI tools on Bridge Online are declined in the design; BI tools keep using Basic authentication.
- Automatic key rotation is not offered; rotation is a manual three-step action followed by a restart of every node.
What It Builds On
| Kind | Name | From | To |
|---|---|---|---|
| invantive component | Invantive Connect | 27.0.54 | |
| invantive component | Invantive(R) Basics | 27.0.93 | |
| invantive component | Invantive(R) Cloud API Shared | 27.0.93 | |
| invantive component | Invantive(R) SQL for Core | 27.0.93 | |
| invantive component | Invantive(R) SQL | 27.0.93 | |
| invantive component | Invantive(R) Web Core Library | 27.0.93 | |
| build tool | Invantive Deploy | 27.0.93 | |
| third party summary |
More Information
- Product manual
- Product documentation
- Questions and answers on the forum
- Downloads
- All release notes
- RFC 6749: The OAuth 2.0 Authorization Framework
- RFC 6238: Time-based one-time passwords
- RFC 7591: OAuth 2.0 Dynamic Client Registration
- RFC 8252: OAuth 2.0 for native apps
- RFC 8414: OAuth 2.0 Authorization Server Metadata
- RFC 8707: Resource Indicators for OAuth 2.0
- Pwned Passwords range service
- Discourse OpenID Connect authentication plugin
- OpenIddict releases
How This Note Was Made
- Not verified by a second reading: the capabilities come from one reading of the documents and source.
- The product did not exist in the previous release, so there is no range of commits to compare.
- The capabilities were read from the documents and the source of the newer state by one reader; each item names no commits.
- Items that are designed but not built at the newer state are not listed; they are recorded as not yet available.