invantive documentation
Invantive Support ForumsLog In / Sign Up

Release notes of Invantive Connect

Release Note - Hosted

Invantive Connect, new in 27.0

Build Date Description
– – the product did not exist
27.0.54 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

Before You Upgrade

These changes ask for a check:

Top 25 Changes

  1. 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.
  2. Dynamic client registration for AI assistants without a client secret
    • Enhancement
    • A capability that the new product offers from release 27.0.
  3. Every access token carries an audience that the resource server checks
    • Enhancement
    • A capability that the new product offers from release 27.0.
  4. One log-on for all products, with silent renewal and log-out
    • Enhancement
    • A capability that the new product offers from release 27.0.
  5. A second factor is required for every account
    • Enhancement
    • A capability that the new product offers from release 27.0.
  6. Authorization code flow with a proof key (S256) for every client
    • Enhancement
    • A capability that the new product offers from release 27.0.
  7. Strict rules for clients that register themselves
    • Enhancement
    • A capability that the new product offers from release 27.0.
  8. Consent page for clients that registered themselves
    • Enhancement
    • A capability that the new product offers from release 27.0.
  9. Refresh tokens are replaced on every use, and reuse is detected
    • Enhancement
    • A capability that the new product offers from release 27.0.
  10. Access tokens are signed JWTs that servers can check without calling Connect
    • Enhancement
    • A capability that the new product offers from release 27.0.
  11. 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.
  12. Sign-up with e-mail confirmation and return to the application
    • Enhancement
    • A capability that the new product offers from release 27.0.
  13. Password reset by mailed code and password change
    • Enhancement
    • A capability that the new product offers from release 27.0.
  14. Password log-on for Bridge Online and UniversalSQL Server
    • Enhancement
    • A capability that the new product offers from release 27.0.
  15. Single log-on for the support forum
    • Enhancement
    • A capability that the new product offers from release 27.0.
  16. Management pages for users, clients, scopes, resource servers, keys and audit
    • Enhancement
    • A capability that the new product offers from release 27.0.
  17. Create and maintain clients without a restart
    • Enhancement
    • A capability that the new product offers from release 27.0.
  18. Administration tool for clients, users, management accounts, mail and migration
    • Enhancement
    • A capability that the new product offers from release 27.0.
  19. Migration of accounts, passwords and second factors from AWS Cognito
    • Enhancement
    • A capability that the new product offers from release 27.0.
  20. Accounts and secrets in a database of their own
    • Enhancement
    • A capability that the new product offers from release 27.0.
  21. Scopes per Invantive product: cloud-api, mcp, bridge-online and connect-internal
    • Enhancement
    • A capability that the new product offers from release 27.0.
  22. Users can see and withdraw the applications they allowed
    • Enhancement
    • A capability that the new product offers from release 27.0.
  23. Token lifetimes can be set per installation
    • Enhancement
    • A capability that the new product offers from release 27.0.
  24. Lockout after failed log-ons, per user and per address
    • Enhancement
    • A capability that the new product offers from release 27.0.
  25. 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)

Installation and platform

Administration tool for clients, users, management accounts, mail and migration

A command-line tool does what the management pages do, and works when the log-on itself is broken. It sets and resets client secrets, imports secrets from a file, edits redirect addresses, shows log-on attempts, clears lockouts, removes a second factor, and closes, opens and deletes accounts. Without the apply option it only reports what it would do.

  • importance 4
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
Several nodes behind a load balancer with a shared key directory

Nodes share one key directory and one database. A cookie written by one node opens on the other, and missing keys are created once, even when nodes start at the same time. Forwarded headers are believed only from named load balancers, so the log, lockout and address checks see the real caller.

What to Do

Behind a load balancer, name its addresses in Connect:ForwardedHeaders:KnownProxies on every node.

  • importance 3
Mail for confirmation, reset and password changes over SMTP with retries

Each node sends the mail it queued itself. A failed mail is tried again with waits that double from one minute to an hour, up to 10 times by default. In development, mail is written to files and never sent.

What to Do

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.

  • importance 3
Checks at start-up and a sample file that lists every setting

Connect refuses to start on a missing or wrong setting, such as the issuer, the key directory, the licence or the mail server, and names the setting. The sample file written at every start lists every key with its documentation. The issuer cannot change once tokens have been issued.

What to Do

Place the licence file and the database definitions in the AppData/Config folder before the first start.

  • importance 3

Licensing and sign-in

OAuth 2.1 and OpenID Connect server with discovery document and key set

Invantive Connect offers the authorize, token, user information, log-out and revocation endpoints. A discovery document and a key set let a client find the addresses and check token signatures without further set-up. The endpoints have no path prefix.

  • importance 5
Dynamic client registration for AI assistants without a client secret

