Just few thoughts - may be little advanced/off topic if you read it a portal standpoint (for readers who are familiar with dynamic client registration it will be simple)
How are you on-boarding the apps?
Why not think little creative on building a proxy which does the on-boarding using apigee management api's (it's 1 time effort)- https://apidocs.apigee.com/apis (your focus will be creating developer & app specific api's) & use simple java callout to alert.. In simple terms it is called dynamic client registration following this https://datatracker.ietf.org/doc/html/rfc7591#section-3.1
1. Start with api contract for on-boarding clients ( what's the request will look like what all meta data you will require to be get added to the developer/app & what response you want once the app is created ,follow standard error framework which you may have for failures)
2.Develop a proxy based of contract & follow below process (have the proxy on high security profile- use mTLS + OAuth as app's are generating using api's).
- Do a check to validate if developer is already on-boarded or not
- If developer doesn't exists just create developer
- If developer exists check if app is already on-boarded
- If app already exists just throw error (since it already exists & trying register again)
- if app doesn't exists then go ahead and create app
- once onboard gets completed you can simply use email alerting mechanism (using simple java call-out)..
LinkedIn
Twitter
