- Aug 30, 2020
-
-
Tim van Dijen authored
-
- Aug 21, 2020
-
-
Tim van Dijen authored
-
- Dec 24, 2019
-
-
Tim van Dijen authored
-
Tim van Dijen authored
* Raise minimum PHP version to 7.0 * Remove tests pre-PHP 7.2 * Upgrade dev dependencies * Ignore tests for deprecated class * Add typehints; not touching public API * Remove none-array replacements-param; old behaviour from pre-1.4 release * Psalm fixes * Add upgrade notes * PSR-12
-
- Oct 01, 2019
-
-
Tim van Dijen authored
PSR-12 compliancy
-
- Sep 24, 2019
-
-
Jaime Pérez Crespo authored
This allows us to default to the error log, while also not breaking SSP completely. If we cannot initialize the logging handler, then we resort to the web servers log and log a critical error. This resolves #1194
-
Jaime Pérez Crespo authored
bugfix: Do not flush logs after creating a session handler, we might not have a track ID and therefore the log will be trashed.
-
Jaime Pérez Crespo authored
The new `$initializing` property should signal that we are initializing the logging handler with a value of `true`, not the other way around. Also, it should only be set to `true` while we are actually initializing the logging handler.
-
- Sep 16, 2019
-
-
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.
-
- Aug 31, 2019
-
-
Tim van Dijen authored
-
Tim van Dijen authored
-
- Aug 29, 2019
-
-
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
-
- Aug 28, 2019
-
-
Tim van Dijen authored
-
- Jun 06, 2019
-
-
Tim van Dijen authored
-
- Feb 03, 2019
-
-
Tim van Dijen authored
-
- Jan 10, 2019
-
-
Guy Halse authored
-
- Oct 17, 2018
-
-
Arno van der Vegt authored
-
- May 31, 2018
-
-
Tim van Dijen authored
-
Tim van Dijen authored
-
- May 22, 2018
-
-
Thijs Kinkhorst authored
-
- Apr 13, 2018
-
-
Matt Schwager authored
-
- Dec 08, 2017
-
-
Tim van Dijen authored
Fixes edge-case https://github.com/simplesamlphp/simplesamlphp/issues/741 where application has one of the known LoggingHandlers' name as a defined class
-
- Oct 25, 2017
-
-
Jaime Pérez Crespo authored
-
- Oct 19, 2017
-
-
fentie authored
-
- Nov 03, 2016
-
-
Jaime Pérez authored
-
- Jul 04, 2016
-
-
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.
-
- May 20, 2016
-
-
Jaime Perez Crespo authored
-
Jaime Perez Crespo authored
Fix an issue with the SimpleSAML\Logger class that was still trying to fetch the track ID from the session when running from the command line, where there's obviously no session at all.
-
- Apr 04, 2016
-
-
Jaime Perez Crespo authored
-
- Apr 01, 2016
-
-
Jaime Perez Crespo authored
Migrate all the logging handlers to namespaces. Make SimpleSAML\Logger a bit more intelligent so that it allows using custom logging handlers. Now you just need to implement SimpleSAML\Logger\LogginghandlerInterface in a class, and set the 'logging.handler' option in the configuration file to a string with the full name of your class.
-
- Mar 31, 2016
-
-
Jaime Perez Crespo authored
If we are invoked from the command line, log the messages to standard error, instead of ignoring them.
-
Jaime Perez Crespo authored
Since we allow now defering log messages while we are initializing logging, we no longer need to dump them to the error log.
-
Jaime Perez Crespo authored
Allow passing as a parameter the logging handler to use in SimpleSAML\Logger::createLoggingHandler().
-
- Feb 26, 2016
-
-
Jaime Perez Crespo authored
-
Jaime Perez Crespo authored
Move the error-reporting logic in SimpleSAML_Utilities to the SimpleSAML_Logger class, and add a new method there to evaluate whether an error would be masked or not according to its level.
-
- Nov 06, 2015
-
-
Jaime Perez Crespo authored
-
- Oct 27, 2015
-
-
Jaime Perez Crespo authored
Prevent the SimpleSAML_Logger class from creating loops while trying to get the track ID from the session. It must now be set manually by calling SimpleSAML_Logger::setTrackID(). Also allow SimpleSAML_Memcache to differentiate between a key not found in memcache and a request to memcache failed. If all servers are down, an exception is thrown and the user informed about the internal error. This hopefully resolves #264.
-
- Aug 05, 2015
-
-
Jaime Perez Crespo authored
-
- Jul 31, 2015
-
-
Jaime Perez Crespo authored
-
- Jul 08, 2014
-
-
Jaime Perez authored
Rename SimpleSAML_Session::getInstance() to SimpleSAML_Session::getSessionFromRequest(), and leave the former as deprecated.
-