Skip to content
Snippets Groups Projects
  1. Mar 12, 2021
  2. Jan 22, 2021
  3. Sep 15, 2020
  4. Sep 10, 2020
  5. Jun 13, 2020
  6. Apr 30, 2020
  7. Feb 15, 2020
  8. Feb 14, 2020
  9. Dec 24, 2019
  10. Oct 01, 2019
  11. Sep 24, 2019
  12. Sep 16, 2019
    • Jaime Pérez Crespo's avatar
      Remove superfluous log message · 512b9cf3
      Jaime Pérez Crespo authored
      If we reach this point, we're likely already logging the error somewhere else (i.e. the session handler in use), so there's no point on logging the exception's message again.
      512b9cf3
  13. Aug 31, 2019
  14. Aug 29, 2019
    • Jaime Pérez Crespo's avatar
      Make sure we respect log message order · 014992c8
      Jaime Pérez Crespo authored
      When we are logging something and the logger hasn't been initialized, the messages are deferred and flushed by a shutdown handler. However, when we initialize a session, we set the track ID in the logger, effectively initializing it with everything we need. When we log something and then load the session (or create it), any subsequent logs will be dumped, but the deferred logs will wait until shutdown, changing the order in which they were emitted.
      
      This patch makes sure we flush the deferred logs as soon as we have a track ID (can either be set manually or by, most typically, loading a session). That way, we get those logs out as soon as we can, and subsequent logs entries will be dumped afterwards, keeping their relative order.
      
      This closes #1107
      014992c8
  15. Aug 28, 2019
  16. Jun 06, 2019
  17. Feb 03, 2019
  18. Jan 10, 2019
  19. Oct 17, 2018
  20. May 31, 2018
  21. May 22, 2018
  22. Apr 13, 2018
  23. Dec 08, 2017
  24. Oct 25, 2017
  25. Oct 19, 2017
  26. Nov 03, 2016
  27. Jul 04, 2016
    • Jaime Pérez's avatar
      bugfix: Make sure SimpleSAML_Session::getSessionFromRequest() always raises an... · 52c6bf04
      Jaime Pérez authored
      bugfix: Make sure SimpleSAML_Session::getSessionFromRequest() always raises an exception when a transient session is used due to a misconfiguration or a temporary failure fetching an existing session.
      
      Transient sessions are just an exceptional event, and they shouldn't be treated as regular sessions. Therefore, if we are trying to get the current session and end up with a transient one, that's because an error occurred and we should raise an exception. Since exceptions due to secure cookies trying to be set via an insecure channel are likely to be misconfigurations, we treat them like that, raising a SimpleSAML\Error\CriticalConfigurationError.
      
      Additionally, we capture exceptions in the SimpleSAML\Logger::flush() method, ensuring the error reported in #413 doesn't happen again.
      
      This resolves #356.
      52c6bf04
  28. May 20, 2016
  29. Apr 04, 2016
  30. Apr 01, 2016
  31. Mar 31, 2016
Loading