starting the readthedocs stuff

.gitignore

@@ -120,3 +120,6 @@ Sustainsys.Saml2.StubIdp/App_Data/*.json
 *.ndproj
 NDependOut
 *.coveragexml
+
+#ReadTheDocs output
+docs/_build

.vscode/settings.json

@@ -0,0 +1,3 @@
+{
+    "restructuredtext.confPath": "c:\\Users\\edahl\\Saml2"
+}

README.md

@@ -22,7 +22,7 @@ forms sites.
 Note that the Owin & ASP.NET Core2 modules enables SAML identity providers to be integrated within
 [IdentityServer3](https://github.com/IdentityServer/IdentityServer3) and
 [IdentityServer4](https://github.com/IdentityServer/IdentityServer3) packages.  Review 
-[this document](doc/IdentityServer3Okta.md) to see how to configure Saml2
+[this document](docs/IdentityServer3Okta.md) to see how to configure Saml2
 with IdentityServer3 and Okta to add Okta as an identity provider to an IdentityServer3 project.
 There is also a SampleIdentityServer3 project in the Saml2 repository.
 
@@ -37,7 +37,7 @@ contains a Saml2 authentication handler for ASP.NET Core 2.x.
 
 Once the nuget packages are installed you must provide configuration either through code
 or through `web.config` sections.
-See [configuration](doc/Configuration.md) for details.
+See [configuration](docs/Configuration.md) for details.
 
 ## Troubleshooting
 
@@ -49,8 +49,8 @@ See [configuration](doc/Configuration.md) for details.
 
 ## Saml2AuthenticationModule
 The Saml2AuthenticationModule provides Saml2 authentication to IIS web sites. In many cases it should just be
-[configured](doc/Configuration.md) in and work without any code written in the application 
-at all (even though [providing an own ClaimsAuthenticationManager](doc/ClaimsAuthenticationManager.md)
+[configured](docs/Configuration.md) in and work without any code written in the application 
+at all (even though [providing an own ClaimsAuthenticationManager](docs/ClaimsAuthenticationManager.md)
 for claims translation is highly recommended).
 
 ## Mvc Controller
@@ -62,7 +62,7 @@ over using the authentication module as it integrates with MVC's error handling.
 The Owin middleware is modeled after the external authentication modules for social login
 (such as Google, Facebook, Twitter). This allows easy integration with ASP.NET Identity 
 for keeping application specific user and role information. See the 
-[Owin Middleware](doc/OwinMiddleware.md) page for information on how to set up and use the middleware.
+[Owin Middleware](docs/OwinMiddleware.md) page for information on how to set up and use the middleware.
 
 ## ASP.NET Core 2 Handler
 The ASP.NET Core 2 Handler is compatbile with the ASP.NET Core 2.0 authentication model.

Sustainsys.Saml2.HttpModule/CommandResultHttpExtensionsShared.cs

@@ -107,7 +107,7 @@ private static void EnsureSessionAuthenticationModuleAvailable()
             {
                 throw new InvalidOperationException(
                     "FederatedAuthentication.SessionAuthenticationModule is null, make sure you have loaded the SessionAuthenticationModule in web.config. " +
-                    "See https://github.com/SustainsysIT/Saml2/blob/master/doc/Configuration.md#loading-modules");
+                    "See https://github.com/SustainsysIT/Saml2/blob/master/docs/Configuration.md#loading-modules");
             }
         }
     }

docs/.vscode/settings.json

@@ -0,0 +1,3 @@
+{
+    "restructuredtext.confPath": "c:\\Users\\edahl\\Saml2\\docs"
+}

doc/ClaimsAuthenticationManager.md → docs/ClaimsAuthenticationManager.md

@@ -1,27 +1,27 @@
-ClaimsAuthenticationManager
-==========================
-
-When using federated authentication the identity provider solely decides what 
-claims to use to populate the incoming identity. If using multiple identity
-providers there is very high probability that they will present the same
-information in somewhat different ways. That's where the 
-`ClaimsAuthenticationManager` fits in. It works as a translation filter
-that can modify or replace the incoming identity as soon as it has been
-constructed from the incoming authentication response.
-
-Implement a `ClaimsAuthenticationManager` by creating a class derived from the
-[`System.Security.Claims.ClaimsAuthenticationManager`](http://msdn.microsoft.com/en-us/library/system.security.claims.claimsauthenticationmanager.aspx)
-class.
-
-Then register it with a 
-[`<claimsAuthenticationManager>`](Configuration.md#claimsauthenticationmanager-element) 
-element in the configuration if the configuration is loaded from the config file.
-If the configuration is done in code (typically for the OWIN middleware) the
-`ClaimsAuthenticationManager` should be registered in 
-`Options.SPOptions.SystemIdentityModelIdentityConfiguration.ClaimsAuthenticationManager`.
-
-## Single Logout
-If you are using Single Logout, you need to make sure that the claims containing
-the Saml2 logout information are present in the returned identity. The
-types of the claims are available in `Saml2ClaimTypes.SessionIndex` and
-`Saml2ClaimTypes.LogoutNameIdentifier`.
+ClaimsAuthenticationManager
+==========================
+
+When using federated authentication the identity provider solely decides what 
+claims to use to populate the incoming identity. If using multiple identity
+providers there is very high probability that they will present the same
+information in somewhat different ways. That's where the 
+`ClaimsAuthenticationManager` fits in. It works as a translation filter
+that can modify or replace the incoming identity as soon as it has been
+constructed from the incoming authentication response.
+
+Implement a `ClaimsAuthenticationManager` by creating a class derived from the
+[`System.Security.Claims.ClaimsAuthenticationManager`](http://msdn.microsoft.com/en-us/library/system.security.claims.claimsauthenticationmanager.aspx)
+class.
+
+Then register it with a 
+[`<claimsAuthenticationManager>`](Configuration.md#claimsauthenticationmanager-element) 
+element in the configuration if the configuration is loaded from the config file.
+If the configuration is done in code (typically for the OWIN middleware) the
+`ClaimsAuthenticationManager` should be registered in 
+`Options.SPOptions.SystemIdentityModelIdentityConfiguration.ClaimsAuthenticationManager`.
+
+## Single Logout
+If you are using Single Logout, you need to make sure that the claims containing
+the Saml2 logout information are present in the returned identity. The
+types of the claims are available in `Saml2ClaimTypes.SessionIndex` and
+`Saml2ClaimTypes.LogoutNameIdentifier`.