Skip to end of banner
Go to start of banner

Configuring Open-Audit with HTTPS/SSL

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

UPDATE - Open-AudIT now requires http to be accepted from localhost / 127.0.0.1. The below information is now outdated.


Tasks

If you are using https for Open-AudIT, you will need to manually edit the files /usr/local/omk/bin/open-audit_tasks.[sh|vbs]. You will need to update the URL to reflect the https prefix. To use https, there is a line below that should be un-commented, and the regular line commented out. that's all there is to it.

Default regular line

curl -s -o /dev/null --data "" "http://localhost/omk/open-audit/tasks/execute" >/dev/null 2>&1

Commented out line

# curl -s -o /dev/null  --insecure --data "" "https://localhost/omk/open-audit/tasks/execute" >/dev/null 2>&1

Config

The config option oae_server located in /usr/local/omk/conf/opCommon.nmis under the openauditenterprise section will also need to be changed. The default value for this is http://127.0.0.1/open-audit/ and changing this to https://127.0.0.1/open-audit/ will allow use of https.

After these values are changed perform a omkd restart:

service omkd restart


Discoveries

When creating a Discovery, but sure to select the https URL or if it does not appear, select Other, then manually enter the correct URL.


Independent audit scripts

If you have deployed scripts directly to devices (and are running them using cron | task scheduler) you will need to manually edit the URL paramter within the audit script and set it to use https.

  • No labels