In our application, we use SSO (Single Sign-On) authentication. Each user can belong to multiple access groups, with one designated as primary. During the login process, we update the user's primary access group in the PostSSOAuthentication activity based on business logic or user context.

However, despite successfully updating the primary access group, the portal that launches immediately after login corresponds to the previous (original) primary access group, not the newly assigned one. The correct portal only launches on the next login, indicating that the update is persisted but not reflected in the current session.