Minor format and exception message fixes, plus add information about the different communication channels we have today.

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”.

`core:ScopeFromAttribute` is a generalised version of this.

Closes: #512

This should help people configure the PHP session handler and mitigate issues when sessions collide. Related to #478.

Issue a notice when the option is used nonetheless.

Closes: #432

Update module docs to use module enabling/disabling through configuration file rather than touching 'enable'/'disable' files inside module directories

The new saml:FilterScopes allows a SAML Service Provider to remove the values from a scoped attribute whose scope is not declared in the IdP metadata and/or does not match with the domain in use by the IdP itself.

This closes #22.

Mention the change in the way NameIDs are processed inside an eduPersonTargetedID, and offer an example on how to process the value.

The hash algorithm to use to calculate signature digests for self metadata was not configurable. Add the 'metadata.sign.algorithm' configuration option to fix that.

This resolves #411.

* Add an extra apache access control directive
  to make it work with newer Apaches
  Source: http://stackoverflow.com/questions/23337446/getting-a-403-forbidden-error-for-simplesaml-after-apache-upgrade

Change the extension of the documentation files from .txt to .md so that they can processed as markdown and displayed in github.

Update the documentation regarding translation (remove all references to the translation portal, reformat and fix typos).

Update the documentation. Trailing slashes are no longer required for 'baseurlpath'. This resolves #363.

Fixes #379

Add a method to SimpleSAMLphp_SessionHandlerPHP to restore a session existing previously to our own session. This can be used in SimpleSAML_Session to restore the PHP session status previous to calling our API, while also guaranteeing that our session is correctly saved. The documentation has been updated to reflect this and recommend how to deal with conflicting PHP sessions. This closes #244 and resolves #349.