After completing the upgrade to OTK 4.x, the "auth/oauth/v2/authorize" policy we see an assertion that states "Code not available for assertion: CustomAssertion" for the "Check Response Type Supported" assertion.
What do we need to do to fix that?
Release : 9.4
Component : API GATEWAY
If you see this problem ensure once you have performed an upgrade that you have restarted the ssg services.
To restart SSG services;
SSH to your gateway.
Login as ssgconfig.
choose option 3
3) Privlieged shell
# service ssg restart
Once ssg services have restarted then login to policy manager again and validate if the /authorize endpoint now has resolved the "custom assertion is not available"
If the above does not fix this,
The assertion can be recreated by re-installing OTK, or can migrated moved by exporting and importing the encapsulated assertion from other gateway with same OTK version.