Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Correct me if I am wrong, but I think there is finally no way to do what I am trying to since Chrome (and I think FF too) save the exact cookie and are able to restore the session skiping all LoginHandler methods.</p> <p>Let me explain myself.</p> <p>Right, I was about (and actually I did) to implement the solution described in your answers and comments:</p> <ol> <li>User X enters the web site with his login/password using Safari (for example)</li> <li>The login datetime is stored both in table <code>User</code> in the database and in session</li> <li>Without logging out, the same User X opens a different browser (Chrome, for example)</li> <li>The new login datetime is updated in database and in Firefox session</li> <li>The user gets back to Safari and tries to refresh the page</li> <li>He gets an exception as the datetime doesn't coincide with the one stored in session</li> </ol> <p>Well... great so far, as it seems to solve the problem.</p> <p>And here comes the big deal: as described <a href="https://stackoverflow.com/questions/10617954/chrome-doesnt-delete-session-cookies">here</a> and <a href="https://groups.google.com/a/chromium.org/forum/?fromgroups=#!topic/chromium-bugs/cjt3WwgOJ3c" rel="nofollow noreferrer">here</a>, Chrome is not deleting properly the session cookies. So when user doesn't logs out and just close the browser, anytime he or she comes back to Chrome, the session is automatically restored without passing through a login handler, login method or anything around.</p> <p>This causes that "magical" datetime key not to be saved both in database and session and, as a result, put a stick in the wheel of letting just one session as a time, what was the original plan.</p> <p>Any more light on the issue??</p> <p>I want to cry :(</p>
    singulars
    1. This table or related slice is empty.
    1. POFOSUserBundle - Unique session access
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USElPiter
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COAs I said you should also implement your own [Voter](http://symfony.com/doc/current/cookbook/security/voters.html) that will take care of these datetime comparisons. Whenever comparison fails (5-6 in your example), you log out the user (see ["Symfony2: how to log user out manually in controller?"](http://stackoverflow.com/a/6474975/1337344)) and `return VoterInterface::ACCESS_DENIED;`. See the documentation for more information on security and how to implement a custom voter.
      singulars
      1. PO
      1. USiamdto
    2. COThanks, I understood it well. But, please, read from the point where I begin "And here comes the big deal". Really, I understand how to make that comparisons (even without Voter framework (although I'll take a look at it)), but the problem is, as I said, that I will never be able to intercept the session creation as it is not created indeed, but just recovered and not passing through any "LoginHandler" or Login method or anything like that. May be I am really missing something, but I don't get it. I'll take a look to Voter, but according to what you said, I don't think it will solve.
      singulars
      1. PO
      1. USElPiter
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload