Credential with Target Scope available for Patching and not for Jobs & Deployment Procedure in 12c

(Doc ID 1557425.1)

Last updated on NOVEMBER 01, 2017

Applies to:

Enterprise Manager Base Platform - Version 12.1.0.1.0 to 12.1.0.4.0 [Release 12.1]
Information in this document applies to any platform.

Symptoms

Usecase 1:

Create a Named Credential as sysman user, say namedcreds1(at target level, NOT Global) as given below:

From Cloud Control navigate to Setup > Security > Named Credential. Now click 'Create'
Here provide the 'Scope' as 'Target' and provide rest of details.

 

This credential is available during Patching. The same credential is not available for the owner during job creation or during Deployment Procedure.

Usecase 2:

Provide access to the named credential create above, say namedcreds1,  to a different Super Administrator, say admin1.
Login as admin1 and navigate to Setup > Security > named credential.
  Here you can see the named credential namedcreds1.
Navigate to Enterprise > Job > Activity.
 Click on 'OS Command' option for 'Create Job'.
   Now in Credentials tab, it does not show namedcreds1 in Preferred or as Named.

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms