Cognos ReportNetTM Installation and Configuration Guide
Cognos ReportNetTM Installation and Configuration Guide Cognos ReportNetTM Installation and Configuration Guide
Chapter 4: Configuring ReportNet Authorization Settings for ReportNet Users The following authorization objects are required for any ReportNet user. Some of the values shown, such as *, are default values that you may want to modify for your environment. Authorization object Field Value S_RFC Authorization check for RFC access Activity 16 Name of RCF to be protected Type of RFC object to be protected RFC1 RS_UNIFICATION, SDTX, SH3A, SU_USER, SYST, SUSO FUGR S_USER_GRP User Master Maintenance: User Groups Activity 03 Name of user group * Authorization Settings for ReportNet Administrators If users will perform administrative tasks and searches for users and roles, the following values must be added to the S_RFC authorization object in addition to the values listed above for ReportNet users. Some of the values shown, such as *, are default values that you may want to modify for your environment. Authorization object Field Value S_RFC Authorization check for RFC access Activity 16 RFC_NAME Type of RFC object to be protected PRGN_J2EE, SHSS, SOA3 FUGR Enable Single Signon Between SAP BW and ReportNet To enable single sign on between SAP BW and ReportNet, ensure that you set the following system parameters on the SAP BW server: • login/accept_sso2_ticket = 1 • login/create_sso2_ticket = 1 • login/ticket_expiration_time = 200 Configure ReportNet to Use Netegrity SiteMinder To use Netegrity SiteMinder as your authentication provider, you must configure it to protect the ReportNet portal. The users must be stored in an LDAP server or as part of an NTLM domain. Therefore, in addition to the Netegrity SiteMinder provider, you must add a corresponding LDAP or NTLM authentication provider to your configuration for each user directory. 44 Cognos ReportNet TM
Chapter 4: Configuring ReportNet Steps for Netegrity SiteMinder 1. On the computer where you installed Content Manager, open Cognos Configuration. 2. In the Explorer window, under Security, right-click Authentication, and click New resource, Namespace Type. 3. In the Name box, type a name for your authentication namespace. 4. In the Type list, click the Netegrity SiteMinder namespace and then click OK. The new authentication provider resource appears in the Explorer window, under the Authentication component. 5. In the Properties window, for the Namespace ID property, specify a unique identifier for the namespace. 6. Specify the values for all other required properties to ensure that ReportNet can locate and use your existing authentication provider. 7. In the Explorer window, under Security, Authentication, right-click the Netegrity namespace and click New resource, SiteMinder Policy Server. 8. In the Name box, type a name for the policy server and click OK. 9. In the Properties window, specify the Host property and any other property values you want to change. 10. In the Explorer window, right-click the new SiteMinder Policy Server and click New resource, User directory. Tip: Configure a user directory for each user directory in the SiteMinder policy server. 11. For each user directory, configure a corresponding LDAP or NTLM namespace. 12. If users are stored in an LDAP server, set the Use external identity property to True and the External identity mapping property to the default value. 13. In the Name box, type a name for the user directory and click OK. 14. In the Properties window, type a value for the Namespace ID reference property. Tip: Ensure that you use the same value as the Namespace ID property for the corresponding LDAP or NTLM authentication provider. 15. From the File menu, click Save. Steps for All Types of Authentication Provider Except Netegrity SiteMinder 1. On the computer where you installed Content Manager, open Cognos Configuration. 2. In the Explorer window, under Security, right-click Authentication, and click New resource, Namespace Type. 3. In the Name box, type a name for your authentication namespace. 4. In the Type list, click the appropriate namespace and then click OK. The new authentication provider resource appears in the Explorer window, under the Authentication component. 5. In the Properties window, for the Namespace ID property, specify a unique identifier for the namespace. 6. Specify the values for all other required properties to ensure that ReportNet can locate and use your existing authentication provider. 7. If you want to customize the authentication for ReportNet, specify the values for other properties. 8. From the File menu, click Save. Configure Single Signon Between ReportNet and Cognos Series 7 Products To configure single signon between ReportNet and Cognos Series 7 products, ensure that the cookie settings match. That means that the configuration properties for the cookie properties must be the same for both ReportNet and Cognos Series 7. By configuring single signon, you will not be prompted to reenter authentication information. You can then add Cognos Upfront Series 7 NewsBoxes to your ReportNet Web portal pages. Installation and Configuration Guide 45
- Page 1 and 2: COGNOS (R) ENTERPRISE BUSINESS INTE
- Page 3 and 4: Table of Contents Introduction 7 Ad
- Page 5 and 6: Chapter 10: Uninstalling Cognos Rep
- Page 7 and 8: Introduction This document is avail
- Page 9 and 10: Additional Materials In this guide,
- Page 11 and 12: Chapter 1: ReportNet Before impleme
- Page 13 and 14: Chapter 1: ReportNet Installing Rep
- Page 15 and 16: Chapter 1: ReportNet Framework Mana
- Page 17 and 18: Chapter 2: Installing ReportNet on
- Page 19 and 20: Chapter 2: Installing ReportNet on
- Page 21 and 22: Chapter 2: Installing ReportNet on
- Page 23 and 24: Chapter 2: Installing ReportNet on
- Page 25 and 26: Chapter 3: Installing ReportNet on
- Page 27 and 28: Chapter 3: Installing ReportNet on
- Page 29 and 30: Chapter 3: Installing ReportNet on
- Page 31 and 32: Chapter 3: Installing ReportNet on
- Page 33 and 34: Chapter 4: Configuring ReportNet Af
- Page 35 and 36: Chapter 4: Configuring ReportNet St
- Page 37 and 38: Chapter 4: Configuring ReportNet 3.
- Page 39 and 40: Chapter 4: Configuring ReportNet Co
- Page 41 and 42: Chapter 4: Configuring ReportNet Wh
- Page 43: Chapter 4: Configuring ReportNet Th
- Page 47 and 48: Chapter 4: Configuring ReportNet 3.
- Page 49 and 50: Chapter 4: Configuring ReportNet 4.
- Page 51 and 52: Chapter 4: Configuring ReportNet St
- Page 53 and 54: Chapter 4: Configuring ReportNet 6.
- Page 55 and 56: Chapter 4: Configuring ReportNet Ad
- Page 57 and 58: Chapter 4: Configuring ReportNet Ex
- Page 59 and 60: Chapter 4: Configuring ReportNet Sp
- Page 61 and 62: Chapter 4: Configuring ReportNet 3.
- Page 63 and 64: Chapter 5: Installing Framework Man
- Page 65 and 66: Chapter 5: Installing Framework Man
- Page 67 and 68: Chapter 6: Configuring Framework Ma
- Page 69 and 70: Chapter 6: Configuring Framework Ma
- Page 71 and 72: Chapter 6: Configuring Framework Ma
- Page 73 and 74: Chapter 6: Configuring Framework Ma
- Page 75 and 76: Chapter 6: Configuring Framework Ma
- Page 77 and 78: Chapter 7: Advanced Configuration O
- Page 79 and 80: Chapter 7: Advanced Configuration O
- Page 81 and 82: Chapter 7: Advanced Configuration O
- Page 83 and 84: Chapter 7: Advanced Configuration O
- Page 85 and 86: Chapter 7: Advanced Configuration O
- Page 87 and 88: Chapter 7: Advanced Configuration O
- Page 89 and 90: Chapter 7: Advanced Configuration O
- Page 91 and 92: Chapter 8: Setting Up the Samples Y
- Page 93 and 94: Chapter 8: Setting Up the Samples 7
Chapter 4: Configuring ReportNet<br />
Authorization Settings for ReportNet Users<br />
The following authorization objects are required for any ReportNet user. Some of the values<br />
shown, such as *, are default values that you may want to modify for your environment.<br />
Authorization object Field<br />
Value<br />
S_RFC<br />
Authorization check<br />
for RFC access<br />
Activity 16<br />
Name of RCF to be<br />
protected<br />
Type of RFC object to<br />
be protected<br />
RFC1<br />
RS_UNIFICATION,<br />
SDTX, SH3A,<br />
SU_USER, SYST,<br />
SUSO<br />
FUGR<br />
S_USER_GRP<br />
User Master<br />
Maintenance: User<br />
Groups<br />
Activity 03<br />
Name of user group *<br />
Authorization Settings for ReportNet Administrators<br />
If users will perform administrative tasks <strong>and</strong> searches for users <strong>and</strong> roles, the following values<br />
must be added to the S_RFC authorization object in addition to the values listed above for<br />
ReportNet users. Some of the values shown, such as *, are default values that you may want to<br />
modify for your environment.<br />
Authorization object Field<br />
Value<br />
S_RFC<br />
Authorization check<br />
for RFC access<br />
Activity 16<br />
RFC_NAME<br />
Type of RFC object to<br />
be protected<br />
PRGN_J2EE, SHSS,<br />
SOA3<br />
FUGR<br />
Enable Single Signon Between SAP BW <strong>and</strong> ReportNet<br />
To enable single sign on between SAP BW <strong>and</strong> ReportNet, ensure that you set the following<br />
system parameters on the SAP BW server:<br />
• login/accept_sso2_ticket = 1<br />
• login/create_sso2_ticket = 1<br />
• login/ticket_expiration_time = 200<br />
Configure ReportNet to Use Netegrity SiteMinder<br />
To use Netegrity SiteMinder as your authentication provider, you must configure it to protect the<br />
ReportNet portal. The users must be stored in an LDAP server or as part of an NTLM domain.<br />
Therefore, in addition to the Netegrity SiteMinder provider, you must add a corresponding LDAP<br />
or NTLM authentication provider to your configuration for each user directory.<br />
44 <strong>Cognos</strong> ReportNet TM