null,"Error":true,"Message":"The identity provider may not be configured correctly. Contact your administrator: Exception of type 'Laserfiche.LicenseManager.MismatchedSamlEncryptionSettingsException' was thrown."} ... with LFDS as a SAML provider , I would be interested in your configuration . It seems that AD FS is very particular about URL being case ......

I have configured Aptify as an Identity Provider and LaserFiche Directory Service as a Service Provider .  We are using SAML.  I followed the directions outlined ... following error is displayed:   "The identity provider may not be configured correctly. Contact your administrator: Exception of type 'Laserfiche.LicenseManager.InvalidAssertionException' was thrown."   Has anyone ......

there was information that was provided OneLogin to configure SSO on Laserfiche Cloud but not for the on-premise environment. We seem to be close ......

LFDS SAML Authentication with RSA identity provider . When the user clicks on the SAML button and then enters their credentials at the RSA login, then ... true,"Error":true,"Message":"The identity provider may not be configured correctly. Contact your administrator: ID4037: The key needed to verify the signature could not ......

step-by-step guide to configure LFDS with Microsoft EntraID.  I did followed LF Article on LFDS 10.3 SAML Authentication, but it's not ......

the following error. I am configuring a dev Okta account as a SAML idP in Directory Server. Everything was going great until I tried to ... true,"Error":true,"Message":"The identity provider may not be configured correctly.  Contact your administrator: ID4148: The Saml2SecurityToken is rejected because the SAML2:Assertion\u0027s ......

XXXX.XXXX.XXXX.com Description: Identity Provider 'XXXX.XXXX' not registered successfully. LMAdminWeb.Infrastructure.Exceptions.LMAdminWebException: Identity Provider 'XXXX.XXXX' not registered successfully. ---> Laserfiche.LicenseManager ... this an indication that this identity provider is not configured to use TLS or is there something else going on? Directory Server version 11.0 ......

step by using the Linked Identity Providers feature since we already have a few thousand users in the system. What is currently holding us back ... there a reason we are not able to only include the Laserfiche AD groups?...

SAML response. I'm also  not sure how to use anything else. If we add DisplayName, First Name, Last Name, and Department to the SAML ... LFDS. :( So this information is not useful. What am I missing?...

being able to link both Identity Providers within LFDS, but turns out I was wrong. You cannot link a SAML provider to another SAML provider ... within LFDS, regardless of which Identity Provider authenticated the user. Another fun feature request for SCIM 2.0 would be to enable "role-based" license ......

Other Claims" in LFDS under Identity Provider seems doesn't work.   Furthermore, it seems that other defined claim (such as E-mail) only synchronize when ......

MFA. We have Azure AD configured for our internal users but we would like to explore options for external users. If it's not possible ......

SSO Service URL which is not something we can provide if using IdP-initiated authentication....

related backend errors logged that may not be surfaced in the UI. ...

Mapping for the SAML Okta Identity Provider . We are unsure about the Groups mapping entry. We have changed 'LDAPDistinguished Name' to 'AD SIDS'.   Should the ......