Symptom
- It is not possible to load story when using proxy user in embedded SAC of SuccessFactors
Environment
- Embedded SAC in SuccessFactors
Reproducing the Issue
- Login to sucessfactors system as user A
- Go to reporting-->Can open story successfully.
- Proxy as any other user that is able to access Stories
- Go to reporting-->Open the same story
===>Loading screen will appear and story cannot be opened.
Cause
-
There are 21 JAM applications connected to your specific instance. All of these JAM applications setting cookies at the Root Domain, which is shared with the SAC Authentication Server.
The cookies being set by these applications are overwhelming the system and exceeding the maximum cookie limit accepted by the SAC Authentication Server. As a result, this is causing request failures during the access process. More than 16KB, data is sent from browser to SAC backend server. Reason is extra cookies added in browser at root domain by applications registered under ACS
Resolution
- Unless all unnecessary applications from SF ACS are removed, cookies sent from the browser will continue to exceed the limit, which will directly affect the SAC login process. So to avoid the issue, need to remove the unnecessary applications from SF ACS.
Keywords
OEM, SF, embedded, user, login , story, loading, blank , open, proxy , KBA , LOD-ANA-OEM , Embedded usage of SAP Analytics Cloud , Problem
SAP Knowledge Base Article - Public