Our SQL DBAs are working to move most/all our SQL connections to SSL. They have asked if Adaxes can support this.
Yes, it is supported. However, per Microsoft documentation SSL support in SQL was stopped starting with version 2016 and now TLS is used. For details, have a look at the following article: https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/enable-encrypted-connections-to-the-database-engine?view=sql-server-ver15.
For information on how to enable logging to an external MS SQL database, have a look at the following help article: https://www.adaxes.com/help/EnableExternalDatabaseLogging.
Thank you, yes, I did mean TLS. It looks like the communication is not using TLS. If we disable the ability on the SQL server to accept non-TLS connections will it start using that connection method?
Yes, that should work just fine.
Can the logging database be run on SQL 2019?
Dear Adaxes team, Please confirm if Adaxes 2019.1 support SQL server 2017 for logging database. Also suggest Adaxes steps to perform if we are migrating our logging database from SQL server 2012 to SQL server 2017
I am evaluating Adaxes. I noticed that the web interface does not allow modification of the External Email Address (ms-Exch-Target-Address). What would someone do if they needed to change the Target Address?
I'm seeing this error when I run a user deprovision. It still executes the script but nobody likes errors! Run PowerShell Script 'DuoDeprovisionExport' For the user. The term ' ... running an export script in the first place for my Duo user info. ) Thanks.
We are looking for a tool that can support a blacklist for password resets and that will enforce this blacklist to certain OU groups but not others, or potentially use a whitelist of users that it will not be enforced upon.