Fiori FES logon page should use the data source/authentication from ECC backend

[former_member395548]

Hi all,

We are in process of replacing SAP portal. Very first challenge of replacing portal logon page with Fiori FES logon page. Portal is using the data source as ECC R/3 system. In current setup Fiori is integrated with SAP portal and working fine with SSO.

Now client wants the data source for Fiori logon page to be R/3(ECC backend only). So looking for advice/options - how Fiori logon page (Which is a hub deployment) can use data-source from ECC system(or authenticates against the ECC backend system)?

[BJarkowski · Accepted solution]

I'm sorry, but I don't think that's possible.

In fact, SAP NetWeaver JAVA gives you the possibility to configure external user store, but such configuration is not available in the ABAP stack. That means each user that should have access to the SAP Fiori has to be created on the Front-End server.

To make it easier you could take advantage of the SAP CUA (this way users can be created for both systems at once). Have a look here:

https://wiki.scn.sap.com/wiki/display/Basis/Central+User+Administration%28CUA%29+configuration

[Matt_Fraser · Accepted solution]

Yep, you'll recall I had a similar question not too long ago, and CUA is the way we're planning to go now. It seems like an oversight to not have this sort of capability in a "frontend" system that is intended to pass user logons through to backend systems to not have a way to set one of those backends as the "user master" in the same way you can with a Java Portal, but there it is. Whoever said SAP was logical?

[gregorw]

When you did suggested CUA to create the users in the Front-End Server you might have also an Active Directory in Place. With ADFS you can get Single Sign On to the ABAP Stack using SAML2.