I've an application built with Experience Builder we're hosting on https://example.com/exb. It is served and supported by an ASP.NET Core backend. ASP.NET Core provides custom rest endpoints for our SPA (https://example.com/exb/api) as well as authentication.
The ASP.NET Core backend is configured for OAuth against ArcGIS Portal. No content can be loaded unless the user has authenticated, including the JavaScript files that comprise the ExB app. That is, when an unauthenticated user opens https://example.com/exb ASP.NET begins an a OAuth flow against ArcGIS Portal. Once signed in, ASP.NET returns a cookie that is required for all future requests to https://example.com/exb and child paths.
The access and refresh tokens one obtains from the OAuth flow with portal are embedded in the cookie.
How can I initialize SessionManager/IdentityManager in the ExB app with an already signed in user. We don't want them to have a secondary OAuth flow and should be able to use the existing info we obtain from the initial login.
