Fix documentation links

Apparently, links to modules must have a "./" prefix.

docs/index.md

@@ -31,7 +31,7 @@ SimpleSAMLphp Documentation
   * [Configuring HTTP-Artifact](./simplesamlphp-artifact-idp)
   * [Identity Provider Advanced Topics](simplesamlphp-idp-more)
   * [Holder-of-Key profile](simplesamlphp-hok-idp)
- * [Automated Metadata Management](metarefresh:simplesamlphp-automated_metadata)
+ * [Automated Metadata Management](./metarefresh:simplesamlphp-automated_metadata)
  * [Maintenance and configuration](simplesamlphp-maintenance) - covers session handling, php configuration etc.
  * [Authentication Processing Filters](simplesamlphp-authproc) - attribute filtering, attribute mapping, consent, group generation etc.
  * [Advanced features](simplesamlphp-advancedfeatures) - covers bridging protocols, attribute filtering, etc.

docs/simplesamlphp-advancedfeatures.md

@@ -60,7 +60,7 @@ Automatic update of SAML 2.0 Metadata XML from HTTPS
 ----------------------------------------------------
 
 The `metarefresh` module is the preferred method for doing this.
-Please see the [metarefresh documentation](metarefresh:simplesamlphp-automated_metadata).
+Please see the [metarefresh documentation](./metarefresh:simplesamlphp-automated_metadata).
 
 
 

docs/simplesamlphp-customauth.md

@@ -216,7 +216,7 @@ Note that we have updated the username & password to "theconfigusername" and "th
 A more complete example - custom database authentication
 --------------------------------------------------------
 
-The [sqlauth:SQL](sqlauth:sql) authentication source can do simple authentication against SQL databases.
+The [sqlauth:SQL](./sqlauth:sql) authentication source can do simple authentication against SQL databases.
 However, in some cases it cannot be used, for example because the database layout is too complex, or because the password validation routines cannot be implemented in SQL.
 What follows is an example of an authentication source that fetches an user from a database, and validates the password using a custom function.
 

docs/simplesamlphp-install.md

@@ -234,7 +234,7 @@ There are a few steps that you should complete in the main configuration file, `
 -  Set an administrator password. This is needed to access some of the pages in your SimpleSAMLphp installation web
    interface.
    
-   Hashed passwords can also be used here. See the [`authcrypt`](authcrypt:authcrypt) documentation
+   Hashed passwords can also be used here. See the [`authcrypt`](./authcrypt:authcrypt) documentation
    for more information.
 
    ```
@@ -374,7 +374,7 @@ in a separate document.
    + [Remote SP reference](simplesamlphp-reference-sp-remote)
    + [Setting up an IdP for G Suite (Google Apps)](simplesamlphp-googleapps)
    + [Advanced Topics](simplesamlphp-idp-more)
- - [Automated Metadata Management](metarefresh:simplesamlphp-automated_metadata)
+ - [Automated Metadata Management](./metarefresh:simplesamlphp-automated_metadata)
  - [Maintenance and configuration](simplesamlphp-maintenance)
 
 

docs/simplesamlphp-sp.md

@@ -122,7 +122,7 @@ directory.
 If you intend to add your SP to a federation, the procedure for managing trust in federations differ, but the common part is
 that you would need to provide the *SAML 2.0 metadata of your SP*, and register that with the federation administration.
 You will probably be required too to consume the federation metadata periodically. Read more about
-[automated metadata management](metarefresh:simplesamlphp-automated_metadata) to learn more about that. 
+[automated metadata management](./metarefresh:simplesamlphp-automated_metadata) to learn more about that. 
 
 
 Test the SP