Data integration - 2.2.3
New MFA function via app
With version 2.2.3, we introduced in-app MFA support, allowing users to authenticate via Google Authenticator or Microsoft Authenticator.
Previously, MFA was available only by e-mail, which limited flexibility and depended on access to the e-mail for each login.
Now the user can authenticate directly through the application of their choice, eliminating the need to access the e-mail and speeding up the login process.
This update provides greater security and convenience to the login flow. Authentication via application generates temporary and exclusive codes, considered more secure. Initial configuration is required, and the user needs a device with the authenticator app, but once configured, the new MFA method makes the experience more efficient, faster, and more secure.
For this new function, we updated the activation flows, self-registration, and manual registration, including the option of multi-factor authentication (MFA) via the application, increasing the security of data integration processes.
This function will only be enabled for environments that have MFA activated in the Authentication (CM008).
New connection to Dremio Cloud - Data source
In version 2.2.3, we added support for connecting to the new Dremio Cloud data source (AD047), expanding integration options for users.
Now, when configuring Dremio Cloud, simply fill out the connection fields and choose between authentication with Personal Access Token (PAT) or OpenID Connect, registered at the Credential center (AD069). This integration allows for data to be accessed and viewed directly on the platform, offering greater agility and ease of use.
With this new feature, users can connect to Dremio Cloud in a safe and customized way, using modern authentication methods.
This additional flexibility in choosing the data source makes the system more robust and adaptable, better meeting the needs of different environments and data architectures.
Access expiration - External and internal users
In version 2.2.3 of the system, we introduced the access expiration feature for internal and external users, allowing the system administrator to configure an automatic expiration date.
Now, a daily schedule will automatically inactivate users whose expiration date has been reached, making it easier to control temporary access and ensuring security when terminating unnecessary or old access.
This feature provides more practical and safe user management, especially for companies that need temporary or limited access.
Automatic expiration optimizes account management, ensuring that only active and authorized users remain with access to the system.
Internal user
External user
JDBC Oracle Thin connection improvements - Data source
In version 2.2.3, we improved the connection with Oracle via JDBC Oracle Thin, including new detailed information about the connected server, the driver used in SoftExpert Suite, and the ping feature for connection test.
Furthermore, all connections to external data sources now exclusively use a JAVA engine, ensuring greater compatibility and stability when connecting to database servers.
These improvements aim to optimize the configuration and monitoring of connections, providing a more robust and informative experience for the user.
OIDC authentication for databases - Credential center
In version 2.2.3, we introduce support to authentication via OpenID Connect (OIDC) for integration into database data sources, enabling the use of identity providers.
This new feature allows users to configure secure and centralized authentication, ensuring greater protection and compliance with security policies.
With this resource, users have flexibility to integrate services with modern and simplified authentication, eliminating the need to manage credentials manually.
Authentication via OIDC improves security and efficiency in integrations, meeting the demands of corporate environments and applications with robust authentication requirements.
Bearer Token authentication for Web Services - Credential center
In version 2.2.3, we implemented authentication via Bearer Token, expanding security options for accessing Web Services.
With this new feature, users can authenticate themselves in a simple and effective way, using temporary access tokens that eliminate the need for fixed credentials. Authentication via Bearer token offers an additional safety and practicality layer for integrations, ensuring quick and protected accesses.
This flexibility is especially suited to services and APIs that require dynamic authentication, providing a more secure and modern integration experience.
Blocking data sources with excessive errors - Data Source (SOAP and REST)
In version 2.2.3, we implemented an automatic blocking system for REST/SOAP data sources that exceed a 75% error rate on a minimum of 100 daily requests, protecting system stability when automatically suspending sources with high occurrence of failures.
We also added a control in the alert center (CM034) that displays detailed information about the blocked data source, including the percentage of failures and the total number of requests.
This feature makes monitoring more efficient, providing administrators with a clear and quick vision of problematic data sources and ensuring proactive management to avoid impacts on the performance and integrity of integrations.
New fields for SCIM provisioning
In version 2.2.3, the language, date of birth, and admission date fields have been added to SCIM provisioning, expanding the user profile configuration options.
Now, when provisioning users, you can include the desired language (if not specified, the system applies the default language), as well as date of birth and hire date, offering a more complete and customized profile.
These new fields bring greater flexibility and detail to user registration, allowing companies to adapt the information according to their needs and internal policies. This facilitates data integration and information management, improving personalization in the corporate environment.
Click here for further details.
Creation of the new Administrative Access - System tab
In version 2.2.3, we introduced a new tab to the System (CM006) menu. The Administrative access tab was developed to centralize e-mail and password change features, in addition to blocking and unlocking the main administrative user (root).
This update allows users to quickly find the necessary tools and configurations to efficiently manage their operations.
Additionally, we have implemented the root administrator blocking option, which can be enabled exclusively by the administrators themselves.
After requesting the block, the administrator will be automatically disconnected from the system. Unblocking, in turn, can be performed by any other administrative user with access to this feature.
Discontinuations
From version 2.2.3 onwards, the ADINTERFACE table is discontinued. Integrations that use this table must be adjusted to use DIINTERFACE.
In version 2.2.3, we also officially discontinued support for authentications via NTLM, aligning the platform with modern security standards and best authentication practices.
View the latest improvements made to this component: