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



Single Sign On with Directory server 10.3 without TLS 1.0 and 1.1

asked on September 5

Hi All,


Any has tried Directory server 10.3 Single Sign feature with ADFS Successfully. We are in the process of trying SSO initially with Web Access. But still struggling to get over it. Both are in 2 different servers, and LFDS and LFDSSTS are in the same machine. 


Every time the Directory server login happens, the below error is noted in LFDS System event log:

A fatal error occurred while creating a TLS server credential. The internal error state is 10013.

Meantime the below error is seen in WebAccess server logs:

  Message: The token XML does not appear to be valid.
Parameter name: tokenXml
  Stack trace:    at Laserfiche.SecurityTokenService.Ticket..ctor(String tokenXml)
   at Laserfiche.WebAccess.Common.ConnectionManager.AuthenticateSessionWithClaims(Session sess, RepositoryRegistration repoReg, ClaimsIdentity claimsId)
   at Laserfiche.WebAccess.Common.ConnectionManager.AutoLogon(String repoName, HttpContext context, Boolean forceLogin, WARepository waRepo)
   at Laserfiche.WebAccess.Common.ConnectionManager.<>c__DisplayClass46_0.<CheckConnectedInternal>b__1()

Certificates are installed and access to certificates also provided. Any one has configured Directory Server SSO feature with LFDS 10.3 by allowing only TLS 1.2? (TLS 1.0 and 1.1 are disabled in our environment)







0 0


replied on September 5

How did you enable TLS 1.2?  We have found that using IISCrypto works best to get the initial starting point, then follow instructions found at

Make sure to set all Servers the same.  We usually start in IISCrypto by applying "Best Practices" and then disabling all protocols except TLS 1.2.  Then we create/set the 6 registry values as directed by the KB 1013919.  Finally, we reboot the server and test.

2 0
replied on September 10

Thanks Bert for your reply!


The TLS 1.2 settings already been made in the servers related to Laserfiche, but no success till now. But have you tried this option using TLS 1.2 with LFDS 10.3?  

0 0
replied on September 6

Hi Kirubaa,

If what Bert suggested doesn't work for you, temporarily enable TLS 1.0 and 1.1 on both servers and try again. That will help verify if the issue is actually related to the TLS version

You can also try upgrading to the latest version of LFDS 10.4.x, which targets .NET 4.7.2 and thus uses TLS 1.2 by default. LFDS 10.4 is backwards compatible with other Laserfiche 10.3 components.

0 0
replied on September 10

Hi Samuel,

Thank you for the reply!

TLS 1.2 option is ruled out, as we tried this earlier. Also the ADFS \Windows authentication button also having the same issue, when going through LFDS.

I'm checking the option of Temporarily enabling the TLS version. But last option would be upgrading then.



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

Sign in to reply to this post.