Connect Secure ( CNS) Changing their installer to add a "User Secret"

Software, Tasks & Script Requests
1

https://cybercns.atlassian.net/wiki/spaces/CVB/pages/2103410891/How+To+Install+ConnectSecure+V4+Agent

I know y’all just built out an integration on this, and come September 1st they are changing their agent installation to add a user secret to the installer. Not sure if you guys were aware of this, so I wanted to give you a heads up.

2

@DimitriRodis
Maybe your new integration takes this into account, but wanted to give you a heads up anyhow.

3

I’d just have to check to see if I had that in there. Should be an easy fix (if not) though as long as we can get that param value with their API.

1 Like
4

if you need a guinea pig, hit me up :slight_smile:

5

Any update on this? Just trying to see when I can get the integration working again. Thanks.

6

Would also like some info on this one. The user secret isn’t unique in any way, so it looks like it could also just be added as a required variable for the integration, and then added to the script.

7

Hi,

I believe the addition of the user secret to the integration and functions related to connect secure has caused problems deploying the agent.

The connectsecure agent was working but now isn’t for us. Looks like the module/integration and install scripts were updated 4 days ago according to the history in the script editor.

8

Any update on this one?
Broken for us as well.
Thanks

9

:bulb: Note

The ConnectSecure integration has been updated to use user_secret. Some instances are not having the update reflected until the integration type is manually refreshed. You can navigate to Show More > Integrations and click Reload integration types. After that, reload your ConnectSecure integration as well, and the user_secret should be present.