OK. So, our project has been pretty much smooth sailing thus far. The integration of SAP Hybris Cloud for Customer (C4C) with our system landscape, however, was the first real challenge we came up against.
In addition to C4C, we also introduced SAP JAM as a collaboration tool. The plan was to connect both with Active Directory via SCI (SAP Cloud Identity) to allow us to use single sign-on (SSO) to access them simultaneously. And this is where we ran into rocky waters:
Due to caching and DNS problems, the JAM integration has produced mixed results depending on the browser used. This is because the SCI login URL is set as a default rather than that of JAM.
Depending on the AD version, we also encountered problems with the direct integration.
And as of today, we have not been able to fully solve point 1. The JAM integration is up and running on Microsoft Internet Explorer and/or Firefox, but not on Google Chrome and certainly not for our Mac users. I'm confident, however, that we will be able to work out a viable solution with the SAP support team at CeBIT.
For point 2, we had to take a bit of a detour through SAP Cloud Platform, which looks as follows:
At CeBIT, we will also use the opportunity to talk to SAP's support to assess how we can make the direct integration work.
For now, we have rolled out a preliminary solution here as well that we will extensively test, carefully evaluate, and surely adapt more than once over the coming weeks. So far, we have defined three work centers with separate permissions for each: inside sales, sales executive, and of course admin.
C4C comes with some 2,000 criteria that allow us to set very granular permissions for every single user. There are many items where we couldn't tell you right away whether, and if so, how they will specifically benefit the individual user. But I'm sure anyone who has ever had to configure their company vehicle knows exactly what I mean.
Conclusion: C4C is integrated with our system landscape. Systems admins are the MacGyvers of the IT industry!