Skip to content
Snippets Groups Projects
  1. Apr 18, 2018
  2. Feb 21, 2018
  3. Dec 29, 2017
  4. Nov 29, 2017
  5. Oct 19, 2017
  6. Oct 10, 2017
  7. Sep 07, 2017
  8. Aug 31, 2017
  9. Aug 14, 2017
    • Jan de Mooij's avatar
      Make POST template compatible with CSP (#635) · 9c49e503
      Jan de Mooij authored
      See issue #593 for a problem description.
      SimpleSamlPHP makes use of unsafe inline Javascript and CSS elements.
      Although most generated HTML uses SimpleSamlPHP's own headers, the
      keepPost option in an authentication request uses the headers of
      the PHP application it is sent from. This forces web applications
      using SimpleSamlPHP to allow 'unsafe-inline' in their Content
      Security Policy.
      
      This commit fixes this issue for the keepPost page ''only'', to
      allow PHP applications using SimpleSamlPHP to use a more strict
      Content Security Policy. This does not take away from possible
      XSS vulnerabilities in other parts of SimpleSamlPHP.
      9c49e503
  10. Aug 09, 2017
  11. May 24, 2017
  12. Dec 05, 2016
  13. Oct 03, 2016
  14. Sep 15, 2016
  15. Aug 23, 2016
  16. Aug 22, 2016
  17. Aug 16, 2016
  18. Aug 15, 2016
  19. Jul 26, 2016
    • Jaime Pérez's avatar
      Bump the version of the SAML2 library. · b02c5432
      Jaime Pérez authored
      Now we are finally using the 2.x branch of the SAML2 library, which was also migrated to use namespaces. Even though the library provides an autoloader that allows loading the classes with the old names using class aliasing, we need to do the migration in one commit (at least for most part of it). This is due to the way SimpleSAMLphp checks data types, using inheritance to check objects agains abstract or more general classes. Even though class aliasing works, there's no way to replicate those relationships, and type checks that use the old class names will fail because the aliases are virtually new classes that don't inherit from others.
      b02c5432
  20. Jul 19, 2016
    • Jaime Pérez's avatar
      Do not enforce reading the configuration from files. · 8eaf60b1
      Jaime Pérez authored
      The www/_include.php script, included by all scripts in www/, checks unconditionally for the existence of the config.php file. However, this prevents us from testing the scripts automatically. Instead of checking for the file, we just try to load the configuration, and live with it if it works. That way we can pre-load the configuration using SimpleSAML_Configuration::loadFromArray(), as we are doing in some tests.
      8eaf60b1
  21. Jul 06, 2016
    • Jaime Pérez's avatar
      bugfix: Exception handler compatible with PHP 7. · b2bfd47d
      Jaime Pérez authored
      PHP 7 changed the way it handles internal errors. Now, Exception objects inherit from the Throwable interface, as well as the new Error objects. Internal functions throw Error objects now instead of raising an error, so the exception handler would need to handle them as well. Therefore, the exception handler is no longer guaranteed to receive an Exception object. We need now to discern whether the parameter is an exception (and continue our business as usual), or an Error (in case such thing exists, only PHP 7), and in this last case parse it and let the error handler do its stuff.
      
      This should resolve #330.
      b2bfd47d
  22. Jun 29, 2016
    • Jaime Pérez's avatar
      Add a new hook for exception handling. · 918dcd16
      Jaime Pérez authored
      In line with the previous commit, we now allow hooking in the exception handler, so that a module can implement its own logic to deal with certain exceptions.
      918dcd16
    • Jaime Pérez's avatar
      Stop intercepting exceptions in www/module.php. · 613e2c99
      Jaime Pérez authored
      The module.php file is the way we allow modules to have their own pages. All those are executed and presented to the user via this script. However, if an exception is thrown by a module, that exception will be captured directly by the module.php script. This prevents us from adding more logic to exception handling, adds code duplication, and makes the exception handling non-uniform, since we could end up handling the same exception differently depending on whether it was thrown by a module or by a regular page.
      
      Now we no longer intercept exceptions in module.php, allowing the exception handler to kick in. That way exceptions are always handled uniformly, and we can also implement additional logic that we may want (i.e. adding a hook to the exception handler so that modules could handle exceptions the way they want).
      613e2c99
  23. Jun 06, 2016
  24. Jun 03, 2016
  25. Apr 20, 2016
  26. Apr 11, 2016
  27. Mar 09, 2016
  28. Mar 03, 2016
  29. Mar 02, 2016
  30. Feb 26, 2016
  31. Feb 18, 2016
  32. Feb 17, 2016
  33. Jan 25, 2016
  34. Nov 06, 2015
Loading