SOA Worklisapp Login with AD Account Fails with ORABPEL-30511
(Doc ID 2920628.1)
Last updated on JANUARY 12, 2023
Applies to:
Oracle SOA Suite - Version 12.2.1.4.0 and laterInformation in this document applies to any platform.
Symptoms
On : 12.2.1.4.0 version, Workflow Service Engine
SOA WORKLISTAPP LOGIN WITH AD ACCOUNT FAILS WITH ORABPEL-30511
ERROR
-----------------------
< exception.code:30511
exception.type: ERROR
exception.severity: 2
exception.name: Verification Service cannot resolve user identity.
exception.description: User XXXXXXXX cannot be found in the identity repository.
exception.fix: Workflow Context token cannot be null in request.
ORABPEL-30511
exception.code:30511
exception.type: ERROR
exception.severity: 2
exception.name: Verification Service cannot resolve user identity.
exception.description: User XXXXXXXX cannot be found in the identity repository.
exception.fix: Workflow Context token cannot be null in request.
at oracle.bpel.services.workflow.verification.cache.local.LocalCacheManager.lookupUser(LocalCacheManager.java:639)
at oracle.bpel.services.workflow.verification.cache.local.LocalCacheManager.getBPMUserFromUserMap(LocalCacheManager.java:574)
at oracle.bpel.services.workflow.verification.impl.VerificationService.createWorkflowContext(VerificationService.java:1324)
at oracle.bpel.services.workflow.verification.impl.VerificationService.getWorkflowContext(VerificationService.java:1261)
at oracle.bpel.services.workflow.verification.impl.VerificationService.getWorkflowContext(VerificationService.java:1219)
Caused By: ORABPEL-10509
User not found.
User "XXXXXXXX" is not found in configuration "jazn.com"
Check if the user exists in the repository specified by the configurations. Check the error stack and fix the cause of the error.
Cause
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
Symptoms |
Cause |
Solution |
References |