The server needs to support SAML 2.0 to better handle end-to-end authentication for published web services, web service data sources and cloud based databases that support SAML. It is also needed to more easily integrate with third party authentication systems like Ping Identity and Okta.
We need to enforce MFA when authenticating to TDV using the Studio client. This means we need some mechanism to pass a request to use a token, in addition to username/password.
TDV Studio, Web UI and Manager UI needs to support SSO login and enabling SSO via SAML method in Azure AD would be feasible as many of the BI tools supports this method of SSO integration. Requesting this feature, because it would be helpful for the Organization as it is easy to setup and manage.
Recently, a lot of companies have adopted SSO services to achieve collaboration through single sign-on using SAML authentication, without having to log in to each system individually each time. Especially, many BI tools users can do authentication by SAML, and there are used in front of Data Virtualization. Since it is costly to manage users separately for TDV, it is expected that TDV can also be SSO capable by SAML.
While I appreciate the enhanced OAuth 2.0 support, I request an enhancement to be able to apply SAML authentication to published REST APIs as shown in the link below.
https://community.denodo.com/docs/html/browse/8.0/en/vdp/administration/server_configuration/server_authentication/saml_authentication/saml_authentication
The lack of this feature may prevent TDV from being chosen by customers considering implementing DV solution.
I hope that you will consider this matter and that this situation will be resolved as soon as possible.
TIBCO Data Virtualization supports Open ID Connect and Oauth since version 8.5. This is the recommended protocol for integrating with Ping Identity, Okta and many other Identity and Access Management solutions.