Skip to content
Snippets Groups Projects
  1. Jun 06, 2017
    • Jaime Pérez Crespo's avatar
      Fix a bug in the PHP session handler · ab344d88
      Jaime Pérez Crespo authored
      When unserializing the session fails, the handler should return null instead of false. Additionally, SimpleSAML_Session::load() should make sure that it got an instance of SimpleSAML_Session, to avoid any misbehaving handlers to generate an issue.
      
      This resolves #616.
  2. Apr 01, 2017
  3. Sep 27, 2016
  4. Jul 04, 2016
  5. Jul 03, 2016
  6. Jul 02, 2016
    • Jaime Pérez's avatar
      bugfix: Stop SimpleSAML_SessionHandler::newSessionId() from initializing the session. · 4056af12
      Jaime Pérez authored
      Historically, SimpleSAML_SessionHandler::newSessionId() has also created the session, sending the cookies to the browser. This is problematic both because given the name of the method one would not assume such behaviour, and also because even for transient sessions the handler would then try to set cookies. When we are using a transient session, it is likely to be because we cannot set cookies or because there was a temporary error when loading the session. If we try to set the cookies even for transient sessions, we could either get an error because cookies cannot be set, or overwrite the previous session cookies with transient ones, trashing a legitimate session in case a temporary error occurs.
      
      As a side effect, this can also cause behaviours like the one described in issue #413. There's no point in trying to set the cookies when it's not possible, so we shouldn't even try, and save us the errors.
      
      To fix this, we made SimpleSAML_SessionHandler::setCookie() abstract, forcing each extending class to implement it. The former implementation is moved to SimpleSAML_SessionHandlerCookie, and the SimpleSAML_SessionHandlerPHP gets a new method that starts the session, effectively sending the cookie. SimpleSAML_Session would then be responsible to call the setCookie() method of the session handler when creating a regular session, and skip it when creating a transient one. This introduces a bug, since SimpleSAML_Session was trying to set the auth token cookie calling the same setCookie() method in the session handler. We fixed that by using SimpleSAML\Utils\HTTP::setCookie() instead, in 8756835b.
      
      This resolves #413.
      4056af12
    • Jaime Pérez's avatar
    • Jaime Pérez's avatar
      Fix indentation. · 271be82c
      Jaime Pérez authored
      271be82c
  7. Jun 08, 2016
  8. Apr 12, 2016
  9. Apr 07, 2016
  10. Feb 15, 2016
  11. Oct 26, 2015
  12. Aug 04, 2015
  13. Jun 08, 2015
  14. May 27, 2015
  15. Apr 21, 2015
  16. Apr 16, 2015
  17. Jul 09, 2014
  18. Sep 13, 2013
  19. Sep 11, 2013
  20. Sep 05, 2013
  21. Jan 30, 2012
  22. Aug 10, 2011
  23. Aug 09, 2010
  24. Jul 13, 2010
  25. Jul 07, 2010
  26. Feb 24, 2010
  27. Feb 15, 2010
    • Olav Morken's avatar
      Disable cookie secure-flag by default. · c4ae073b
      Olav Morken authored
      This patch removes the autodetection of the secure flag for the cookie
      based on whether the user is accessing simpleSAMLphp through https. The
      reason for this is that the user can often access an SP through both
      https and http. If the user starts with http, everything will work, but
      if the user starts with https, the user will get two separate cookies,
      one for https and one for http.
      
      This patch introduces a new configuration option in config.php:
      
          /*
           * Set the secure flag in the cookie.
           *
           * Set this to TRUE if the user only accesses your service
           * through https. If the user can access the service through
           * both http and https, this must be set to FALSE.
           */
          'session.cookie.secure' => FALSE,
      
      git-svn-id: https://simplesamlphp.googlecode.com/svn/trunk@2180 44740490-163a-0410-bde0-09ae8108e29a
      c4ae073b
  28. Dec 02, 2009
  29. Sep 25, 2009
  30. Aug 14, 2009
Loading