Invantive TOTP method broken with Exact Online

Dear Team from Invantive,
It seems that the change of method on the login in EOL as broken the TOTP :-((( described here Circumvent two-step verification and refresh tokens on Exact Online using Data Hub

Exact now requires a 2-page-step login+password followed by TOTP.

now my QueryTool seems lost… the TOTP is not filled like before

Thanks for your help

It is recommended to register your own client ID as instructed on Registratie Exact Online app voor gebruik met Invantive Control for Excel (only in Dutch, I am sorry). Essentially, this enable use of your own Exact Online app.

Further, you will need to upgrade to a recent 20.2 production release, such as 20.2.27 or newer, as found on https://releasenotes.invantive.com.

That will solve the log on issue.

For the near future, Exact and Invantive will change their partnership to provide large accounting firms and customers in general with more flexibility while maintaining our view on how to best implement security according to ISO 2700[12] and the OAuth standard.

Thanks @guido.leenders
I had the OAuth method since July 2021 … but… since Exact requires exact continuity between refresh tokens as described here Old refresh token used I am using OAuth accross multiple iIvantive product (QueryTool and Data Hub for me) AND also multiple Exact databases (=multiple EOL divisions)

I moved to TOTP because of the above described error.

Am I wrong ?

I am using Beta 20.1.537

Ok, PROD 20.2.27 works with the new Exact login logic & TOTP.

Then I’m lost.

I though that Invantive BETA releases were always more advanced than PROD ones.

Although the numbering always seemed strange to me (prod 20.2 > beta 20.1)
now PROD 20.2.27 vs BETA 20.1.537

thanks for your insight on this numbering question…

Yes, TOTP logic is recommended when running on secured hardware and when needing to connect from multiple devices, such as cluster configurations or even devices located across Europe.

The version numbering convention for the last years has been:

  • Versions follow MAJOR.MINOR.BUILD.
  • Build increments continuously.
  • Minor numbers increment continuously and reset to 0 on an increment of version.
  • Odd numbers as minor version are non-production, even numbers for minor version are production.
  • The major version typically reflects the year of publish, but can be different.