-
Notifications
You must be signed in to change notification settings - Fork 681
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Login succeeds but later commands fail #731
Comments
Update I tried logging in again, this time supplying my token:
Now this works:
Apologies if you're supposed to always supply the token - the examples I saw used Regardless, perhaps we can make the error message clearer, either during login or while running subsequent commands. |
It doesn't work for me even when I pass the token:
Inspec version:
|
@atul86244 Which Chef Compliance version are you using? |
@atul86244 Hey Atul, just had the same issue. Mine was caused by a to short token as I just copied it from Safari... but it always ends copying with the first minus "-" sign! |
@chris-rock @cjohannsen81 I am using the latest version of Compliance ( Look at this example below:
Is this a known issue? |
@atul86244 I think it´s known as I had the same discussion with @chris-rock today :) |
Looking at this now...can authenticate with token, but then error from Compliance Server 1.3.1
|
Description
I am able to login to my Compliance server:
But
inspec compliance profiles
fails like this:InSpec and Platform Version
I am running Mac OS 10.11.3.
The text was updated successfully, but these errors were encountered: