Unable to login to OAuth Manager after upgrade from OTK
search cancel

Unable to login to OAuth Manager after upgrade from OTK


Article ID: 234091


Updated On:


CA API Gateway


After upgrading OTK 4.2 to 4.4.1, and following all Broadcom documentation, we are no longer able to log in to the OAuth Manager.


The installation appears to be perfectly clean and the JDBC connection test works fine using the OAuth connection but the log shows this error:

REQUESTID:0000017e77de9190-483 oauth/manager [/oauth/manager]: 11000: Policy processing caught an exception: RaiseErrorAssertion is stopping execution.
2022-01-20T14:54:54.644+0000 WARNING 756 com.l7tech.server.message: AUDITLOG: INFO: PROJECT:: REQUESTID:0000017e77de9190-483 oauth/manager [/oauth/manager]: Message was not processed: Assertion Falsified (600)



Release : 10.0

Component : Gateway


After the upgrade, the OAuth manager failed because it could not find the otk-related cluster-wide properties. 

These properties are introduced in OAuth 4.4.1  and are installed by the subcomponent "OTK Configuration". See the screenshot below.

Make sure this component is selected during the upgrade from 4.4 to 4.4.1 or during the upgrade from 4.2.to 4.4.1 or from any otk release before including 4.4 to 4.5.x and 4.6

Screenshot OTK 4.4.1 Solution Kit (Example):