search

packetchaos / navi

A Command-line tool which leverages the Tenable.io API to reduce the time it takes to get information that is common during remediation or a troubleshooting event
GNU General Public License v3.0
72 stars 26 forks source link

WAS 403 response #10

Closed javrav2 closed 4 years ago

javrav2 commented 4 years ago

While creating a WAS scan i am getting a 403 response while using my admin account.

You are not authorized! You need to be an admin <Response [403]>

packetchaos commented 4 years ago

Tenable just switched from V1 to V2 of the WAS products... Can you elaborate on which command you used?

Did you use the "navi was --scan myurl"?

packetchaos commented 4 years ago

I will be removing the old V1 reference in Navi this weekend...

javrav2 commented 4 years ago

Yes i used --> navi was --scan myurl

packetchaos commented 4 years ago

When did you receive the 403 error? After choosing a template? Did you get to walk through the options?

javrav2 commented 4 years ago

Yes i chose the template, selected the scanner and then selected my user which is admin. After Gave me 403 error

packetchaos commented 4 years ago

Which template did you choose? I will test it out now.

javrav2 commented 4 years ago

i chose 2 web app scan

javrav2 commented 4 years ago

awesome, thank you! Great tool by the way!

packetchaos commented 4 years ago

So I can't duplicate the error on the newest version 5.1.34.

Are you using it in a container?

packetchaos commented 4 years ago

Okay...Looks like my build process is out of sync...The container was behind. I just had the container rebuilt. So if you are using docker, pull the newest container and try it again.

If you have confirmed you are using the latest version, I would double-check that your API keys are from and admin account and that WAS is still active in your T.io. container.

packetchaos commented 4 years ago

Last...I will add a "navi version" command to make it easier to get said version. :)

javrav2 commented 4 years ago

Its working for me now :-)

packetchaos commented 4 years ago

Sweet! Sorry for the hassle. My build and package pipeline was out of sync. I will close this ticket as complete.

Let me know if you have any improvement suggestions.

Have a great day!