- Dec 14, 2016
-
-
Thijs Kinkhorst authored
cf. 36051879
-
- Dec 12, 2016
-
-
Jaime Pérez authored
bugfix: Make sure a persistent NameID is not generated by default when the UserID is missing in the state array. This allowed misconfigured IdPs (i.e. those without both a PersistenNameID authproc filter, a “userid.attribute” configuration option and no “eduPersonPrincipalName” attribute available after running all the authentication processing filters) to generate a persistent NameID based on “null”, effectively giving all users the same identifier.
-
Jaime Pérez authored
-
Jaime Pérez authored
bugfix: When obtaining a UserID for the state array prior to running authproc filters, if the source attribute had multiple values a warning was logged but the UserID was still recorded.
-
- 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.
-
- Dec 05, 2016
-
-
Jaime Pérez authored
-
Andreas Åkre Solberg authored
-
Andreas Åkre Solberg authored
Add translated error info in data for error template. This is needed in order for theming error page with Twig.
-
- Dec 03, 2016
-
-
Jaime Pérez authored
-
- Dec 01, 2016
-
-
Thijs Kinkhorst authored
-
- Nov 30, 2016
-
-
Jaime Pérez authored
-
Jaime Pérez authored
This resolves #523.
-
- Nov 24, 2016
-
-
Jaime Pérez authored
-
Hanne Moa authored
-
- Nov 22, 2016
-
-
Jaime Pérez authored
-
Jaime Pérez authored
This resolves #519.
-
Jaime Pérez authored
The $store and $params variables were not initialized before trying to execute the prepared statement.
-
Jaime Pérez authored
This resolves #519.
-
Jaime Pérez authored
bugfix: When generating a NameID from a multivalued attribute, a warning was logged but the NameID was still generated.
-
- Nov 21, 2016
-
-
Jaime Pérez Crespo authored
Fix APR1_MD5::check call
-
ntoniazzi authored
$password and $crypted where swapped
-
- Nov 17, 2016
-
-
Tim van Dijen authored
-
- Nov 15, 2016
-
-
Thijs Kinkhorst authored
Frequently people put fs paths in baseurlpath or URL paths in the other settings. By more clearly separating these two classes of options I hope to reduce confusion a bit.
-
Thijs Kinkhorst authored
-
Thijs Kinkhorst authored
-
Thijs Kinkhorst authored
-
Hanne Moa authored
-
Thijs Kinkhorst authored
-
Thijs Kinkhorst authored
For #458
-
Thijs Kinkhorst authored
-
-
Jaime Pérez authored
-
Thijs Kinkhorst authored
-
Hanne Moa authored
-
Hanne Moa authored
-
- Nov 14, 2016
-
-
Jaime Pérez authored
The guidelines on how to write your own module talk about the process() method receiving a “$request” or a “$state” parameter, instead of being consistent and sticking to just one of the names. Use “$request”.
-
Jaime Pérez authored
-
Thijs Kinkhorst authored
Deprecate AttributeRealm authproc filter
-
Hanne Moa authored
-