Skip to content
Snippets Groups Projects
  1. Nov 14, 2016
  2. Nov 07, 2016
  3. Aug 30, 2016
  4. Aug 10, 2016
    • Jaime Pérez's avatar
      bugfix: Avoid the SAML2 IdP resilient to failures when getting DOMNodeList attribute values. · bd5ede94
      Jaime Pérez authored
      Due to recent changes in the SAML2 library, when an attribute has a value that contains XML, its contents are returned as a DOMNodeList instead of a string. This causes problems when running as a proxy, since the SAML2 IdP will obtain attributes in a format that cannot be cast to string. Regardless of the attribute encoding configured in the IdP for a remote SP, we should handle those cases gracefully, so that the IdP don't end up in an uncaught exception.
      bd5ede94
  5. 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
  6. Apr 13, 2016
  7. Mar 09, 2016
  8. Nov 06, 2015
  9. Oct 11, 2015
  10. Aug 30, 2015
    • Jaime Perez Crespo's avatar
      When building an assertion, the current time should be obtained once, used... · de4e22c5
      Jaime Perez Crespo authored
      When building an assertion, the current time should be obtained once, used many, instead of being obtained every time we are using it (that could lead to clock discrepancies between several timestamps in the same assertion). Additionally, if authentication happened in the past (that is, we got a request that is not the one that triggered authentication, and this is pure SSO), we should calculate the value for SessionNotOnOrAfter relative to the start of the session, not the current time. This resolves #244.
      de4e22c5
  11. May 31, 2015
  12. Apr 23, 2015
  13. Apr 21, 2015
  14. Apr 20, 2015
  15. Apr 16, 2015
  16. Apr 15, 2015
  17. Feb 20, 2015
  18. Jan 19, 2015
  19. Jul 10, 2014
  20. Jul 09, 2014
  21. Jul 08, 2014
  22. Feb 02, 2014
  23. Dec 09, 2013
  24. Nov 26, 2013
  25. Nov 25, 2013
  26. Aug 13, 2013
  27. Aug 12, 2013
  28. Aug 09, 2013
  29. Jul 17, 2013
  30. Dec 03, 2012
  31. Aug 02, 2012
  32. Apr 17, 2012
  33. Mar 29, 2012
Loading