Fixed dconf_gnome_screensaver_idle_activation_enabled wrt RHEL7 STIG

[matejak]

• Fixed the STIG ID.
• Adjusted the timeout to the STIG value.

https://vaulted.io/library/disa-stigs-srgs/red_hat_enterprise_linux_7_security_technical_implementation_guide/V-71893?version=v2r7

[mildas]

Changes identified:
Profile stig on rhel7:
 Rule added to stig profile.
 Rule removed from stig profile.

Recommended tests to execute:
 build_product rhel7
 tests/test_suite.py profile --libvirt qemu:///system test-suite-vm --datastream build/ssg-rhel7-ds.xml stig

[ggbecker]

I think this rule is already correct. The 15 minutes delay is associated with the rule: https://github.com/ComplianceAsCode/content/blob/master/linux_os/guide/system/software/gnome/gnome_screen_locking/dconf_gnome_screensaver_idle_delay/rule.yml and the variable being used for the 15 minutes is inactivity_timeout_value=15_minutes

[matejak]

I see, there is a lock delay (short) and inactivity timeout (long).

[openshift-ci-robot]

@matejak: The following test failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
ci/prow/e2e-aws-rhcos4-moderate	b5093dd	link	/test e2e-aws-rhcos4-moderate

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[matejak]

Closing, I can confirm that this PR was based on the confusion between lock delay and idle delay.