Show Detail Frame Customizable Component Changes

Additional Oracle WebCenter Upgrade Details 16-7

16.2 Content Integration Connections: Migration of Credentials to External Applications

Content integration capabilities of Oracle WebCenter enable you to integrate decentralized content located across various content repositories, such as Oracle Content Server, Oracle Portal, or your file system, into your WebCenter applications. This section describes the authentication methods supported in Oracle WebCenter 10.1.3.x and Oracle WebCenter 11g applications. It also describes how credentials are migrated to external applications for content repository connections when you upgrade a WebCenter 10.1.3.x application. To integrate content from a content repository into your WebCenter application, you need to create a connection to the required repository. In Oracle WebCenter 11g, while creating a content repository connection, you can set the authentication method to any of the following: ■ Identity Propagation : In this method, no credentials are passed to the content repository. Instead, the repository connector uses the current users identity as determined from the Java security context. This method is generally used when the application and the content repository use the same identity store to authenticate users. ■ External Application : This method can be used in all other cases where the current user’s identity should not be propagated directly to the content repository. Table 16–4 Attribute Changes in an Upgraded WebCenter Application Containing Portlets Attribute Change in the Upgraded Application isSeededInteractionAv ailable This attribute is renamed to displayActions. The upgrade utility migrates isSeededInteractionAvailable=false|true to displayActions=onHover|always, respectively. isMinimizable This attribute is renamed to showMinimizeAction. The upgrade utility migrates isMinimizable=false|true to showMinimizeAction=none|chrome, respectively. isMaximizable This attribute is renamed to showMaximizeAction. This change is applicable only for HTML portlets. The attribute is not available for rich-text portlets. The upgrade utility migrates isMaximizable=false|true to showMaximizeAction=none|chrome, respectively. isMovable This attribute is renamed to showMoveAction. The upgrade utility migrates isMovable=False|True to showMoveAction=none|menu, respectively. contentInlineStyle This attribute is renamed to InlineStyle. text This attribute is renamed to title. portletType This attribute is removed. isLinkModeAvailable This attribute is removed. showRemoveAction This attribute is removed from an HTML portlet. In Oracle WebCenter 11g, this attribute is available only for rich-text portlets. expansionMode In JDeveloper 11g, the values allowed for this attribute are normal and minimized. In a WebCenter 10.1.3.x application, if the value is set to maximized, then the attribute is removed from the upgraded application. 16-8 Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF In Oracle WebCenter 10.1.3.x, the authentication method used for connecting to a content repository is determined through the setting specified for JAAS security. Select the Use JAAS for security checkbox if you want to transfer the user’s identity to the repository without passing the credentials and to use the trust relationship between the WebCenter application and the content repository. If you do not use JAAS security, you need to specify credentials and leave the checkbox unselected. Figure 16–1 shows the content repository connection details of a WebCenter 10.1.3.x application that does not use JAAS security. In Figure 16–1 , the Use JAAS for security checkbox is not selected and credentials are specified in the Username and Password fields. Figure 16–1 Authentication Method of a WebCenter 10.1.3.x Application If you upgrade a WebCenter 10.1.3.x application in which JAAS security is used that is, the Use JAAS for security checkbox is selected, then Identity Propagation is automatically set as the authentication method for the connection in the upgraded application. The Use JAAS for security feature is same as Identity Propagation. If the Use JAAS for security checkbox was not selected in your WebCenter 10.1.3.x application, when you upgrade the application, the authentication method is set to External Application . Further, a new external application with public credentials is created automatically by using credentials from the 10.1.3.x content repository connection. Figure 16–2 shows the content repository connection details of an upgraded application. It shows the External Application authentication method selected and a new external application created for the upgraded application. Figure 16–3 shows the public credentials automatically specified for the newly created external application.