Hi Martin,
thanks for the answer.
Well, the idea was that the users would not be simultaneously connected to the Internet and the corporate network. If they were connected securely to the corporate network, they could the run the application on premise firsthand.
With SAML and FORM authentication, the form comes directly from the IdP, which needs thus to be accessible from the users browser, if I understand things right (Not sure however, how this would work with BASIC authentication).
IDS seems not to be practical for this, esp. as currently the user name from the IdP and the user name in the backend systems needs to be identical.
And the point with all those federation systems, if there is not already one in place, having to set it up would be significantly more hassle than to order a HANA Cloud Account and deploy an application there.
Please do not understand me wrong, it is nice that you use that open standard SAML and open up those various options, but I think a KISS solution for adding a SAP HANA Cloud application to a running ABAP stack seems to be in need. Couldn't eg the SCC also include a "mini" IdP authenticating to an ABAP stack via RFC calls?
Regards,
Wolfgang
