The Caster Remote Authenticated setting in the ReportCaster Server Configuration tool may be set as follows:

• If Caster Remote Authenticated is set to NO, the ReportCaster user ID must be authenticated by typing user credentials onto a sign-on page.
• If Caster Remote Authenticated is set to YES, the ReportCaster user ID has already been authenticated remotely using Web server security, and a matching user ID exists in the ReportCaster Repository. However, there is no need to store a password in the ReportCaster Repository. This setting only works with Web-based applications.

  When Caster Remote Authenticated is set to YES, the ReportCaster determines the user identity based on the value stored by the Web server in a parameter called REMOTE_USER. This parameter is set only when the Web server is performing authentication. The REMOTE_USER parameter contains the browser Web server user ID. This may be an operating system ID or another user ID, such as an LDAP ID.

• If Caster Remote Authenticated is set to HTTP Header, ReportCaster performs sign-on integration without REMOTE_USER using the HTTP header variable specified in the Header Name setting. For more information, see the Configuring Managed Reporting for Trusted or External Authentication chapter in the WebFOCUS Security and Administration manual.

To enable Caster Remote Authentication, the following sample code may be appended to your /ibi/WebFOCUS77/webapps/webfocus/WEB-INF/web.xml file. This sample enables the use of Basic authentication for the ReportCaster user ID. It only enables administrators to access the ReportCaster Console. This is a standard J2EE container managed security sample.

<web_app>
!code
!code
!code 
!Insert the following code here right before the </web_app> tag 
<security-constraint id="SecurityConstraint_1">
         <web-resource-collection id="WebResourceCollection_1">
            <web-resource-name>console</web-resource-name>
            <description>Report Caster Console</description>
            <url-pattern>/console/*</url-pattern>
         </web-resource-collection>
         <auth-constraint id="AuthConstraint_1">
            <description>Console:+:Administrators</description>
            <role-name>Admins</role-name>
         </auth-constraint>
         <user-data-constraint id="UserDataConstraint_1">
            <transport-guarantee>NONE</transport-guarantee>
         </user-data-constraint>
      </security-constraint>
      <security-constraint id="SecurityConstraint_2">
         <web-resource-collection id="WebResourceCollection_2">
            <web-resource-name>access</web-resource-name>
            <description>regular users</description>
            <url-pattern>/servlet/DSTRCServlet/*</url-pattern>
         </web-resource-collection>
         <auth-constraint id="AuthConstraint_2">
            <description>rusers:+:regular access</description>
            <role-name>Users</role-name>
            <role-name>Admins</role-name>
         </auth-constraint>
         <user-data-constraint id="UserDataConstraint_2">

     <transport-guarantee>NONE</transport-guarantee>
         </user-data-constraint>
      </security-constraint>
<login-config id="LoginConfig_1">
         <auth-method>BASIC</auth-method>
         <realm-name>WebFOCUS</realm-name>
      </login-config>
      <security-role id="SecurityRole_1">
         <description>Regular Users</description>
         <role-name>Users</role-name>
      </security-role>
      <security-role id="SecurityRole_2">
         <description>Administrators</description>
         <role-name>Admins</role-name>
      </security-role>
</web_app>