EM 13c: Oracle Enterprise Manager (EM) Cloud Control Connection to My Oracle Support (MOS) Changes to Support IDCS Based OAuth
(Doc ID 2993008.1)
Last updated on DECEMBER 06, 2024
Applies to:
Enterprise Manager Base Platform - Version 13.4.0.0.0 and laterInformation in this document applies to any platform.
Details
My Oracle Support (MOS) and Automated Release Update (ARU) services are moving to IDCS OAUTH from MOD OSSO.
Enterprise Manager's connection to My Oracle Support has transitioned to a more secure, client-to-client based model utilizing a new endpoint to handle the authentication. The end user's MOS credential, along with a client credential particular to EM, is used to request a token from this authentication endpoint. EM passes the OAuth token. MOS/ARU verifies the token against OAuth end-point and also validates required access to the requested resource (e.g. MOS/ARU data). Once validated, MOS/ARU responds to EM with request resource.
The patch will restore the following functionality:
| Serial | Functionality | Navigation |
| 1 | MOS Proxy Settings | Setup -> Proxy Settings -> My Oracle Support |
| 2 | MOS Credentials | Setup -> My Oracle Support -> Set Credentials |
| 3 | Check Updates Job | Setup -> Extensibility -> Self Update -> Check Updates |
| 4 | Download Agent software | Setup -> Extensibility -> Self Update -> Agent -> select platform and Download |
| 5 | Download Plugin software | Setup -> Extensibility -> Self Update -> Plugins -> select plugin and Download |
| 6 | Patch search & download | Enterprise -> Provisioning & Patching -> Patch Updates |
| 7 | Refresh from MOS Job * | Enterprise -> Job -> Activity -> Create Job of type Refresh from MOS |
| 8 | Opatch Update Job * | Enterprise -> Job -> Activity -> Create Job of type Opatch Update |
| 9 | Download CVU * | Enterprise -> Job -> Activity -> Create Job of type Download CVU |
* Setting and applying the MOS Credentials will start and enable these reoccurring jobs
Actions
The following system patches are currently available to provide the connection fix:
EM 13.5
The correction is first included in 13.5 RU19 <Patch 35861059> Oracle Enterprise Manager 13c Release 5 Update 19 (13.5.0.19) for Oracle Management Service
See the following note for information on obtaining the latest EM 13.5 RUs
<Note:2760230.2> Enterprise Manager 13.5 Main Release Update List (Includes Plug-ins)
To apply a one-off patch for this correction, see the following, by version:
For EM 13.5 RU18:
<Patch 35722730>: Oracle Enterprise Manager 13c Release 5 Update 18 (13.5.0.18) for Oracle Management Service
AND
<Patch 35875342> : Transition from using the OAM client and backend to the IDCS client and backend
For EM 13.5 RU17:
<Patch 35460709> : Oracle Enterprise Manager 13c Release 5 Update 17 (13.5.0.17) for Oracle Management Service
AND
<Patch 35875342> : Transition from using the OAM client and backend to the IDCS client and backend
For EM 13.5 RU16:
<Patch 35437906> : Oracle Enterprise Manager 13c Release 5 Update 15 (13.5.0.16) for Oracle Management Service
AND
<Patch 35875342> : Transition from using the OAM client and backend to the IDCS client and backend
EM 13.4 Release Update:
Apply <Patch 35174911>: Oracle Enterprise Manager 13c Release 4 Update 20 (13.4.0.20) for Oracle Management Service
AND
<Patch 35875342> : Transition from using the OAM client and backend to the IDCS client and backend
See the following note for information on obtaining the latest EM 13.4 RU (note that Release Updates are cumulative):
<Note 2647078.1> Enterprise Manager 13.4 Main Release Update List (Includes Plugins)
Review the patch ReadMe for prerequisites to apply any of the patches described above.
Note:
1.To complete the installation of this patch, execute the following command from OMS server
cd $OMS_HOME/bin
$ emctl set property -sysman_pwd <sysman password> -name oracle.sysman.emSDK.core.mos.load_client_from_wallet -value true
From Console:
· Navigate to the MOS credential setting page (Setup > My Oracle Support > Set Credentials)
· Click Apply (changing the credential is not necessary)
2. Set the OMS property back to false:
cd $OMS_HOME/bin
$ emctl set property -sysman_pwd <sysman password> -name oracle.sysman.emSDK.core.mos.load_client_from_wallet -value false
Verification:
3. Ensure the URL https://login-ext.identity.oraclecloud.com:443 is accessible between EM and My Oracle Support, including through a proxy or firewall, if required,
4. Change the OMS Patching settings from Offline to Online mode
5. In the EM console, go to Setup/Proxy Settings/My Oracle Support.
Set 'Manual Proxy configuration' and specify the Proxy details, if access through a proxy is required
6. Perform a "Test Connection" and ensure it is successful/Click on Apply
Contacts
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Details |
| Actions |
| Contacts |
| References |