An AI client can register itself with a single request and receives a client identifier. No client secret is handed to users. The registration follows RFC 7591.

  • importance 5
One log-on for all products, with silent renewal and log-out

A browser that is already signed in gets a code straight away, so the user does not type credentials again. Clients can ask for a new password with prompt=login or refuse any page with prompt=none. A log-out endpoint ends the session and returns to an address registered by the client.

  • importance 5
Log-on page with e-mail address, password and an option to stay signed in

Users log on with their e-mail address and password. An account whose address was never confirmed, or that was closed, is refused before the password is checked. The account is read again at every authorisation and every token exchange, so closing it takes effect at once.

  • importance 4
Sign-up with e-mail confirmation and return to the application

Anyone can create an account. The address has to be confirmed through a link that is valid for one day. A sign-up for an address that already has an account gives the same answer, so the page does not reveal which addresses are known.

  • importance 4
Password reset by mailed code and password change

A reset link is valid once and for 60 minutes by default. Asking for a reset gives the same answer for every address, and a second mail within two minutes is not sent. After a reset or a change, all tokens of the user are revoked and all browser sessions end.

  • importance 4
Password log-on for Bridge Online and UniversalSQL Server

These servers receive the user name and password of a BI tool. They exchange them once at Connect for a short-lived token of 10 minutes without a refresh token. Only confidential clients that have been given this permission may do so, and the same lockout and audit trail apply as on the log-on page.

What to Do

Each of these servers needs its own client and secret at Connect, set in its own settings.

  • importance 4
Single log-on for the support forum

The forum signs in through Connect with the OpenID Connect plugin. A user who is signed in elsewhere reaches the forum without typing credentials again. The forum matches accounts on the confirmed e-mail address that Connect reports.

What to Do

The forum administrator has to point the OpenID Connect plugin at the discovery document and register the forum callback address at Connect.

  • Discourse
  • importance 4
Migration of accounts, passwords and second factors from AWS Cognito

A one-time run copies the accounts of the Cognito pool to Connect with the same subject. It carries over password hashes and authenticator secrets from the vault without overwriting anything Connect already holds. A dry run and a verify option check the result.

What to Do

Run the migration, first as a dry run, before any product switches to Connect.

  • AWS Cognito
  • importance 4
Scopes per Invantive product: cloud-api, mcp, bridge-online and connect-internal

Besides the standard scopes, there is one scope for each server that accepts tokens. A client reaches a server only while it holds the matching scope. Administrators can add or change scopes and resource servers on the management pages.

  • importance 3
Application tokens for servers with the client credentials grant

Servers of Invantive obtain a token for themselves with a client identifier and secret. The token names the application, not a user, and carries the audiences of its scopes. A secret can be reset on the management pages or with the administration tool.

  • importance 3
Claims in the tokens and the user information endpoint

Tokens carry the subject, e-mail address, whether it is confirmed, name, language and the methods used to sign in. Name and language are only included when the profile scope was asked for. The user information endpoint answers with the current values of the account.

  • importance 3
Users who were not migrated are taken over at their first log-on

While the transition lasts, a user without a stored password is checked once against Cognito and then stored in Connect. The authenticator secret is fetched first; without it the log-on is refused. A changed or reset password is also written back to Cognito until that mirror is switched off.

What to Do

Provide the Cognito settings and an access key limited to reading one account and setting a password, for the duration of the transition only.

  • AWS Cognito
  • importance 3
Do not ask for a code again on a trusted computer for 30 days

A user can mark a computer as trusted after answering a code. The tokens then still show that two factors were used. The trust ends when the authenticator is replaced.

  • importance 2

Security

Every access token carries an audience that the resource server checks

The resource parameter of RFC 8707 decides for which server a token is valid. For MCP Server the audience is the exact address that was asked for, so a token for one database does not open another database. A request without a resource gets the audiences of its scopes, and a client credentials request without any audience is refused.

What to Do

A client of MCP Server has to send the resource parameter with the address of its database.

  • importance 5
A second factor is required for every account

Every interactive sign-in uses a code from an authenticator application, and the requirement cannot be switched off. A user without an authenticator sets one up at the first log-on, by barcode link or by typing the secret. Authenticators that users already hold for Invantive Cloud keep working.

  • importance 5
Authorization code flow with a proof key (S256) for every client

Interactive sign-in uses the code flow, and every client has to send a proof key, public or confidential. Only the S256 method is offered, because the plain method gives no protection. The implicit flow is not available.

What to Do

A client has to send a code challenge with method S256 in every authorisation request.

  • importance 4
Strict rules for clients that register themselves

A self-registered client is always a public client and may only use the code and refresh token grants. Redirect addresses must be absolute and use https, with a plain http exception for loopback addresses of native clients. One address may register 10 clients per hour by default, and a registration that was never used is removed after 30 days.

  • importance 4

