Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Identity Management (MOSC)

OAM 12.2.1.3 aaa_key creation is issue, How to remediate it?

Sep 11, 2020 5:04PM edited Sep 17, 2020 11:00AM in Identity Management (MOSC) 13 commentsAnswered

OAM12.2.1.3 with jdk1.8.xxx on RHEL 7.x

Artifacts creation with aaa_key do not have below

-----BEGIN RSA PRIVATE KEY-----

Proc-Type: 4,ENCRYPTED -- Missing

DEK-Info: DES-CBC,28A74A6B77AD0751

--Missing

Any suggestions what it could be and how to remediate it?

Thank you in advance.

Rajive

Tagged:

0

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

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

Category Leaderboard

Top contributors this month