SAP HANA Cloud Platform local runtime does not progress past login screen

[matteoprinetti]

Hi all,

I'm trying to following this https://developers.sap.com/tutorials/s4sdk-scp-neo-sample-application.html tutorial which basically boils down to this (after installing java jdk 8 and maven):

generate archetype, compile and run on local server

mvn archetype:generate -DarchetypeGroupId=com.sap.cloud.sdk.archetypes -DarchetypeArtifactId=scp-neo-javaee7 -DarchetypeVersion=RELEASE  (I used myapp as application name)
cd myapp
mvn clean install

this all goes well (I tried to deploy the .war on my Cloud Account and it works).

then I deploy to my local hana CP.

mvn scp:clean scp:push -pl application

If I browse on my pc to http://localhost:8080/myapp-application/hello I get the login screen, i enter test / test but the servlet never comes up. I can confirm test / test is working (if I enter some other username it say "authentication failed"), but basically the runtime never lets me fetch the resources.

Where is the error ? Its very easy to replicate - I tested in Windows and Linux and in both cases the scp is "stuck" at the login screen.

[mkuhr-test]

Hi Matteo, thanks for reaching out.
Is there a specific reason why you are starting with SAP Cloud Platform Neo? Generally the Cloud Foundry environment is the recommended approach as of today. The SDK also has an archetype for that. The artifact ID is "scp-cf-tomee" for tomee or "scp-cf-spring" for spring.

[matteoprinetti]

Hi Matthias, reason is we have a fairly large productive portal which is still on neo and is not going to change for a while, so we need to have the tools working.

At the moment is hosting some 60 odd SAPUi5 apps and we want to add Java Apps to it.

[sachinbr]

Hi Matteo,

I am facing same issue how did you solve this issue?

Regards,
Sachin

[tanvii_237]

Hi Matteo,

Essentially, the fix is to remove the following line from server/conf/context.xml of neo sdk:

<Valve className="com.sap.cloud.runtime.kotyo.tomcat.support.CookieValve"/>

So either you can do the fix manually or upgrade to the latest neo sdk version 1.88.x which is to be released on December 3 on Maven central, where this authentication issue in local deployment is fixed.

Best Regards,

Tanvi

[matteoprinetti]

Thank you Tanvi for the fix in the official release.

[mkuhr-test]

Until there is a solution you can work around this by commenting out the authentication parts completely in the web.xml. For local deployments this is fine, so to unblock you I would recommend that.

[matteoprinetti]

Hi Matthias workaround is working,

I just removed <security-constraint> from the XML.

[mkuhr-test]

Okay, I can reproduce the issue and am looking into a fix.