This would mean that any code using this helper function could not
use the ldap.filter option. It's a followup to commit
ff5497e9 which fixed this for the
`login()` method but not for the `searchfordn()` method.

added exception logging for federation lookups

Be gentle with weird implementations that set $_SERVER['HTTPS'] to null.

SAMLBuilder AttributeAuthorityDescriptor empty protocolSupportEnumeration

Remove sensitive data from logs during LDAP filters

This reverts commit 82a46a7c.

This removes the dependency on mcrypt for good, closes #660 and resolves #615.

We've just been moved from Precise to Trusty, and PHP 5.3 is not available in the latter, so builds fail.

Otherwise, a theme would not be able to include/embed/extend its own templates.

Also tweak wording of artifact idp docs a bit re memcache extension.

Memcached extension support

Adds further support for php-memcached.

Invalidate opcache after writing a file

When opcache.validate_timestamps is disabled, then the new metadata will not be read after a metarefresh.
This can be solved by adding the metadata file to an opcache blacklist, but calling opcache_invalidate()
after writing a file is a nice out-of-the-box solution.

Hopefully, this will enable everybody that is using simplesamlphp to disable opcache.validate_timestamps
without running into problems.

This new interface allows themes to define a class that can be hooked at certain specific points of template initialization/handling, so that they can do stuff like automatically adding variables for all templates, or adding twig extensions. This classes must implement the new TemplateControllerInterface, and be specified in the "theme.controller" configuration option. This way, we avoid the performance hit if we use traditional hooks, and we also avoid hooks from other modules causing trouble.

For now, the interface offers two entry points: setUpTwig(), which allows managing the twig environment after initialization (e.g. to add an extension or define filters); and display(), which offers all the data passed to the template, and allows adding or modifying it.

This makes sense as those should be static values available to every template.

Additionally, add a "templateId" variable that we can use for templates to identify themselves.

Make sure if we are using a theme, its module is added as a valid domain where we can look for translations.

Therefore, it should be accessed using self, not $this.

- Make sure timeout is added conditionally, when we actually have it.
- Additionally, pass the state ID to the template in the "auth_state" variable. Trying to be consistent with this from now on.

Fix for #618, correcting the login layout on mobile screens.

Instead of one cache, we need to use two: one for the list of modules available, and the other for the details for them. Those caches should be filled independently, so that someone calling getModules() does not trigger the code checking of the modules are enabled or finding their hooks.

It has also an impact in performance, and covers an unlikely scenario. Instead, if you plan to use templates from another module, now you need to call the "addTemplatesFromModule()" method right after creating the template. That way you can register manually what templates you are supposed to use, being much more efficient.

An alternative way to inject data in the templates should be used. This has a terrible impact in performance, and could have undesired side effects.