Closed faustefan closed 4 years ago
Hi @faustefan
cool. Thanks for reporting. You can test with master branch if you like.
Best regards, Nena
Hi @nenaraab,
thanks a ton. I have run a local maven build of the java-api project based on master branch and deployed the resulting artifact with my app. It starts up just fine 👍
Thanks a ton for the quick fix. Looking forward to the patch version including it so I can bring the dependent changes to my apps code base.
Have a great day, Stefan
Solved with version 2.7.8
Dear colleagues,
during the run of Fortify on a CAP project, we were made aware that the app should migrate from
com.sap.xs2.security
tocom.sap.cloud.security
. When doing and testing the necessary changes based on your good documentation, we found the issue that the java application could no longer be started in SCP CF due to a bean initialization error.Reading the stack traces last "Caused By:" line (see below), we quickly came to the finding, that as soon as an application makes use of a XSUAA service instance with service plan
apiaccess
, the application can no longer be started. Temporarily removing the dependency to this service instance and redeploying the application made the app start up and work just as expected (besides functionality that depended on it).I then checked what adding the service plan would result in. As expected the application now started successfully when the XSUAA service instance with service plan
apiaccess
is bound (we have two instance bound with service plansapplication
andapiaccess
). You can see the small changes I did in https://github.com/faustefan/cloud-security-xsuaa-integration/commit/399338533d681ce7ef1a8836fc588d4cfb44d11b.I would ask you to take a look since I cannot judge if you are by intent not supporting the missing service plan or it is just missing. If you want, I can open a PR for the changes in above linked repo.
Thanks a ton, Stefan
Original stack trace of failing application startup: