Hello, First of all, thank you very much for this project, looks ver

'Invoke-PSTenableTokenStatus' is not recognized as the name of a cmdlet about pstenable HOT 4 CLOSED

Xyrodileas commented on June 29, 2024

'Invoke-PSTenableTokenStatus' is not recognized as the name of a cmdlet

from pstenable.

Comments (4)

vouran commented on June 29, 2024

Can confirm that we're seeing the same issue in our environment with the Get-PSTenableSeverity cmdlet.

PS C:\windows\system32> $PSVersionTable.PSVersion

Major  Minor  Build  Revision
-----  -----  -----  --------
5      1      16299  1004

from pstenable.

jwmoss commented on June 29, 2024

Sorry all! It should be resolved in 0.2.2. Let me know, I did some testing today.

from pstenable.

vouran commented on June 29, 2024

It works for us now, thanks! Different topic but is there a way to increase how long the token is available for? It seems like I need to run the connect command every couple of minutes.

from pstenable.

jwmoss commented on June 29, 2024

I don’t see any documentation around the time an API will work until expiry here - https://docs.tenable.com/sccv/api/Token.html

The code I updated should automatically check & update the token if it’s expired based on the API documentation. Let me know if that doesn’t work, and open a separate issue so I can track that.

from pstenable.

Recommend Projects