Versionshinweise zu Invantive Connect
Anmerkungen zu dieser Version - Gehostet
Invantive Connect, neu in 27.0
| Build | Datum | Beschreibung |
|---|---|---|
| – | – | 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 Verbesserungen
- 0 Fehlerbehebungen
- 16 Was Sie vor dem Upgrade überprüfen sollten
Dieser Hinweis
- Bevor Sie ein Upgrade durchführen
- Die 25 wichtigsten Änderungen
- Alle Verbesserungen 20
- Alle Fehlerbehebungen 0
- Worauf es aufbaut
- Weitere Informationen
Verbesserungen
Bevor Sie ein Upgrade durchführen
Diese Änderungen erfordern eine Überprüfung:
- 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.
Die 25 wichtigsten Änderungen
- OAuth 2.1 and OpenID Connect server with discovery document and key set
- Verbesserung
- A capability that the new product offers from release 27.0.
- Dynamic client registration for AI assistants without a client secret
- Verbesserung
- A capability that the new product offers from release 27.0.
- Every access token carries an audience that the resource server checks
- Verbesserung
- A capability that the new product offers from release 27.0.
- One log-on for all products, with silent renewal and log-out
- Verbesserung
- A capability that the new product offers from release 27.0.
- A second factor is required for every account
- Verbesserung
- A capability that the new product offers from release 27.0.
- Authorization code flow with a proof key (S256) for every client
- Verbesserung
- A capability that the new product offers from release 27.0.
- Strict rules for clients that register themselves
- Verbesserung
- A capability that the new product offers from release 27.0.
- Consent page for clients that registered themselves
- Verbesserung
- A capability that the new product offers from release 27.0.
- Refresh tokens are replaced on every use, and reuse is detected
- Verbesserung
- A capability that the new product offers from release 27.0.
- Access tokens are signed JWTs that servers can check without calling Connect
- Verbesserung
- 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
- Verbesserung
- A capability that the new product offers from release 27.0.
- Sign-up with e-mail confirmation and return to the application
- Verbesserung
- A capability that the new product offers from release 27.0.
- Password reset by mailed code and password change
- Verbesserung
- A capability that the new product offers from release 27.0.
- Password log-on for Bridge Online and UniversalSQL Server
- Verbesserung
- A capability that the new product offers from release 27.0.
- Single log-on for the support forum
- Verbesserung
- A capability that the new product offers from release 27.0.
- Management pages for users, clients, scopes, resource servers, keys and audit
- Verbesserung
- A capability that the new product offers from release 27.0.
- Create and maintain clients without a restart
- Verbesserung
- A capability that the new product offers from release 27.0.
- Administration tool for clients, users, management accounts, mail and migration
- Verbesserung
- A capability that the new product offers from release 27.0.
- Migration of accounts, passwords and second factors from AWS Cognito
- Verbesserung
- A capability that the new product offers from release 27.0.
- Accounts and secrets in a database of their own
- Verbesserung
- A capability that the new product offers from release 27.0.
- Scopes per Invantive product: cloud-api, mcp, bridge-online and connect-internal
- Verbesserung
- A capability that the new product offers from release 27.0.
- Users can see and withdraw the applications they allowed
- Verbesserung
- A capability that the new product offers from release 27.0.
- Token lifetimes can be set per installation
- Verbesserung
- A capability that the new product offers from release 27.0.
- Lockout after failed log-ons, per user and per address
- Verbesserung
- A capability that the new product offers from release 27.0.
- Password rules and an optional check against leaked passwords
- Verbesserung
- A capability that the new product offers from release 27.0.
Alle Verbesserungen
Änderungen an Verhalten, Plattformen, Treibern und Einstellungen, nach Bereichen geordnet.
Bedeutung: alle | 2 und höher | 3 und höher | 4 und höher | 5
Plattform: alle | AWS Cognito (2) | Discourse (1) | PostgreSQL (2)
20 von 41 wird angezeigt.
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.
- Bedeutung 4
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.
- Bedeutung 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.
- Bedeutung 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.
- Bedeutung 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.
- Bedeutung 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.
- Bedeutung 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.
- Bedeutung 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.
Was ist zu tun?
Each of these servers needs its own client and secret at Connect, set in its own settings.
- Bedeutung 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.
Was ist zu tun?
The forum administrator has to point the OpenID Connect plugin at the discovery document and register the forum callback address at Connect.
- Discourse
- Bedeutung 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.
Was ist zu tun?
Run the migration, first as a dry run, before any product switches to Connect.
- AWS Cognito
- Bedeutung 4
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.
Was ist zu tun?
A client of MCP Server has to send the resource parameter with the address of its database.
- Bedeutung 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.
- Bedeutung 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.
Was ist zu tun?
A client has to send a code challenge with method S256 in every authorisation request.
- Bedeutung 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.
- Bedeutung 4
Consent page for clients that registered themselves
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.
- Bedeutung 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.
- Bedeutung 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.
Was ist zu tun?
After switching or retiring a key, every node has to be restarted.
- Bedeutung 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.
Was ist zu tun?
Create the database, roles, tables and views with the delivered scripts; PostgreSQL 18 or later is the workspace minimum.
- PostgreSQL
- Bedeutung 4
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.
- Bedeutung 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.
Was ist zu tun?
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.
- Bedeutung 4
Alle Fehlerbehebungen
Fehler der älteren Version, die behoben wurden.
Keine.
Angekündigt, noch nicht erhältlich
- 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.
Worauf es aufbaut
| Art | Name | Von | Bis |
|---|---|---|---|
| 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 |
Weitere Informationen
- 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
Wie dieser Zettel entstanden ist
- 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.