LastPass OTB Connector - Signature Error but Still Works?

Hello Friends,

We have connected our SandBox environment to our Enterprise LastPass application. We are in the process of setting it up to be utilized for Disabling accounts only (for now).

The issue present here is that at the time of testing the connection, we receive an interesting error:

“[ConnectorError] Signature is not correct”

All we are wanting to know, is what does it mean by Signature is not correct. The reason we as this is because within the connectors settings, there is no attribute that states “Signature”.

The weird part here, and really why we are asking what this means, is that we went ahead and attempted accounts and entitlement aggs on the source, even though the error was present. IT WORKED! :blush:

And this allowed us to test disabling LastPass accounts in Sandbox. And this works too! Which means it technically would work if we moved it to Prod.

However, I am weary of putting it in prod at the moment and setting up the disable piece (as that is all we need at this time) while it produces such an error in our test connection.

All in all, we would just like to know what it means by “Signature” and if there would be concern of moving it to Prod with said error or is our concern warranted?

Any and all assistance would be greatly appreciated, we believe its Token related… but we followed the process per the connector documentation and do not believe we have missed anything.

LastPass Documentation for quick reference:

https://documentation.sailpoint.com/connectors/saas/lastpass/help/SaaS_Connectivity/LastPass/Integrating_SailPoint_LastPass.html