...
Maintaining multiple sessions could be cumbersome and lead to errors.
Adding prefix to routes could be extra work.
Solution 2:
Changes references like userid roles and other necessary things in existing session and portal automatically starts to use thatOnce switch profile is initiated fetch the managed user profile details. Replace the user data in session keeping the parent token as it is.
...
Things to reinitialise -
Telemetry
User profile
Update UserId in elements in indeindex.html
Proposed changes to session object.
Expand | ||
---|---|---|
| ||
|
Pros:
Simple to do.
Cons:
...
Increasing size of session data.
...
|
Pros:
Simple to do.
Cons:
Managing session data each time when profile is switched.
Session ID remains same for user and managed user profile.
Solution 3:
Things to reinitialise -
...
Storing session id and mapping it with User Id in cassandra (where portal store sessions)
Cassandra TTL might delete the other mapped data (not sure NOC team says they dont add explicit TTL currently).
Fetch user details should give details of parent if parent exists
How to do in mobile
How mobile will support offline swtich (as switch requires to generate token)parent if parent exists
How to do in mobile
How mobile will support offline swtich (as switch requires to generate token)
Conclusion
Team to follow Solution 2.
Parent’s token will be used and child’s token will not be generated.
Session data to be updated with child user profile data. Just changing the session data is required no need to change cookie and generate new session.
Re initialisation of telemetry server and user service.