What happened when I landed Saiku.
Approximate process
Saiku Default has admin and two developer identity when landing Saiku, the background user authentication successfully created the user information session and stored in the session a randomly generated SessionID this is a unique identity ID for each user and then access /saiku/rest/saiku/session - Get interface Gets the stored SessionID if you get the SessionID, start building the Saiku home page.
/saiku/rest/saiku/User Account/discover
Detailed process
1. Visit/saiku/rest/saiku/info
2. Visit/saiku/rest/saiku/ui-settings
3. Access/saiku/rest/saiku/session [GET] not logged in, no SessionID, execute new loginform () Operation Create Login window
Click the [Login] button
4. Access/saiku/rest/saiku/session [POST] with user name password for user authentication [Sessionresource-login]
User information is written to session, especially SessionID, after successful verification
5. Execute Response.ok (). Build () Return request page [this is/saiku/rest/saiku/session [GET]]
6. At this time by accessing the/saiku/rest/saiku/session [get] will be able to get to the writing session to obtain the user information
7. After verification, access to the/saiku/rest/saiku/user name/discover interface to obtain a user's cube and a series of information
Note: The LoginForm login window is always created if the user's SessionID information is not available through getsession
Two choices and what happens when you switch the cube
with browser tracking, it is found that when Cube is selected, the Saiku server randomly generates an ID string that is unique when used for interaction. If another cube is selected and a request is resubmitted, Saiku will automatically delete the original ID string and regenerate an ID string as a new query. http://ip:port/saiku/rest/saiku/login account/query/4ff7d01e-8a6b-5eb4-991b-c0ce680a4bca/result/flat Where: 4ff7d01e-8A6B-5EB4-991B-C0CE680A4BCA is the interaction ID
Saiku-What happens when I log in/select Cube