Contents

Title and Copyright Information

Preface

- Related Documents

- Conventions

1 Known Issues and Deprecated Features

- Supported Browsers

- Known Issues

- Updating NameID/ SSO Profile Requires Import Of Metadata

- After Importing Metadata, SSO Is Disabled Automatically

- SSO Configuration Breaks

Oracle® Cloud

Known Issues for Oracle Cloud Identity and Access Management

16.3

E68445-07

August 2016

This document describes issues you might encounter when using shared identity management for Oracle Cloud services.

Oracle Cloud Known Issues for Oracle Cloud Identity and Access Management, 16.3

E68445-07

Copyright © 2015, 2016, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Preface

Known Issues for Oracle Cloud Identity Management describes the issues you might encounter with shared identity management for Oracle Cloud services.

Related Documents

There are several types of related resources available to you.

See Secure Platform Cloud Services documentation, videos, and tutorials.

Conventions

The following text conventions are used in this document.

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

1 Known Issues and Deprecated Features

This section describes issues associated with Shared Identity Management for Oracle Cloud services.

There are no deprecated features/commands in this release.

Topics:

- Supported Browsers

- Known Issues

Supported Browsers

Oracle Cloud supports the following the minimum requirements for web browsers:

Web Browser

Version

Microsoft Internet Explorer

9 or 10

Notes:

- Set Browser Mode to IE9 or IE10

- Set Document Mode to IE9 or IE10 standards

Google Chrome

29 and later

Mozilla Firefox

24 and later

Apple Safari

6

Known Issues

The following issues are present in Shared Identity Management for Oracle Cloud services.

Topics:

- Updating NameID/ SSO Profile Requires Import Of Metadata

- After Importing Metadata, SSO Is Disabled Automatically

- SSO Configuration Breaks

Updating NameID/ SSO Profile Requires Import Of Metadata

After importing partner metadata using the Self Service SSO configuration, you may run into problems updating the SSO profile or NameID mapping.

After you used MyServices > Users > SSO Confguration tab to import partner metadata, if you want to change the SSO Profile or NameID mapping, then you must re-import the partner metadata.

However, after re-importing the partner metadata, the previous settings of SSO Profile / NameID are rolled back to default values.

Workaround

The Oracle Identity Federation REST APIs support update via PUT. Use the PUT operation and update only the provided fields.

After Importing Metadata, SSO Is Disabled Automatically

When using the Self Service SSO Configuration tab, if you re-import new partner metadata, SSO is disabled automatically.

As an indication, the message SSO is disabled appears at the bottom of screen.

Whenever you upload a new configuration, you must test the new configuration before enabling SSO.

SSO Configuration Breaks

SSO configuration breaks if a corrupted identity metadata file or a new certificate file is uploaded.

Issue

The SSO Configuration may break if you:

- Uploaded a corrupted Identity Provider metadata file

- Uploaded a new Certificate file to an existing SSO Configuration

- Tried importing an Identity Provider metadata file without specifying the SingleLogout endpoint

If there is a existing SSO configuration in place, and you update the Signing Certificate, by choosing Enter identity provider metadata manually, and upload the certificate file, the SSO configuration becomes unavailable, as if there was no configuration in place.

If you have uploaded a corrupted metadata file, during the first configuration, then also the SSO configuration becomes unusable. And because you cannot update the metadata, as mentioned above, the SSO configuration cannot be reconfigured either.

Any attempt to re-create the configuration fails.

Probable Reason

When invoking the Oracle Identity Federation REST API to create or update a partner, the MyServices console sets the SigningCert or EncryptionCert to the exact content of the file, instead of converting to the Base64 encoded value of the binary certificate.

Workaround

If the certificate is PEM encoded, before you upload the file, ensure that the file does not contain either of the following lines:

-----BEGIN CERTIFICATE-----

-----END CERTIFICATE-----

If the certificate contains these lines, remove them.

If the certificate is in binary format, the MyServices console does not support uploading this format.

If you are trying to import Identity Provider metadata without specifying the SingleLogout endpoint, edit and add the SingleLogoutService element to your Identity Provider metadata.xml file and then import it.