- Sep 25, 2019
-
-
Tim van Dijen authored
-
- Aug 28, 2019
-
-
Tim van Dijen authored
-
- Jul 23, 2019
-
-
Tim van Dijen authored
Fix Psalm-issues in the modules-directory
-
- Jun 06, 2019
-
-
Tim van Dijen authored
-
- Feb 11, 2019
-
-
Tim van Dijen authored
-
- Jan 17, 2019
-
-
Jaime Pérez Crespo authored
-
Jaime Pérez Crespo authored
-
- Dec 07, 2018
-
-
Tim van Dijen authored
Start migrating to SAML2 getters/setters
-
- Nov 13, 2018
-
-
Thijs Kinkhorst authored
-
- Nov 12, 2018
-
-
Jelle Witteveen authored
-
- Nov 07, 2018
-
-
Jelle Witteveen authored
-
Jelle Witteveen authored
-
- Oct 17, 2018
-
-
Arno van der Vegt authored
-
- Jun 01, 2018
-
-
Tim van Dijen authored
-
- May 31, 2018
-
-
Tim van Dijen authored
-
Tim van Dijen authored
-
- May 29, 2018
-
-
Thijs Kinkhorst authored
SHA-1 is still supported but needs to be configured explicitly if you need it.
-
- May 28, 2018
-
-
Jaime Pérez Crespo authored
-
- Jan 26, 2018
-
-
Tim van Dijen authored
-
Jaime Pérez Crespo authored
This allows us to both specify the details of the policy, and also to avoid skipping sending one by setting the configuration option to false.
-
- Jan 06, 2018
-
-
Tim van Dijen authored
-
- Oct 25, 2017
-
-
Jaime Pérez Crespo authored
-
- Oct 19, 2017
-
-
fentie authored
-
- Dec 09, 2016
-
-
Jaime Pérez authored
- Variables possibly undefined when first used. - Usage of XMLSecurityKey class without proper namespace.
-
Jaime Pérez authored
This resolves #530. There are two problems here: - When only one SubjectConfirmation is received and it is empty, an error should be thrown. However, the error would be a not very descriptive message warning about access to a non-property in a null object. Something more descriptive should be in place. - Additionally, in PHP 7.0 this is an error and not an exception, and then the code continues to execute, effectively allowing assertions without a proper SubjectConfirmation element. This is wrong according to the standard.
-
- Sep 05, 2016
-
-
Jaime Pérez authored
Even though the default "exact" is used by most people, and few products support anything else, there's people asking for this.
-
- Aug 05, 2016
-
-
Thijs Kinkhorst authored
Issue a notice when the option is used nonetheless. Closes: #432
-
- Jul 26, 2016
-
-
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.
-
- Mar 29, 2016
-
-
Jaime Perez Crespo authored
This is related to #346, and closes #347. It enables richer NameIDPolicy configuration, allowing to set not only the format, but also the value for "AllowCreate".
-
- Mar 09, 2016
-
-
Jaime Perez Crespo authored
-
- Nov 06, 2015
-
-
Jaime Perez Crespo authored
-
Jaime Perez Crespo authored
(being respectful with occurences that might change the behaviour, i.e. default database prefixes)
-
Jaime Perez Crespo authored
This reverts commit 09c5a23f.
-
- Nov 05, 2015
-
-
Thijs Kinkhorst authored
SHA-1 is still supported but needs to be configured explicitly if you need it.
-
- May 12, 2015
-
-
Brian Vuyk authored
-
- May 11, 2015
-
-
Brian Vuyk authored
-
- Apr 21, 2015
-
-
Jaime Perez Crespo authored
-
Jaime Perez Crespo authored
Move SimpleSAML_Utilities::selfURLNoQuery() to SimpleSAML\Utils\HTTP::getSelfURLNoQuery() and deprecate the former.
-
- Apr 20, 2015
-
-
Jaime Perez Crespo authored
-
- Apr 16, 2015
-
-
Jaime Perez Crespo authored
Mark the old ones as deprecated and schedule them for removal in 2.0.
-