Microsoft SQL Server作为Atrifactory 7.38.10元数据数据库
我们已经在Windows Server上安装了Atrifactory 7.38.10，Microsoft SQL Server在System.yml中配置为元数据的数据库。
String connectionUrl =
"jdbc:sqlserver://localhost:1433;" +
"databaseName=AdventureWorks;integratedSecurity=true;" +
"encrypt=true;trustServerCertificate=true";
vratifactory.bat开始投掷以下提到的错误。
- 无法初始化数据库（db config：{mssql jdbc：sqlserver：//dev.tfs2017sql.xyz.com：55300; dataBasEname = jfrogpoc; engrogpoc; encrypt; encrypt = false; sendStringParametStringParametStringSunicode = falsife = falsife = falsife = falsifore = artifory repository repository repository repository repository; ：TLS握手失败：X509：未知当局签署的证书 连接到数据库的错误。放弃 jfrog.com/metadata/v7/services/common/db.(* databasebearer).init jfrog.com/metadata/< a href =“/cdn-cgi/l/email-protection” class =“ __ cf_email__” data-cfemail =“ afd998fd998819c988819f”> /database_bearer.go:152
Java版本是11，JDBC驱动程序是“ MSSQL-JDBC_AUTH-10.2.1.2.1.x64.dll”，用于Windows集成
We have installed Atrifactory 7.38.10 on a windows server, Microsoft SQL server configured in System.yml as a database for metadata.
String connectionUrl =
"jdbc:sqlserver://localhost:1433;" +
"databaseName=AdventureWorks;integratedSecurity=true;" +
"encrypt=true;trustServerCertificate=true";
Artifactory.bat start throwing below mentioned error.
- Could not initialize database (db config: {mssql jdbc:sqlserver://dev.tfs2017sql.xyz.com:55300;databaseName=JFROGPOC;encrypt=false;sendStringParametersAsUnicode=false;applicationName=Artifactory Binary Repository;integratedSecurity=true;}): TLS Handshake failed: x509: certificate signed by unknown authority
error connecting to database. giving up
jfrog.com/metadata/v7/services/common/db.(*databaseBearer).init
jfrog.com/metadata/[email protected]/services/common/db/database_bearer.go:152
Java version is 11 and JDBC driver is “mssql-jdbc_auth-10.2.1.x64.dll” for windows integrated authentication
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
从外观看，问题是在元数据服务上，如您所说。
我建议尝试跟随此文章尝试向元数据服务提供其他Golang连接URL（因为Java的脚本转换可能不支持所有参数），并确保您已将证书添加到/etc/etcl/certs文件夹中元数据服务是用Golang编写的，通常从OS加载证书，而不是从Java Trust Store中加载。
From the way it looks, the issue is on the metadata service as you said.
I suggest trying to follow this article I wrote in the past about it and try to provide to the metadata service an additional golang connection URL(as it's possible that the script conversion from the Java doesn't support all the parameters), and make sure you have added the certificate to the /etc/ssl/certs folder as metadata service is written in Golang and usually load the certificates from the OS and not from the Java trust store.