x Want to participate? Join the group to interact
  • State Not Answered
  • Replies 4 replies
  • Subscribers 134 subscribers
  • Views 2116 views
  • Users 0 members are here
Browse Forums
Announcements
270
topics
260
replies
Databases and Operating Systems
761
topics
2k
replies
Financials Suite
1k
topics
3k
replies
General Discussion
2k
topics
10k
replies
Operational Suite
852
topics
2k
replies
Reporting and Analytics
1k
topics
3k
replies
Reports, Macros, and Customizations
877
topics
3k
replies
Sage CRM for Sage 300
183
topics
414
replies
Dave Swan

Any information on Sage SQL Server Certificate

Posted By

According to the Sage KB116170 information "In a new implementation like 2023 or in an upgrade where a new DSN using the ODBC Driver 18 for SQL Server to connect, your will require a Server Certificate in place for SQL to connect to the SQL database properly. The required Certificate will need to be named exactly the same as the server name. It is important to plan with your IT staff to purchase a Server Certificate and have it in place to avoid any delays in your installation. A Microsoft link about Certificates is available below for your IT staff for reference."

Does any one have any specifics on what type of certificate is needed as Self Certification is not recommended by Microsoft?  

Parents
  • 0

    I'm not sure, but from what I have read, you may need a certificate similar to what is required for SSL for IIS Web sites. Also meaning the DB Server name should be a FQDN to allow mandatory encryption to work.

    There is an option in the ODBC driver to "Trust Server Certificate" which sounds much like the "Insecure connection" to localhost "Do you trust it?". With this option turned on I can connect the a SQL DB Server, which will only have the locally signed certificate that windows servers self generate. This will allow encryption, but is a risk of man in the middle attacks.

    There is more info from MS
    https://learn.microsoft.com/en-au/sql/connect/odbc/windows/dsn-wizard-4?view=sql-server-ver16

    Otherwise make encryption optional, which is not recommended.

Reply
  • 0

    I'm not sure, but from what I have read, you may need a certificate similar to what is required for SSL for IIS Web sites. Also meaning the DB Server name should be a FQDN to allow mandatory encryption to work.

    There is an option in the ODBC driver to "Trust Server Certificate" which sounds much like the "Insecure connection" to localhost "Do you trust it?". With this option turned on I can connect the a SQL DB Server, which will only have the locally signed certificate that windows servers self generate. This will allow encryption, but is a risk of man in the middle attacks.

    There is more info from MS
    https://learn.microsoft.com/en-au/sql/connect/odbc/windows/dsn-wizard-4?view=sql-server-ver16

    Otherwise make encryption optional, which is not recommended.

Children

*Community Hub is the new name for Sage City