Connector for Laserfiche 11
Thursday, September 14, 2023 at 09:46amOur Onespan integration is only with Laserfiche and we have updated the Onespan database schema after our migration to Laserfiche version 11.
We have run the installer file on our servers and created the new database schema. Still the button to edit the configuration is greyed out, and Laserfiche workflows are not connecting.
Is there anything else we should do to establish the connection?
Reply to: Connector for Laserfiche 11
Monday, September 18, 2023 at 09:25amHi Geethmi,
Sorry for the late reply! It took me some time to set up the Lasrfiche environment in my local working station.
If the "OneSpan" Configuration button is still greyed out, have you added these three Laserfiche Repository Groups:
OSS_User – The users of this group will have access to the integration Laserfiche WebAccess.
OSS_Admin – The users of this group will have access to the configuration tab of the integration UI. Which is mostly administrative actions.
OSS_All_Transactions – The users of this group will have access all the transactions of Connection Profile.
And assign at least "OSS_User" and "OSS_Admin" to your logged in Lasrefiche user?
Duo
Reply to: Connector for Laserfiche 11
Thursday, September 14, 2023 at 10:32amHi Geethmi,
Thanks for your post!
You mentioned about "migration to Laserfiche v11", are you upgrading LF from v10 to v11? Why I am asking is because we have both OneSpan Sign Laserfiche Connectors for LF v10 and v11, please make sure that you are deploying with the latest connector code.
Duo
Reply to: Connector for Laserfiche 11
Thursday, September 14, 2023 at 10:34amHi Duo,
Yes we downloaded the latest package from OneSpan website for the install. But it doesn't seem to be connecting.
Thanks
Reply to: Connector for Laserfiche 11
Thursday, September 14, 2023 at 11:01amHi Geethmi,
From your description, it sounds like a database connection issue. In the app_config.xml file, did you specify the database source name, username and encrypted password in below format, and choose to deploy the xml config in installer?
<OneSpanSignSettings>
<MSSQLServerCredential UserId="" Password="" DataSourceName="" DatabaseName="OSSInfo" />
</OneSpanSignSettings>
Among above settings:
-DataSourceName: if there's a slash in your database name, you can try to switch between back and forward slash to see if it makes any difference
-Password: use the enclosed ESLConnector.ContentEncryptor.exe to encrypt the database password
-DatabaseName: keep the value as "OSSInfo"
Duo
Reply to: Connector for Laserfiche 11
Thursday, September 14, 2023 at 11:37amHi Duo,
I believe the given format matches what we have. Please see below.
And yes, we encrypted the password using ContentEncryptor and put the encrypted value here in app_config.
When I run the installer in powershell as administrator, I didn't get any errors. Following is the message I get after I run the installer.
"Looking for workflow installation directory
Creating folder OneSpanSign for custom activity fiels under Workflow installaton directory
Copying custom activity files
Creating folder OneSpanSign for custom activity icon under C:\ProgramData\Laserfiche\
Copying custom activity icon
Completed intastallng workflow components
Installing OneSpan Sign integration for Laserfiche Workflow Ended"
I wish I had an error message to show you, but unfortunately I don't have one
Thanks
Reply to: Connector for Laserfiche 11
Thursday, September 14, 2023 at 11:46amHi Geethmi,
This configuration format looks like v10 connector to me. I will share the latest code via SFTP again and send the SFTP credentials to the email you registered in our community.
Duo
Reply to: Connector for Laserfiche 11
Thursday, September 14, 2023 at 11:47amThanks Duo! I'll be waiting for your email then.
Reply to: Connector for Laserfiche 11
Thursday, September 14, 2023 at 02:57pmHi Duo,
So we compared the file you gave vs what we had. There were no differences. However we ran the installer once again taking your files.
Still we are not getting any error messages, but the button is greyed out and Laserfiche workflow is unable.
We have installed in our test area the OneSpan integration and have create a blank OSSInfo database. Do you have any ideas on what we can do to get that button working since we need to access it to enter our Connection Profile information?
Thanks
Geethmi
Reply to: Connector for Laserfiche 11
Thursday, September 14, 2023 at 02:58pmAttached is the button status now
Reply to: Connector for Laserfiche 11
Thursday, September 14, 2023 at 03:04pmThanks for the info!
Have you got the chance to compare the app_config.xml? Below is an empty example, where the only required data is OneSpanSignSettings > MSSQLServerCredential.
<?xml version="1.0" encoding="UTF-8"?>
<config>
<destinationPaths rootPath='C:\Program Files\Laserfiche\Web Access\Web Files'>
<dllPath>bin</dllPath>
<cssPath>Assets\OneSpanSign\css</cssPath>
<jsPath>Assets\OneSpanSign\js</jsPath>
<wsPath>App_Services</wsPath>
</destinationPaths>
<laserficheConfiguration rootPath='C:\Program Files\Laserfiche\Web Access\Web Files\Config'>
<customActionsConfigFileName>CustomActions.xml</customActionsConfigFileName>
<customToolsConfigFileName>CustomTools.xml</customToolsConfigFileName>
<webAccessConfigFileName>WebAccessConfig.xml</webAccessConfigFileName>
<webAccessAppPoolName>WebAccessAppPool</webAccessAppPoolName>
</laserficheConfiguration>
<OneSpanSignSettings>
<MSSQLServerCredential UserId="" Password="" DataSourceName="" DatabaseName="OSSInfo" />
</OneSpanSignSettings>
</config>
Duo
Reply to: Connector for Laserfiche 11
Thursday, September 14, 2023 at 04:40pmWe actually did compare those. This is how the string is displayed.
<MSSQLServerCredential UserId="xxxxxxx" Password="xxxxxxxxx" DataSourceName="vlfdbtst" DatabaseName="OSSInfo" />
Thanks
Geethmi
Reply to: Connector for Laserfiche 11
Monday, September 18, 2023 at 04:31pmActually that worked! The button appeared and we were able to set up the profile.
Still the workflow doesn't seem to be connecting. Is there anything else apart from setting up these user account we should have done?
Thanks
Geethmi