We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi there, I've tried using the latest version of the OpenID connect script, but I get an error from sysdig. Executing this: ./oidc_config.sh` -s -u <URL> -i sysdig -e <secret> Returns: jq: error (at :1): Cannot iterate over null (null) { "timestamp": 1549902178334, "status": 404, "error": "Not Found", "message": "Not Found", "path": "/api/admin/auth/settings" } jq: error (at :1): Cannot iterate over null (null) { "errors": [ { "reason": "Invalid request format", "message": "Can't read HTTP input." } ] }
./oidc_config.sh` -s -u <URL> -i sysdig -e <secret>
Previous version, around beginning of December, was working fine.
The text was updated successfully, but these errors were encountered:
@curionim, Pls can you let me know whether you are encountering the issue while running the script against our SaaS app or the on-premise app? If you are running the on-premise app and the version of the app is not the latest (v1586), pls use the scripts in https://github.com/draios/sysdig-cloud-scripts/releases/tag/onprem%2Fpre-1586.
Sorry, something went wrong.
No branches or pull requests
Hi there,
I've tried using the latest version of the OpenID connect script, but I get an error from sysdig.
Executing this:
./oidc_config.sh` -s -u <URL> -i sysdig -e <secret>
Returns:
jq: error (at :1): Cannot iterate over null (null)
{
"timestamp": 1549902178334,
"status": 404,
"error": "Not Found",
"message": "Not Found",
"path": "/api/admin/auth/settings"
}
jq: error (at :1): Cannot iterate over null (null)
{
"errors": [
{
"reason": "Invalid request format",
"message": "Can't read HTTP input."
}
]
}
Previous version, around beginning of December, was working fine.
The text was updated successfully, but these errors were encountered: