In initial discussions with my client, we thought it would be simpler to let a user sign on under different identities for different roles, e.g. training module author versus training consumer. However, this does seem to present problems using session in some ways, i.e. the same user opens both author and trainee pages at the same time, but the site only stores one cookie.
How can I address the main issue here, which is the web app recognising me as one signed on (remembered) user, when I wish to sign on as another? Or do I simply make it clear to users they must always sign off one ‘persona’ before trying to use another one?
Seeing as, e.g. the two roles cites above have widely differing views presented to the user most of the time, we felt the rapidly growing complexity of continually analysing the set of roles assigned to a user, in the role model, all the time isn’t a scenario we’d like, we went with the different user model. What other models could I explore here as well?
Tell me if I got it right, but most of the time this is donde by loggin in with one identity which has different roles assigned to it.
This way you won’t need multiple identities for a single user and you’ll render html depending the roles for this identity. (for example: the highest privileged role in the identity roles collection)
If your client wants wants to stick with multiple identities then I advice using a Session Wrapper
.This way you can create your own session structure and store the logged-in roles.