Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 31 subscribers
  • Views 10818 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

Sophos XG Firewall: How to use API

Barb@Sophos

Hi all,

This article describes the steps how to use Sophos XG Firewall's API.

Please find more information here.

Regards,



This thread was automatically locked due to age.
Parents
  • 0

    Hi all! Is anyone else experiencing issues with authenticating to the API using the encrypted password for a user? I found a forum post from 2016 that was updated in 2017 RE: v16.05 saying that encrypted login via API won't work (https://community.sophos.com/products/xg-firewall/sophos-xg-beta-programs/v16beta/f/sfos-v16-beta-issues-bugs/79383/api-login-with-encrypted-password). I am also experiencing this but haven't found another more recent post. Does anybody know if this is still a problem in the most current release\version? I am running API v1701.1 and the "encrypted" password I get from my user export won't work, but plain text auth does.

     

    Side note: I also noticed that it appeared the encrypted password, when opened with a straight text editor like notepad, seemed to have HTML encoded characters (i.e. it ended with "4da%3D%3D" which would be "4da==" and sounds like a base64 encoded string). I tried both converting from HTML encoded and using the password that was actually included in the export and neither worked via the API.

Reply
  • 0

    Hi all! Is anyone else experiencing issues with authenticating to the API using the encrypted password for a user? I found a forum post from 2016 that was updated in 2017 RE: v16.05 saying that encrypted login via API won't work (https://community.sophos.com/products/xg-firewall/sophos-xg-beta-programs/v16beta/f/sfos-v16-beta-issues-bugs/79383/api-login-with-encrypted-password). I am also experiencing this but haven't found another more recent post. Does anybody know if this is still a problem in the most current release\version? I am running API v1701.1 and the "encrypted" password I get from my user export won't work, but plain text auth does.

     

    Side note: I also noticed that it appeared the encrypted password, when opened with a straight text editor like notepad, seemed to have HTML encoded characters (i.e. it ended with "4da%3D%3D" which would be "4da==" and sounds like a base64 encoded string). I tried both converting from HTML encoded and using the password that was actually included in the export and neither worked via the API.

Children