2 Oracle Platform Security Services

This chapter describes issues and workarounds with artifacts associated with Oracle Platform Security Services (OPSS).

This chapter includes the following sections:

The following documents are relevant to the topics discussed in these notes:

2.1 WSLT Security Commands

The following sections describe issues with security WLST commands:

2.1.1 listAppRoles Command Outputs Wrong Characters

On Linux and Windows platforms, when the locale is set to non-UTF8 locales, such as the fr_FR_iso88591 locale, the listAppRoles command may output the character '?' instead of the expected character.

2.1.2 listResources Command Throws Exception

The listResources command throws an exception if the optional type argument is not specified. The workaround is to specify a value for this argument.

2.2 JNDI Connection Exception and JDK Version

JNDI Connections throw the javax.naming.NamingException: LDAP response read timed out, timeout used:-1ms exception.

This issue is found in domain configured to use an LDAP security store running on any of the following JDK versions: Java SE 6u85, 7u72, or 8u20.

Workaround

Update JDK to Java SE 6u95, 7u80, or 8u45. For certified JDK versions, see Oracle Fusion Middleware 12c Certifications at http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html.

2.3 FIPS Support Issue

Running OPSS with Federal Information Processing Standards (FIPS) compliance has a known issue that requires a patch to fix it.

Workaround

Download and apply the patch that fixes bug number 21838659 to solve the issue.

2.4 Oracle Fusion Middleware Audit Framework

The following sections describe issues with the Oracle Fusion Middleware Audit Framework:

2.4.1 Configuring Auditing for Oracle Access Manager

Although Access Manager appears as a component in Fusion Middleware Control, you cannot configure auditing for Access Manager using Fusion Middleware Control.

2.4.2 Audit Reports do not Display Translated Text in Certain Locales

The standard audit reports packaged with Oracle Business Intelligence Publisher support a number of languages. Business Intelligence Publisher can start in different locales and, at start-up, you can specify the language of choice by setting the preferred locale in Preferences.

If you started Oracle Business Intelligence Publisher on any of the locales:

  • zh_CN (simplified chinese)

  • zh_TW (traditional chinese)

  • pt_BR (portuguese brazilian)

then the entire report including labels, headers, titles shows in English.

This issue will be fixed in a future release of Business Intelligence Publisher.

2.4.3 Audit Reports Always Display in English

The standard audit reports packaged with Business Intelligence Publisher support a number of languages, but report titles and descriptions are displayed in English even when they have been translated.

This issue will be fixed in a future release of Business Intelligence Publisher.

2.5 Users and Identity Store

The following sections describe issues with identities:

2.5.1 libovdconfig.bat Does Not Support a Space in File Path

On the Microsoft Windows platform, the libovdconfig.bat script does not work if the path to your Java installation (specified with in the -jreLoc option) includes a space character, such as the C:\Program Files\Java\jdk1.7.0_21 path.

Workaround

Provide the path to your Java installation in DOS 8.3 format:

-jreloc C:\ProgramFiles\Java\jdk1.7.0_21

2.5.2 Users with Same Name in Multiple Identity Stores

If a user name is present in more than one LDAP repository and the virtualize property is set to use LibOVD, then the data in only one of those repositories is returned when you query that user name with the User and Role API.