Error 'invalid Orchestration Strategy' When Creating An OAM 11g Custom Authentication Module
Last updated on MARCH 08, 2017
Applies to:Oracle Access Manager - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
Error 'Invalid Orchestration Strategy' is occurring when trying to create an Oracle Access Manager (OAM) 220.127.116.11 Custom Authentication Module in their production environment .
The error occurs after creating the Steps and specifying the Orchestration Steps, when the Apply button is clicked.
Steps to reproduce
1. Create a new custom authentication module with name 'test'.
2. Click on the Steps tab and use the + icon to create two steps with e.g. X509CredentialExtractor and UserIdentificationPlugin plugins respectively. No changes made to the default parameters for those steps.
3. Click the Steps Orchestration tab and configure:
Step 1 -> On Success -> Step 2 -> On Failure -> failure
Step 2 -> On Success -> success -> On Failure -> failure
4. Click Apply: get error popup "Invalid Orchestration Strategy."
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