You are viewing limited content. For full access, please sign in.

Question

Question

Updated document on enabling SSL for Laserfiche 10?

Laserfiche Security
Updated February 20, 2018
asked on February 8, 2018 • Show version history

The old registry trick from Laserfiche 8 doesn't seem to work any longer. You can't login with or without SSL after adding it. Is there an updated document for Laserfiche 10. Just looking to encrypt the login password.

0 0

Replies

replied on February 8, 2018

We're working on a new paper. In the meantime, which product are you talking about? Just Laserfiche Server?

0 0
replied on February 9, 2018

Just for Laserfiche server, so that the passwords are encrypted when using Repository accounts or logging in from off the domain.

0 0
replied on February 9, 2018

What error do you get?

0 0
View 6 previous replies
replied on February 9, 2018

This is the error that I get

I have not done this with Version 10 yet, but just following the procedure I used for version 9. I make sure i have an SSL certificate in the personal store.

Here I am using a wildcard that matches the domain of the server and I also tried a self signed just for the heck of it.

Then I just set the SSL port under Local Machine to 443 and enable SSL under current user. I tried both localhost for the IPDatabase and the fully qualified computer name. When using localhost, tried connecting with localhost, when using the fully qualified, tried connecting with fully qualified.

Also when connecting without checking use SSL, I still get this error. 

0 0
replied on February 12, 2018

If it's self-signed, was the certificate imported into the Trusted Root Certification Authorities too so the client machine can verify it?

 

0 0
replied on February 12, 2018

Yes both the self signed and the thawte company who issued the wildcard are in the trusted root. I am not worried about trusting the server though. I would just like to encrypt the user's credentials for when they need to enter their domain information into the input fields where the "use windows auth" can't be checked.

0 0
replied on February 12, 2018

Right, but the client machine still needs to be able to verify the certificate. And the certificate needs to be both on the server and the client.

0 0
replied on February 13, 2018

I am connecting from the server directly after enabling SSL

0 0
replied on February 19, 2018

I just tested the registry key change on my machines and it works. Did you bind the certificate to port 443 on your server machine? (Step 3 here: https://weblogs.asp.net/scottgu/tip-trick-enabling-ssl-on-iis7-using-self-signed-certificates )

1 0
replied on February 20, 2018

Thanks for checking into this. I did not know that the LFS service was tied to the SSL bindings in IIS. I thought it just randomly choose from the personal store because of the requirement to put the certificate in the personal store. It was bound to the certificate but while looking at the binding I noticed the SSL certificate expired! That was the problem. I got a renewed certificate and it works now. It just never prompted me that it was denying it because of the expiration.

I found that although logging into the repository with SSL is required through the Admin Console. Users can still login using the Client without SSL. Where are the settings to require SSL for the client also?

0 0
replied on February 20, 2018

When you attach a repository, make sure "Use SSL Connection" is checked.

attach_repo_lfs_ssl.PNG
attach_repo_lfs_ssl.PNG (7.28 KB)
Download
0 0
replied on February 20, 2018

Oh yea that works good. Just wondering if there is a way we can enforce that, so they don't forget.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Attachments
Related Posts
Loading ...