Errors connecting to repository after setting Force Encryption to Yes

There is an additional step in the connection information configuration of the monitored instance requiring SSL.

In DPA, click Options > Update Connection Info.

Select the SQL Server monitored instance that needs the SSL connection, and click Next.

Select JDBC URL Properties, and add ssl=request

You may also set it to ssl=require

Thanks for the quick response!

With the Force Encryption set to Yes, I can't even login to DPA.  To test your idea, I temporarily switched it back to No.

I need to clarify that the issue is with the connection to the Repository (not the Monitored server).  I found "Update Repository Connection" under Options/Administration, but it says:

To change the repository database connection information, edit the file then restart DPA.

'{DPA_INSTALL_DIR}/iwc/tomcat/ignite_config/idc/repo.properties'

When I open that file, I don't see anything related to SSL or encryption.

Any other thoughts?

Thanks again.

Ah, I was thinking SSL to the monitored instance.  I that repo.properties file please add the following:

repo.jdbcDriverProperties=ssl\=request

Save the file

Restart Ignite PI server service.

Thanks for the reply.  Sorry for the delay in getting back to this.  I determined that the Force Encryption really isn't necessary like I thought.

I will try this suggestion on a weekend when I have a maintenance window.

Again, sorry for the delay.  I was finally able to get to this today.

chenry's suggestion worked.  I actually had to implement both suggestions because now both the Dev and Prod servers have SSL required.

For review, here is what I did:

In '{DPA_INSTALL_DIR}/iwc/tomcat/ignite_config/idc/repo.properties', I added a line:

     repo.jdbcDriverProperties=ssl\=request

In Options / Monitor Setup / Update Connection Info, selected my Database Instance and Next.  Checked the "JDBC URL Properties" and added "ssl=request" in the textbox.  The restart happened automatically.

Thanks!