A couple of assumptions/question related to ADF in Web 8+
Earlier (Tridion 2013) the claim store was living in the web server's session. Since Web 8, its location is moved to the Content Service. Is it now in the session of the Tomcat (hosted by the microservice)?
For the methods
onSessionStart, is this the request/session of the presentation server (people hitting the website) or to/on single requests towards the Content Service (the website hitting the Content Service)?
What is the lifespan of the claimstore/claims? What is the max size of the claim store (for all the users)?
The session id is used to identify a user with his respective claim store. True or false? If true, is this related to the Session cookie which ADF produces?
In a load balanced scenario with multiple Content Services, if a user is routed to a different service, how does the ADF behave? Does it detect the ID of the original service but see that there is no associated claim store for the user and:
- creates a new one with the same ID
- creates a new one and assigns a new ID, is the old ID deleted in that case?
A variant of the previous setup: In a load balanced scenario with multiple Content Services and claim processor(s) with
onSessionStart(), do you have to ensure that the user is sent to the same service? Is the assumption that otherwise those claims (session start) will not be set in a different claim store (of a different Content Service) correct?