If you’ve found some SAP approval buttons are no longer working in Chrome the issue may be down to a feature implemented in Chrome 88 but only enabled by default in recent versions of Chrome (versions 115 and 116)
The origin-agent-cluster header isn’t a security feature but a http header (for browsers that support the origin-agent-cluster feature/flag) that web developers can implement to change the default behaviour for a web page, putting it into an origin keyed agent cluster so that it is grouped with other pages that have the exact same origin
Same site but cross origin pages will then be excluded from the agent cluster. Your browser will then decide (if it has the origin-agent-cluster-default enabled and if your device has enough resources) to allocate same site but cross origin pages their own process or seperate threads
This can benefit web based applications such as video conferencing or other web based applications that can be resource intensive so each “instance” of a cross origin page don’t impact another cross origin page running in the same browser
If you’re affected by the SAP approval issue, depending on what you use SAP for in your organisation you’ll find you’re no longer able to approve items like invoices, expenses, holidays etc.
No error messages appear when you click on the buttons normally used to approve the above, they just seem to be completely unresponsive in Chrome versions 115 and 116
Try disabling the chrome://flags/#origin-agent-cluster-default flag in Chome and restarting your browser and this will most likely resolve your issue
You may need to go back and disable the chrome://flags/#origin-agent-cluster-default flag later if Chrome is updated in the future (I can’t confirm this as I already have the latest version of Chrome installed)
I found the workaround for the issue here but it wasn’t very well documented https://answers.sap.com/questions/13949753/enterprise-portal-problem-after-chrome-115116.html
More information here: https://web.dev/origin-agent-cluster/#when-to-use-origin-keyed-agent-clusters
Edge has yet to enable its equivalent edge://flags/#origin-agent-cluster-default flag by default so Edge can be used as an alternative browser if you don’t want to disable the chrome://flags/#origin-agent-cluster-default flag in Chrome
Here’s a related Oracle Enterprise issue
