From a5a27827a636e36365f72f4768465c08a69351d5 Mon Sep 17 00:00:00 2001 From: Lance Bragstad Date: Wed, 21 Feb 2024 14:26:33 -0600 Subject: [PATCH] Fix invalid number usage in oauth variable Recent changes to the oauth token maxage variable introduced it as a number instead of a string or integer, which SCAP is expecting. This commit updates the variable to be a string instead of a number type, so that the resulting datastream is valid and parsable by the compliance oeprator profile parsers. Without this change, content from the latest branch will cause the compliance operator installs to hang because it can't parse the xccdf. --- .../openshift/authentication/var_oauth_token_maxage.var | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/applications/openshift/authentication/var_oauth_token_maxage.var b/applications/openshift/authentication/var_oauth_token_maxage.var index 9f52243ab43..4733ea17aee 100644 --- a/applications/openshift/authentication/var_oauth_token_maxage.var +++ b/applications/openshift/authentication/var_oauth_token_maxage.var @@ -4,7 +4,7 @@ title: 'OAuth Token Maximum Age' description: 'Enter OAuth Token Maximum Age Timeout' -type: number +type: string operator: equals