SSL Encryption Certificate with Subject Alt Name Support?

[ColinBo]

We've got a project that up until this point has used the built-in ADO.NET driver for SQL Server access. We are now deploying to a test environment that has a clustered SQL Server where encrypted connections are required. Because of the clustering and requirements of SQL Server on certificate names the actual cluster DNS name is attached to the SSL certificate as a "subject alternative name" as defined in the X.509v3 specification. To get this to work we need to switch to using the SQL Server Native Client. We have been having problems getting it working in our app with NHibernate. Wondering if:

a) is there support in the dotConnect driver for SANs in the SSL certificate? (see Encryption on a Cluster - http://technet.microsoft.com/en-us/libr ... 89067.aspx)

b) is there support for NHibernate in dotConnect for SQL Server?

[Shalex]

a) is there support in the dotConnect driver for SANs in the SSL certificate? (see Encryption on a Cluster - http://technet.microsoft.com/en-us/libr ... 89067.aspx)

The support for SANs in the SSL certificate is not available in dotConnect for SQL Server.

b) is there support for NHibernate in dotConnect for SQL Server?

NHibernate is supported (NHibernate-specific classes are available in dotConnect for SQL Server like in dotConnect for Oracle: http://blogs.devart.com/dotconnect/inde ... racle.html).