[BUG] Custom SFRA session attributes are lost by PWA in phased launch setup

[vcua-mobify]

Custom attributes can be saved onto an SFRA session.

However whenever the OCAPI session bridge triggers, the session (ie. dwsid) is replaced. As a result of this, any custom attributes on the session are lost.

Plugin_slas addresses this problem by calling a special controller which transfers custom session attributes over to the new one generated by the session bridge.

PWA Kit currently does not have a similar mechanism.

Steps To Reproduce

On a phased launch store: Land on an SFRA page and add some custom attributes onto the session Navigate to the PWA - this should initiate the session handoff and trigger a session bridge Go back to SFRA and see that the custom attributes are now gone

Expected result

Custom attributes remain

Actual result

Custom attributes gone

[vcua-mobify]

In plugin_slas, the controller has access to both the old and new dwsid, as well as the methods for working with sessions which allows it to transfer session attributes. PWA Kit does not have easy access to these methods.

A solution would probably be to have PWA Kit call a controller in plugin_slas that takes in both old and new dwsid and facilitates this session attribute transfer

[echessman]

Thank you for submitting this issue. We have made significant strides in our hybrid offering and with our recent work to ensure server stickiness we do not anticipate this issue to happen as frequently. We are also working to move plugin_slas functionality to the platform. In that work we have already addressed this issue.