Deploymenant Manager failing on "CheckApplicationCompliance"
I am trying to deploy a application through Deploymant Management and using the default configuration for the application validation.
It passes the first check fine, but it fails on the second check ( "Check application compliance" ). On the log errors i can only read many messages regarding invalid rule referentes regarding to ruleset name and ruleset versions that are present on the RAP. I have validated so by previewing the product file that was used in the pipeline deploy
On the log we get general errors like ( I have switch the ruleset names for anominity ):
" "taskStatus":"Resolved-Rejected" ,"errors":[ { "errorMessage":" Invalid rule reference found : Ruleset 01-01-06 , RulesetInt 01-01-01 ... " And way below there are things like:
I am trying to deploy a application through Deploymant Management and using the default configuration for the application validation.
It passes the first check fine, but it fails on the second check ( "Check application compliance" ). On the log errors i can only read many messages regarding invalid rule referentes regarding to ruleset name and ruleset versions that are present on the RAP. I have validated so by previewing the product file that was used in the pipeline deploy
On the log we get general errors like ( I have switch the ruleset names for anominity ):
" "taskStatus":"Resolved-Rejected" ,"errors":[ { "errorMessage":" Invalid rule reference found : Ruleset 01-01-06 , RulesetInt 01-01-01 ... " And way below there are things like:
{\"RuleType\":\"Rule-RuleSet-Version\",\"RuleName\":\"Ruleset 01-01-06\",\"InsKey\":\"RULE-RULESET-VERSION RULESET 01-01-06\",\"ErrorMessage\":[{\"Message\":\"Enter password that matches the password defined in the Rule-RuleSet-Name to update a Version\"}]} This error is repeated multiple times for a lot of different ruleset versions and some rulesets. Aperently at random, as there are rulesets that have the same configuration that do not apear on the log, same for versions. The rulesets are configured to use passwords to update and create versions. Am i missing some configuration on the pipeline itself? On deployment manager? I can't find anything similar on PDN posts or the Academy courses