Thread Info
  • State Not Answered
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 62 replies
  • Subscribers 20 subscribers
  • Views 15503 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Connectwise Automate Feedback & Questions.

Elias Collins - Sophos Product Management

Please use this space to create a new post for issues you are having if you do not see a post already created for your issue.  We will also welcome feature functionality feedback, enhancement requests, and general questions.



This thread was automatically locked due to age.

Top Replies

  • in reply to WIlliam Nelson +3

    Just wanted to give an update on this. I think this should be something that is added to the instructions. 

    The fix was after installing the plugin through Automate, you have to go assign the Sophos Plugin user class from within Automate. 

    There are two there. "Sophos Plugin Admin" and "Sophos Plugin User". I gave myself both, but I would think you have to have the admin one to configure the plugin.

    Jump to answer
Parents
  • 0

    I just installed this plugin today and cannot get it to stay connected. I go into the settings for the plugin and put in my API key and secret and it actually does say "Connected" and in using Fiddler, it does get a successful response from the Sophos API and gives me a valid token with expire time. 

    The problem seems to be related to the DB based on the response I got from the POST to the Automate endpoint when it is trying to INSERT into "plugin_sophos_central_pld_auth". The POST responds with a -9999 code. 

    This is further shown when I click out of the settings window and go back into it, the key and secret have disappeared. So it looks like it is just not saving them.

    I opened a ticket with ConnectWise and they said I would have to get with you guys. Any help would be appreciated. Thanks.

  • 0 in reply to WIlliam Nelson

    I am having this exact same issue.  From my logs, each attempt to connect has this:

    2021-01-27T15:54:20.0970978-07:00 [1.0.0.134] Global :: Authenticating
    2021-01-27T15:54:20.9888757-07:00 [1.0.0.134] SophosService :: Authenticated and token updated
    2021-01-27T15:54:21.6708977-07:00 [1.0.0.134] SettingsViewModel :: Sophos WhoAmI api called

  • 0 in reply to Christopher Parker

    HI Christopher, 

    Could you please also validate the API credentials are generated from the Partner account and the tenant accounts are not trials?

  • 0 in reply to Elias Collins - Sophos Product Management

    I have generated the API from my master account to which the customers belong.

    Regarding temporary tenants, I have no idea about that as I have simply created the customers and never assigned anyone as temporary anything.  The only references I can find regarding tenants is in the api programming documentation which I'm definitely not messing with.

    I have confirmed again that I can create the API credentials, enter it into the sohpos central plugin, it will connect, but when I refresh the page with the refresh icon or leave the screen and return it has disconnected and will NOT reconnect again until both the pass and key have been re-entered..

    I have tested this also using api keys from a customer level as well with the same result.

Reply
  • 0 in reply to Elias Collins - Sophos Product Management

    I have generated the API from my master account to which the customers belong.

    Regarding temporary tenants, I have no idea about that as I have simply created the customers and never assigned anyone as temporary anything.  The only references I can find regarding tenants is in the api programming documentation which I'm definitely not messing with.

    I have confirmed again that I can create the API credentials, enter it into the sohpos central plugin, it will connect, but when I refresh the page with the refresh icon or leave the screen and return it has disconnected and will NOT reconnect again until both the pass and key have been re-entered..

    I have tested this also using api keys from a customer level as well with the same result.

Children