What's new in version 2.0
Version 2.0.70
Released on November 18, 2026. This is first of all a security release: it closes several accesses that a user or a visitor could obtain without being entitled to them. Install it without delay.
Documents are no longer published through a public link
When a SmartMaker application displayed the documents of a record, SmartAuth created a public Dolibarr share link for each of them. Such a link opens the file without logging in and never expires: a document viewed from an application could therefore be read by anyone who got hold of its link.
Applications now receive a private reference, which opens nothing by itself: every download checks the rights of the logged-in user. SmartAuth no longer creates any share link. Those created by previous versions remain public, see "Update" below.
Document downloads made from the applications are now recorded in the API log.
Registration and forgotten password
- The registration form no longer asks for a password: it is chosen on the page opened by the link of the confirmation email. Only the person who receives the emails of the address can therefore activate the account. Until now, someone could register the address of a third party with their own password and take over the account as soon as it was confirmed.
- The password reset link is sent only to the address of the user themselves, never to the one of their company or contact, often a shared mailbox.
- The "forgot password" form refuses a request sent from another site.
- The "you already have an account" email is sent at most once per cooldown and five times a day for the same address: it can no longer be used to flood a mailbox.
- Login, registration and token attempts are counted before being checked: a burst of simultaneous requests reaches the limit instead of getting through all at once.
- Deleting an account created by self-service registration also disables its portal accesses.
- The single sign-on (SSO) portal refuses a login that belongs to another Dolibarr entity.
Devices and notifications
- A user can no longer rename or take over the device of another user.
- A notification sent to a device no longer reaches the subscription of another user.
- In the push notification log, a user who is not an administrator only sees their own notifications.
SmartAuth tab and administration pages
- A forged link can no longer revoke or delete all the tokens of a user from the SmartAuth tab of their record: these actions are accepted only when sent by the page itself.
- Revoking several devices at once now reports only the devices really revoked.
- The Cancel button of the token and device cards can no longer send you to another site.
- Creating the Dolibarr OAuth client, testing its connection and sending feedback check the security token of the page.
- The email address of a user can no longer inject code into the SmartAuth dashboard.
A dashboard that tells the truth
- Failed logins count real failures, not every token refresh, PostgreSQL included.
- The weekly change of active tokens is displayed: it always read 0 %.
- The refresh success rate is read from the request log: it always read 0.0 %. When this log is not collected, the card says so instead of showing a rate.
- The dashboard, the API log list and the title of the setup page are translated into every language of the module.
- On Dolibarr 19 to 21, the device filter of the token and log lists works: it displayed an error.
Offline synchronization
- The same offline change sent twice at the same time no longer creates two records.
- A deletion sent through synchronization no longer erases a record changed in the meantime on the server.
- The application is told which fields of a change were not saved.
Applications and integrators
- The
sharefield of document lists holds a private reference instead of the Dolibarr share link; it is used as before with?q=orfile/{hash}. - A choice list of an extra field is refused when its definition would read a secret column, also for the values returned with a record.
- A bank account can no longer be attached through the API to a company outside the user's scope.
- The numeric filters of the API lists refuse a value that is not a number.
- IPv6 addresses are kept whole in the API log.
- The accents of the Spanish, Portuguese, German, Polish and Italian translations are restored.
Update
- Replace the
smartauthfolder with the one from the 2.0.70 archive. No module re-enablement is needed. - The public share links created by previous versions, for the documents viewed from the applications, remain active. To close those that must not be public, remove the share of the file in the Linked files tab of the Dolibarr record concerned.
Version 2.0.68
Released on November 13, 2026.
This version also includes the content of versions 2.0.62, 2.0.64 and 2.0.66, which were not distributed. Their fixes are described below.
An external user only sees their own company
An external user is a Dolibarr user attached to a third party: the access of a customer to their portal, or that of a subcontractor. In Dolibarr, they only see the data of their company. In SmartMaker applications, only their Dolibarr right was checked: an external user allowed to read third parties saw all the third parties, contacts, commercial proposals and invoices of the entity, not only those of their company.
SmartAuth now applies the same boundary as Dolibarr, when reading as when saving, including for the changes made offline and sent later. An external user can no longer attach a record to a company other than their own either.
If external users log in to your applications, install this version without delay.
No password or key in a choice list
Applications display the choice lists of extra fields of type "list from a table". When the definition of such a list came from data imported by a module, and not from a field you declared, it could designate any Dolibarr table.
SmartAuth now refuses any list that would read a table or a column holding secrets (passwords, keys, login tokens, Dolibarr settings), as well as any filter that would not be a simple condition. The list is then displayed empty and the reason is written to the Dolibarr log.
No more false synchronization conflicts
When an application sends a change made offline, SmartAuth checks that the record was not changed in the meantime on the server. This check used the wrong date format: every change sent was reported as a conflict, and the user had to choose between their version and the server's although nobody else had touched the record.
Only a record really changed on the server since the last synchronization now triggers a conflict.
Photo lists on Dolibarr records
You can add a photo list to interventions, projects, contacts and members. To
do so, create an extra field whose code starts with smartlistphoto_, for
example smartlistphoto_before for the photos taken before an intervention.
The SmartMaker applications that display this field let you take and annotate
several photos in it; each photo is saved as a document attached to the
record.
The maximum number of photos of a field is set in Setup > Modules > SmartAuth, tab PWA fields: between 1 and 100, 20 by default. The setting belongs to the field, every application that displays it applies it. When you delete the field, its setting is erased automatically by the SmartAuth scheduled job.
Photo uploads resumed without duplicates
An application that loses the network in the middle of a photo upload resumes it later. SmartAuth recognizes this retry and does not create a second copy of the file. This now also works for applications installed on another domain than your Dolibarr, whose retries were refused until now.
Fields that no longer lose their value
Fields whose name contains a dot, such as the birth date of a member in some applications, arrived empty on the Dolibarr side: their value was lost when saving. They are now saved normally.
More reliable login and startup
- An application that logs in with an invalid device identifier now receives a clear message, instead of a server error.
- On a hosting that restricts file access (
open_basedir), the PHP log no longer receives a warning at every activation or update of a SmartMaker module. - When several applications log in at the same time right after the installation, SmartAuth prepares its configuration without error.
Fixes of versions 2.0.62 to 2.0.66
- On Dolibarr 24, pairing a phone by QR code and the login history of the SmartAuth tab of the user record work again.
- On Dolibarr 23 or later with MySQL or MariaDB, the first activation of the module creates the table of application logins correctly.
- On MySQL or MariaDB, the annotations added to photos are kept again: they were lost at every reload.
Update
- Replace the
smartauthfolder with the one from the 2.0.68 archive. - Disable then re-enable the SmartAuth module in Setup > Modules. This step is required: it creates the settings of the photo lists and repairs the storage of photo annotations.
Version 2.0.60
Released on October 20, 2026.
Mobile applications know whether the server responds
A mobile application connected to SmartAuth regularly checks that the server is reachable, to know whether it can send what it recorded while offline. It now has an address intended for that, which responds without prior login, without loading the database and without filling SmartAuth's request log, even if called every minute.
Until now, this check went through addresses that required a login: the application could think the server unreachable when it was responding.
An incomplete installation is clearly reported
A SmartMaker module, such as SmartInterventions, needs SmartAuth. If SmartAuth's activation fails, for example because one of its tables could not be created, Dolibarr still leaves the SmartMaker module enabled. Its mobile application then failed to log in with a database error that was hard to understand.
The application now receives a message indicating that SmartAuth is not enabled, and the cause is written in the Dolibarr log. To fix it, enable SmartAuth in Setup > Modules: the error message displayed at activation indicates what is blocking.
Synchronization conflicts resolved on the right object
When a modification made offline conflicts with a modification made in the meantime on the server, SmartAuth keeps both versions until the user chooses. Each conflict now records the exact type of the object concerned, and the application receives it directly instead of deducing it.
The user's choice is thus applied with the rules of that object type (editable fields, rights), including when a SmartMaker module adds its own object types alongside those of SmartAuth.
Update
- Replace the
smartauthfolder with the one from the 2.0.60 archive. - Disable then re-enable the SmartAuth module in Setup > Modules: re-enablement adds the new synchronization conflict information. Without re-enablement, everything keeps working, conflicts being then attached to their type as before.
Version 2.0.59
Released on October 20, 2026.
A photo's title and caption stay in the file
When a mobile application connected to SmartAuth sends a photo with a title, a caption or keywords, this information can now be written into the photo file itself, and no longer only in Dolibarr.
A photo downloaded from Dolibarr, copied onto a workstation or sent to a customer thus keeps its description. Common photo viewers and software display it, because it is stored in the standard XMP format.
The formats concerned are JPEG, WebP and PNG. The image itself is not modified: its quality remains that of the upload. If the description is modified later, it is rewritten in the file without being duplicated.
This capability is used by mobile applications that transmit this information with their photos. If writing fails on a file, the photo is still saved as it was sent.
Update
- Replace the
smartauthfolder with the one from the 2.0.59 archive. - No module re-enablement is needed: the new feature applies as soon as the files are replaced.
Version 2.0.58
Released on October 16, 2026.
Version 2.0.58 is a security release. It strengthens the end of sessions opened by single sign-on (SSO) with the services connected to SmartAuth. We recommend installing it quickly.
A stolen session is cut off entirely
An application connected to SmartAuth regularly renews its session. Each renewal is single-use: if an old renewal is presented again, SmartAuth sees the sign of a theft and cuts off the whole session.
Until now, this cutoff only affected the first renewals of the session. The most recent one, still used by the application or the person who stole it, remained valid. Now, the session is cut off entirely, no matter how many renewals have already been made.
A logout takes effect everywhere within minutes
Services connected via SSO themselves verify the authorizations that SmartAuth gives them and regularly consult the list of those that have been withdrawn. Several actions did withdraw access in SmartAuth without listing it: the service concerned then kept accepting the person for up to an hour.
The following actions now take effect on all connected services within minutes:
- changing or resetting the password;
- logging out, of one session or of all sessions, from the My account page;
- logging out from a connected service;
- deleting the account by its holder;
- cutting off a stolen session, described above;
- withdrawing an access requested by a connected application.
Update
- Replace the
smartauthfolder with the one from the 2.0.58 archive. - No module re-enablement is needed: the fixes apply as soon as the files are replaced.
Version 2.0.56
Released on October 12, 2026.
Version 2.0.56 is a fix release. After the update, disable then re-enable the module (see "Update" below): the index fix only takes effect on re-enablement.
Mobile applications stay connected
When a mobile application renews its session, SmartAuth checks that the presented token has not been used already. Until now, if the database was momentarily unavailable at that moment, SmartAuth concluded that the token was stolen and logged the device out.
Now, a database outage returns a temporary error: the session is kept and the application retries on its own. A token that is really reused is still treated as an attack.
Module activation checked
At activation, SmartAuth checks that each of its tables was properly created. If one is missing, activation is refused and a message indicates the tables involved, instead of an enabled module that then fails on the first login.
Complete indexes under PostgreSQL
Several module tables shared the same index names. Under PostgreSQL, only the first of each name was created, and the other tables remained without an index on these columns. Each index now carries the name of its table. Under MySQL and MariaDB, the old indexes are replaced by the new ones when the module is re-enabled.
Replies to emails attached to the right record
The emails sent by SmartAuth (password reset, registration, new connection alert, alternative address confirmation) carry the Dolibarr tracking identifier of their recipient. If you use the Dolibarr email collector, a reply to one of these emails is attached to the user, member or third party concerned.
Update
- Replace the
smartauthfolder with the one from the 2.0.56 archive. - In Home > Setup > Modules, disable then re-enable SmartAuth. Re-enabling creates the missing indexes and removes the old index names.
- If re-enablement is refused, the message lists the missing tables: check the rights of the database user, then enable again.
Version 2.0.54
Released on October 7, 2026.
Version 2.0.54 follows a complete security audit of the module. It also includes the content of 2.0.52, which was not distributed: the member password reset described below is part of it.
After the update, disable then re-enable the module (see the last section): several fixes only take effect on re-enablement.
Who sees what in the administration
The dashboard, the token list, the device list and the login logs now require the SmartAuth read permission. They no longer show anything but the data of the current entity.
On the SmartAuth tab of the user record and in the token list, a user can only revoke, rename or delete their own tokens. Operations on other users' tokens are reserved for administrators. Deleting a device now revokes its tokens.
Action links (revocation, deletion, renaming, links on the configuration page) are protected against forged requests: a trapped link opened by an administrator no longer has any effect.
Renaming a token works again: the name is stored on the corresponding device.
Passwords and sessions
- A password reset always revokes OAuth2 sessions, in addition to mobile application tokens.
- For a member who also has a user account, the new password is written on both identities: logging into the application no longer rejects the password that was just chosen.
- Changing your password from the account page logs out the other sessions.
- Deleting your account by the user also revokes their mobile sessions and anonymizes the associated contact and third party.
- SSO login attempts are limited by address and by identifier.
Single sign-on to the Dolibarr back-office
Logging into the Dolibarr back-office via SmartAuth now works:
the return from authentication reaches the module, and the login
page accepts internal users. The return address of the OAuth client
dolibarr-erp becomes <Dolibarr address>/index.php?afteroauthloginreturn=1.
Re-enabling the module adds this address to the existing client.
If you declared another OAuth client for the back-office, add this return address yourself to its record. See OAuth2 and OpenID Connect.
The consent page correctly displays members. An application that asks for a new authentication no longer causes a login loop.
Offline synchronization
Mobile application synchronization applies the same visibility rules as the API: a user who only sees their own projects or events no longer downloads others through synchronization. Synchronization conflicts no longer keep sensitive fields, and a malformed modification is reported on its own instead of blocking the whole upload.
Push notifications
Notifications are sent to recipients according to their entity and group rights. The sending log can be purged by an administrator.
Bug fixes
- The application list displays again on MySQL databases.
- Global search in the token, log and device lists works again.
- The OAuth client list shows all clients when no status filter is chosen.
- The OAuth logout page displays the revocation message again.
- Several fatal errors on some extrafield types are fixed.
- French accents are restored in the translations.
Update
- Replace the
smartauthfolder with the one from the 2.0.54 archive. - In Home > Setup > Modules, disable then re-enable
SmartAuth. Re-enabling adds indexes on the token tables, enables
the cleanup scheduled task and updates the return address of the
dolibarr-erpclient. - Check that the users who view the dashboard, tokens or logs do have the SmartAuth read permission. See Configuration.