This chapter describes notes on topics associated with Oracle Platform Security Services (OPSS), in the following sections:
The following documents are relevant to topics included in this chapter:
This section describes configuration issues and their workarounds. It includes the following topics:
Section 39.1.3, "Authorization Policy Manager Patch Installations Fail on 64-bit Operating Systems"
Section 39.1.4, "Some Errors/Warnings in Authorization Policy Manager Display Server Locale"
This section describes configuration issues for the Oracle Fusion Middleware Audit Framework. It contains these topics:
Section 39.1.1.1, "Configuring Auditing for Oracle Access Manager"
Section 39.1.1.2, "Audit Reports do not Display Translated Text in Certain Locales"
Although Oracle Access Manager appears as a component in Oracle Enterprise Manager Fusion Middleware Control, you cannot configure auditing for Oracle Access Manager using Fusion Middleware Control.
The standard audit reports packaged with Oracle Business Intelligence Publisher support a number of languages for administrators. Oracle Business Intelligence Publisher can start in different locales; at start-up, the administrator can specify the language of choice by setting the preferred locale in Preferences.
Due to this bug, if Oracle Business Intelligence Publisher is started on any of these 3 locales:
zh_CN (simplified chinese)
zh_TW (traditional chinese)
pt_BR (portuguese brazilian)
then users cannot see the report in that locale (the entire report including labels, headers, titles and so on appears in English), while the other locales display the translated text as expected. For example, when Oracle Business Intelligence Publisher is started in zh_CN, the text cannot be seen in zh_CN even though the preferred locale is set to zh_CN; information is displayed in English.
This issue will be fixed in a future release of Oracle Business Intelligence Publisher.
The standard audit reports packaged with Oracle Business Intelligence Publisher support a number of languages.
Due to this bug, report titles and descriptions are displayed in English even when they have been translated.
This issue will be fixed in a future release of Oracle Business Intelligence Publisher.
In 11gR1, the process that reassociates XML to LDAP stores creates a bootstrap key with the trailing new line character '\n', or its equivalent code '
'. This key value is written in the file jps-config.xml and stored in the wallet. In both places, the key value contains the trailing character '\n'.
When reusing that same wallet in 11gR1 PS1, upon retrieving the bootstrap key, the system trims out the trailing '\n' character; but the key value in the wallet, however, still contains the trailing character, a situation that leads to errors since the requested and stored key values no longer match.
To resolve this issue, proceed as follows:
Use the WLST command modifyBootStrapCredential to reprovision wallet credentials without trailing '\n'. For details on the command usage, see section 9.5.2.5 in the Oracle Fusion Middleware Security Guide.
Manually edit the file jps-config.xml and remove the trailing characters '
' from any bootstrap key.
This problem arises only in the scenario above, namely, when an 11gR1 wallet is reused in 11gR1 PS1; in particular, when reassociating in an 11gR1 PS1 environment, the above trailing character is not an issue.
To work around this issue:
In UNIX/Linux environments edit the $ORACLE_HOME/OPatch/opatch file. In Windows environments edit the %ORACLE_HOME%\OPatch\Opatch.bat file.
Locate the following string:
:CALLOPATCHNODEBUG <!--[if !supportLineBreakNewLine]--> <!--[endif]-->
Append the following boldface text to the preceding string, but be sure to include the location of your 64-bit JDK directory:
In UNIX/Linux environments:
:CALLOPATCHNODEBUG
setenv JAVA_HOME=$JAVA_HOME/bin/java -jre | - jdk $64BIT_JAVA_HOME
In Windows environments:
:CALLOPATCHNODEBUG set JAVA_HOME=%JAVA_HOME%\bin\java C:\jdk1.6.0_21\bin\java %JAVA_VM_OPTION% %JRE_MEMORY_OPTIONS%
Save the file and follow the instructions in the patch README file to install the patch.
Remove the boldface text you added in Step 3.
Save and close your file.
Errors and warnings in Authorization Policy Manager display the server locale and not the browser locale.
There is no workaround to this issue.