A user sees the client name, that it registered itself, where it sends the user back to, the resource it wants and what each permission means. The answer is remembered, so the page does not return at the next sign-in. Products of Invantive itself do not ask for consent.

  • importance 4
Refresh tokens are replaced on every use, and reuse is detected

A refresh token is valid for 30 days by default. When a token that was already used is presented again, the whole authorisation is revoked. A short tolerance of 5 seconds by default lets a client retry after a lost answer.

  • importance 4
Access tokens are signed JWTs that servers can check without calling Connect

Resource servers check the signature with the published key set. Refresh tokens and codes stay encrypted and never leave Connect in readable form. An administrator can rotate the signing key in three steps: publish a new key, switch to it, retire the old one.

What to Do

After switching or retiring a key, every node has to be restarted.

  • importance 4
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
Users can see and withdraw the applications they allowed

The profile page lists the applications with consent, with their permissions and the date of consent. Withdrawing consent revokes the tokens of that application for the user. A user can also sign out of all browser sessions at once.

  • importance 3
Token lifetimes can be set per installation

Defaults are 120 minutes for an access token, 5 minutes for an identity token and a code, 30 days for a refresh token and 10 minutes for a token obtained with a password. Every value can be changed in the settings and is checked at start-up. Used and expired tokens are removed every hour.

  • importance 3
Lockout after failed log-ons, per user and per address

Waiting times grow from one second to fifteen minutes after repeated failures, counted for the user and for the address, whichever is longer. A throttled attempt is not counted again. The counts survive restarts and are shared by all nodes.

  • importance 3
Password rules and an optional check against leaked passwords

A new password needs at least 12 characters and may not contain the e-mail address or the name of the service. An administrator can switch on a check against the Pwned Passwords service, which receives only the first five characters of a hash. If the service does not answer, the password is accepted.

What to Do

Set Connect:Credentials:BreachedPasswordCheck to Online to use the leaked password check; it is off by default.

  • importance 3
Passwords are stored with PBKDF2 and upgraded at the next log-on

Passwords are stored as salted PBKDF2-SHA512 hashes with 210 000 iterations by default. A hash that no longer meets the policy is replaced at the next successful log-on. A weaker development algorithm is refused outside the development environment.

  • importance 3
Browser sessions are recorded and can be ended on every node

Each sign-in is stored as a session. A session ends when the user signs out, changes the password, is closed by an administrator, or loses the authenticator. A user or an administrator can end all sessions at once.

  • importance 3
Internal check of credentials for servers that cannot ask a user

A server of Invantive can send a user name and password to Connect and learn whether they are right, whether the account has a second factor and how long to wait. It runs the same checks as the log-on page. It only answers a caller with an application token from an address named in the settings.

What to Do

Name the addresses of the calling servers in Connect:Internal:AllowedAddresses; without them nothing can reach this endpoint.

  • importance 3
Management accounts with a second factor, an address limit and a short life

Support engineers sign in to the management pages with an account of their own, a password and a code. An account is limited to named addresses and expires after seven days. Sensitive pages ask for a recent sign-in, at most twelve hours old.

What to Do

Create a management account per support engineer with the administration tool after installation.

  • importance 3
Attack prevention, request filtering and address checks on the server

Connect blocks addresses that send repeated suspicious requests and filters requests by pattern. It also checks the service area of an address. Pages that people use are limited to the service area, while the token, registration, revocation, user information and discovery endpoints are open to AI platforms in the United States.

  • importance 3

Logging and diagnostics

Audit trail of log-ons and actions of support staff

Every log-on, failure, password change, second-factor change, consent and action on the management pages is recorded with the user and the address. A row says that something happened and never what was typed. Events are kept for 400 days by default.

  • importance 3
Error pages for people and error answers for programs

People see an error page with the status, a message code, the request identifier and the path, and never a stack trace. Programs that call the token, registration or management endpoints get a JSON error answer instead. The answer follows the Accept header.

  • importance 2

Other

Management pages for users, clients, scopes, resource servers, keys and audit

Support staff see the health of the server, find users and see their sessions, tokens and log-on attempts. They can revoke tokens, end sessions, reset a second factor, clear a lockout and close or open an account. Registrations of self-registered clients can be listed, and the address a registration came from can be blocked.

  • importance 4
Create and maintain clients without a restart

Administrators can create a client, add or remove redirect addresses, reset a secret and delete a client on the management pages. A new secret is shown once. Redirect addresses must use https, except on loopback, and are compared exactly.

What to Do

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.

  • importance 4
Log-on pages in the look of Invantive Cloud

The log-on, sign-up, password, consent and profile pages use the stylesheet, top bar, footer and app launcher of Invantive Cloud. Telephone, e-mail, help and footer links are set per installation, and what is absent is left out. The pages are in English only.

  • importance 2

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

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.