SAS Digital Marketing does not work with Integrated Windows Authentication (IWA).

If you implement SAS Digital Marketing in an IWA environment, you might see the following error when you work within the broadcast category of SAS^® Customer Intelligence Studio:

In addition, the SDM_Server.log file might show the following type of error:

2014-09-18 17:56:42,903 [DEBUG] com.sas.email.rmi.login.LoginImpl        - Getting SDMService for user : null. Client Type :- 1
2014-09-18 17:56:42,903 [DEBUG] com.sas.email.security.OMASecurityMgr    - Delegating the call for login to PlatformServicesUtility
2014-09-18 17:56:42,903 [DEBUG] ecurity.metadata.PlatformServicesUtility - Login Request :- UserId= null. Client type= 1. CacheApplicable= false.
2014-09-18 17:56:42,903 [INFO ] ecurity.metadata.PlatformServicesUtility - About to login using authentication service for user : null
2014-09-18 17:56:42,903 [ERROR] ecurity.metadata.PlatformServicesUtility - Login failed for user : 'null'. AuthenticationException :- Bad username or password.
2014-09-18 17:56:42,903 [ERROR] com.sas.email.security.OMASecurityMgr    - Login failed for user : 'null'. AuthenticationException :- Bad username or password.
2014-09-18 17:56:42,903 [DEBUG] ecurity.metadata.PlatformServicesUtility - Logout request received by RMI server with null user id. Ignoring it.
2014-09-18 17:56:42,903 [ERROR] com.sas.email.rmi.login.LoginImpl        - User [null@test.sas.com] denied access to the server.

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

After you apply the hot fix, make the following updates to your environment:

1. For the web application server where the sas.custintellstudio6.1.ear file is deployed (typically SASServer6), update the sem.conf file or the wrapper.conf file (or the corresponding startsrv script or .ini file, with Java arguments), as appropriate to your site. In an IWA environment, update the file by setting the following property to true:
   
   wrapper.java.additional.18=-Dsas.authentication.iwa=true

   Note: In the wrapper.java.additional.n= argument, n specifies the actual number, as appropriate to the numbering sequence in your existing file, of your wrapper argument.



2. For your SAS Digital Marketing server, update the sem.conf file or the wrapper.conf file (or the corresponding startsrv script or .ini file, with Java arguments), as appropriate to your site. In an IWA environment, set the following property to true.
   
   wrapper.java.additional.18=-Dsas.authentication.iwa=true

   Note: In the wrapper.java.additional.n= argument, n specifies the actual number, as appropriate to the numbering sequence in your existing file, of your wrapper argument.



3. If you experience any difficulties in scheduling broadcasts, set the following system properties for the SAS Digital Marketing server in the sem.conf file or the wrapper.conf file (or the corresponding startsrv script or .ini file, with Java arguments), as appropriate to your site.
   
   wrapper.java.additional.20=-Dsas.dm.schedulingUserId="user-ID" wrapper.java.additional.21=-Dsas.dm.schedulingUserPassword="password"

   Notes:

   • In these arguments, you specify the user ID and password that you use to connect the scheduler to schedule broadcasts.
   • In the wrapper.java.additional.n= argument, n specifies the actual number, as appropriate to the numbering sequence in your existing file, of your wrapper argument.

For these updates to take effect, you need to restart your system.

Operating System and Release Information

A fix for this issue for SAS Digital Marketing 6.1_M1 is available at: