A campaign group in SAS Customer Intelligence (to which the user group has inherited permission) generates SAS^® Marketing Optimization input data such that the user group has explicit permission instead of inherited permission. As a result, you might receive Deny permission rather than Grant permission to the input data.

This problem happens even when you have Grant permission to the campaign group. When user groups have conflicting permissions, explicit permission takes precedence over inherited permission. For more information regarding authorization rules, see Authorization Decisions.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Note: After you apply the hot fix, the following new Java argument is introduced:

This new argument -Dsas.moma.inputdata.preserve.inherited.read.deny=true enables this fix by allowing inherited permissions to be passed to the input data permission.

• In Microsoft Windows environments, the wrapper.conf file is available in the SAS-configuration-directory\Lev1\Web\WebAppServer\SASServer6_1\conf directory. In wrapper.conf, add the arguments as shown below:
  wrapper.java.additional.XX=-Dsas.moma.inputdata.preserve.inherited.read.deny=true

  Note: In the wrapper.java.additional.XX property, XX specifies the next number in the sequence that already exists in the file. Modify XX to be the next number in that sequence.

• In Linux and other UNIX operating environments, the setenv.sh file is located in the SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer6_1/bin directory.

  Add the argument to the JAVA_OPTS= property, as shown below:

  JAVA_OPTS="$JAVA_OPTS =-Dsas.moma.inputdata.preserve.inherited.read.deny=true"

Operating System and Release Information

A fix for this issue for SAS Marketing Automation 6.5 is available at: