MMichau

Switching from Sandbox to Production OneSpan Account - Laserfiche Cloud Integration

-1 votes

Hello!

We has just started our production account with OneSpan for the use of OneSpan Sign, which was live as of 3/1/2023. Specifically, we had a sandbox account to test the integration with Laserfiche Cloud and I’d like to now update that workflow integration to point to our Production account instead. I’m wondering if I need to re-install a different version of the integration, or if I need to change/update some of the existing configuration. Would someone from OneSpan be able to provide some steps to change the account from sandbox to production? Or elaborate on the process so that we can begin utilizing the product within our Laserfiche Cloud system?

 

Thank you!


Reply to: Switching from Sandbox to Production OneSpan Account - Laserfiche Cloud Integration

0 votes

Hi Matt,

You don't need to reinstall the integration. You will need to regenerate the configuration file with the OSS Production account information.

Please follow these steps from the installation guide - 

6. Generate Configuration File

7. Copy Configuration file

 

Image removed.

 

Please let us know if you have more questions on this.

 

Thanks,

Moshiur Reza

 

 


Attachments
temp1.png88.26 KB

Reply to: Switching from Sandbox to Production OneSpan Account - Laserfiche Cloud Integration

0 votes

Thanks Moshiur!  To clarify - is it possible to run integrations for both the Production and Sandbox accounts at once, if I setup two distinct Remote Agents? I'm thinking of scenarios where we want to use Production for 'Live' forms and the Sandbox for testing/demoing new forms/processes. If I understand the configuration correctly, it should be possible with two distinct Remote Agent setups and two workflows (one for each Agent). 

Does this make sense? Just wanted to ask before I made too many assumptions. 

 

Thanks again!


Reply to: Switching from Sandbox to Production OneSpan Account - Laserfiche Cloud Integration

0 votes

Hi Matt,

 

The way you are thinking, does absolutely make sense.

But Unfortunately, we are supporting only one configuration as of now. So, if you really need to do back and forth between OSS accounts, you will have to  change the configurations file. 

 

In future, we will support multiple connections for Laserfiche Cloud integration.

 

Thanks,

Moshiur Reza

 

 


Reply to: Switching from Sandbox to Production OneSpan Account - Laserfiche Cloud Integration

0 votes

Hello!

I've completed the steps outlined above (steps 6 & 7 from the Configuration Guide) and I'm receiving an error when I attempt to fire the Workflow. The error states that there is an issue connecting to the Laserfiche Server. I've re-generated the Configuration file again, ensuring I used correct Credentials for both Laserfiche and OneSpan Sign. I'm not sure where else to check for incorrect settings - is there something else I can try? 

Image removed.

 

 

 

Windows Event Viewer logs:

05192023 – Admin Log

 

---Exception Details---

               A TargetInvocation exception has occurred.

                              Exception has been thrown by the target of an invocation.

                              Could not connect to the Laserfiche Server.

For more details, see the logs in windows event viewer.

 

               -----TRACES----

               Laserfiche.Scripting.Error.ScriptSourceEncodedError: A TargetInvocation exception has occurred. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Exception: Could not connect to the Laserfiche Server.

               For more details, see the logs in windows event viewer.

                  at EslConnector.LFCloud.RequestSignatureCloud.CreateTransaction(IDictionary`2 args)

                  --- End of inner exception stack trace ---

                  at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)

                  at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)

                  at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)

                  at Laserfiche.Scripting.Reflection.ScriptAssembly.InvokeMethod(String typeName, String methodName, Object[] inputs, Boolean verifySignature)

                  at Laserfiche.Scripting.Proxy.ProxyScriptExecutor.<>c__DisplayClass12_0.<InvokeWithTimeout>b__0()

                  at System.Threading.Tasks.Task`1.InnerInvoke()

                  at System.Threading.Tasks.Task.Execute()

                  --- End of inner exception stack trace ---

                  at Laserfiche.Scripting.Execution.ScriptSource.<Execute>d__10.MoveNext()

                  at Laserfiche.Scripting.Engine.ScriptEngine.<Execute>d__8.MoveNext()

               ------

               -----DATA-----

                              OperationId = b0070170b4fb498dbaf0824043f904a3

 

 

 

05222023 – Operation Log

 

5/22/2023 9:56:46 AMError message from exception - Could not connect to the Laserfiche Server. at Laserfiche.RepositoryAccess.Session.SendLogInRequest(String idnRepName, HttpCredential credentials) at Laserfiche.RepositoryAccess.Session.LoginToServer(RepositoryRegistration repository, HttpCredential credentials) at Laserfiche.RepositoryAccess.Session.LogIn(String userName, String password, RepositoryRegistration repository) at EslConnector.LFCloud.RequestSignatureCloud.CreateTransaction(IDictionary`2 args) Void SendLogInRequest(System.String, Laserfiche.HttpClient.HttpCredential) NoConnectionException


Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off