About JohanBogema

Based upon the vulnerabilities reported by Compute in my Lambda function, I updated the urllib3 library in my Python3.7 function to the latest version (1.25.8), but rescanning my function still shows the old library (1.25.7). Does anyone know how I can resolve this? the function should now no longer show any vulnerabilities for urllib3, and should definitely no longer in it's inventory state it uses urllib3 v1.25.7...  ... View more

Hi,   Am trying to fetch alerts based upon an absolute timerange to ensure I don't continuously run into timeouts with my queries (want to get all open alerts for long running accounts that customers never looked at or that simply have way too many misconfigured resources). Whenever I execute the call I however keep running into 400 Bad Request statuses, and seem to be blind for my mistake. The call I'm trying to execute is the following:     curl -X POST \ '<a href="https://api2.redlock.io/v2/alert?alert.status=open&detailed=true" target="_blank">https://api2.redlock.io/v2/alert?alert.status=open&detailed=true</a>' \ -H 'Content-Type: application/json' \ -H 'Host: api2.redlock.io' \ -H 'x-redlock-auth: my-very-special-secret-auth-key' \ -d '{ "timeRange": { "type": "absolute", "value": { "startTime": 1572244614366, "endTime": 1569649014366 } } }'    When attempting it with a GET request to the below URL (of course with the x-redlock-auth header set) it also returns a 400 Bad Request. When using relative time of 1 month it just works as expected.   <a href="https://api2.redlock.io/v2/alert?alert.status=open&timeType=absolute&startTime=1572244614366&endTime=1569649014366&detailed=true" target="_blank">https://api2.redlock.io/v2/alert?alert.status=open&timeType=absolute&startTime=1572244614366&endTime=1569649014366&detailed=true</a>     Regards ... View more

When adding a device I receive an empty error message in the UI as shown below   In the Apache error.log I see the following message appear:   PHP Fatal error:  Uncaught PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'avoidToday' in 'field list' in /var/www/html/libs/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOConnection.php:77\nStack trace:\n#0 /var/www/html/libs/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOConnection.php(77): PDO->prepare('insert into `de...', Array)\n#1 /var/www/html/libs/vendor/illuminate/database/Connection.php(452): Doctrine\\DBAL\\Driver\\PDOConnection->prepare('insert into `de...')\n#2 /var/www/html/libs/vendor/illuminate/database/Connection.php(657): Illuminate\\Database\\Connection->Illuminate\\Database\\{closure}('insert into `de...', Array)\n#3 /var/www/html/libs/vendor/illuminate/database/Connection.php(624): Illuminate\\Database\\Connection->runQueryCallback('insert into `de...', Array, Object(Closure))\n#4 /var/www/html/libs/vendor/illuminate/database/Connection.php(459): Illuminate\\Database\\Connection->run('insert into `de...', Array, Object(Closure))\n#5 /var/www/html/libs/vendor/illuminate/database/Connection.php(411) in /var/www/html/libs/vendor/illuminate/database/Connection.php on line 664, referer: https://172.16.11.129/   Is this a known issue for the 1.0.90 build? The only "strange" thing about the device is that it's accessible on a different port than 443. ... View more

Hi all,   Does anybody have an idea why the following happens, and what the solution might be?   I'm trying to perform a commit-all via the REST API using the the following URL: https://panorama.domain/api/?REST_API_TOKEN=hash&type=commit&action=all&cmd=<commit-all><shared-policy><device-group>"Group-Name"</device-group></shared-policy></commit-all>   I get the following response even though the name of the device-group is correct:   <response status="error" code="17"> <msg> <line> commit-all -> shared-policy -> device-group has unexpected text. </line> <line> commit-all -> shared-policy -> device-group is invalid </line> </msg> </response>   ... View more