Enterprise portal problem after chrome 115/116

[former_member280870]

Hi

We are running Enterprise portal 7.5 SP24

After Chrome 115 (and still in 116) we are facing problems with opening OBN navigation from a WDA , sizing of iViews with WDA of KM Navigation, eventing between applications.

Are anyone facing similar issues?

Thanks

/Jakob

[former_member559196]

Hello Jakob,

Yes! We've had similar issues with ESS links not calling when selected (chrome 115/116). Firefox seems to work ok though. Haven't yet found a solution

[Cassy_Slaven1]

Same here. ESS links not opening. Firefox and Edge are fine. Still looking for a solution because it is random. Some users have no problem, but others do.

[nstrik]

We are having a similar issue as well. Started last week. Using Chrome, when a user clicks links in ESS on the enterprise portal, nothing happens, links don't work. Similar to others on this thread, this is not impacting all users, just some which is odd. Works with Edge so that is our solution at this point, but many users want to use Chrome which has worked up to this point.

[nstrik]

Does anyone know why this issue would only affect some users and not others? We have users on the same version of Chrome, where some are affected and others not. Just curious why is would only impact some users.

[former_member666464]

This is the exact issue we are having. It started at the end of August and we now have 8 people reporting the problem. We have told anyone experiencing this to use Edge as a workaround. We cannot reproduce the issue and have gone through a list of possible causes from versions, settings, updates, old equipment etc. My worry is if Edge starts to have the same problem.

[khigby]

We are having the same issue. On August 31, I tested on my own device and the links in ESS were working fine for me on Chrome version 116.0.5845.140. When I checked my version to record it, I noticed there was a pending update. After applying the update to version 116.0.5845.141 I tested again and the links in ESS no longer worked for me.

This gave me some confidence that it was an issue with a Chrome patch, although we had cases where users on the same version and patch level of Chrome had different results (some had the issue, some did not).

I downloaded the beta version of Chrome 117 and it was working fine for me, but just yesterday Chrome 117 was released in the stable channel and upgrading to it did not fix my issue, even after clearing the User Data folder.

...

Has anyone found a solution to this other than directing users to Edge?

[former_member559196 · Accepted solution]

Setting this may provide resolution:

chrome://flags/#origin-agent-cluster-default set to DISABLED

[jorjey163 · Accepted solution]

It works.

thanks.

[arvindhoshiar · Accepted solution]

Thanks Mr Cooper

Resolved at the movement

[khigby · Accepted solution]

Works for me as well.

[laxmikanth_karunamoorthy · Accepted solution]

Working fine, when manually we do the above settings. Kindly help us for permanent solution on this regard.
[ There will be Multiple End users. we cont. say them to do this settings manually ]

[EduardoGzz]

Check if it is related to note 3159245. We implemented the solution proposed and it resolved the issue.

Thank you

[former_member559196]

Hello Eduardo,

Can you tell me which solution you implemented? I see two options listed on that note

thanks

Brian

[EduardoGzz]

In our case it was 1831525 in our Portals, along with ABAP notes 3154411, 3163365, 3161114, 3194092; for ABAP it will depend on your system patch levels so I would start with 1831525.

We looked at changes to the browser but that would require us to do a company wide policy to deploy to all users; also since the problem was Chrome only, it would be just a matter of time before it makes it to Edge, being it is chromium based.

Hope that helps.

Eduardo

[nstrik]

Our BASIS team also implemented option 2 in note 1831525 and based on our initial testing, it seems to be working for us as well.

[Steve_S1]

I believe this should be the Best Answer. As this is not just a Chrome issue.
We used 3159245 Option 2, our ABAP Sytems are already at a high enough patch level.
So, we just needed to implement 1831525 in our Portal Systems and that fixed the issue while using Chrome.

MS will disable "document.domain" in Edge 118.
https://learn.microsoft.com/en-us/deployedge/edge-learnmore-origin-keyed-agent-cluster

Link to Edge Release dates (118 released on week of 12-Oct-2023)
https://learn.microsoft.com/en-us/deployedge/microsoft-edge-release-schedule#microsoft-edge-releases

Steve

[former_member280870]

Hi

We have tested the group policy in the note mentioned

https://chromeenterprise.google/policies/#OriginAgentClusterDefaultEnabled

And that seems to solve the problem for the users who previously had problems

chrome://flags/#origin-agent-cluster-default

[jjee]

hi all,

We are facing exactily same issue with OBN navigation in chrome(115,116)

Edge is fine but users want to use chrome.

If anyone knows how to solve that, please leave here.

thanks.

[jorjey163]

Now I switched to Microsoft edge but I prefer to use google chrome.

[former_member280870]

Hi

Yeah that works for us as well, but for how long since Chrome/Edge are built on the same engine

/Jakob

[former_member280870]

Hi Brian

I'll update here when we find a solution, please do the same

/Jakob