From 3ccb39a77c715a493cac2fce6c22182db81bb1e7 Mon Sep 17 00:00:00 2001 From: Ozzie Isaacs Date: Wed, 14 Apr 2021 12:26:39 +0200 Subject: [PATCH] Updated OAuth Login with Github and Google (markdown) --- OAuth-Login-with-Github-and-Google.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/OAuth-Login-with-Github-and-Google.md b/OAuth-Login-with-Github-and-Google.md index 6b145ea..33ae398 100644 --- a/OAuth-Login-with-Github-and-Google.md +++ b/OAuth-Login-with-Github-and-Google.md @@ -10,7 +10,7 @@ The following screenshot shows the relevant settings. ![Settings](images/OAuth/Github_OAuth_Settings.png) -The Callback routine has to end with `login/github/authorized`. +The Callback routine has to end with `login\github\authorized`. After clicking on "Register application" Github will present you the Client ID and Client secret values. If your Callback routine is a non encrypted endpoint, Calibre-Web will deny accepting tokens for this endpoint. You can overwrite the encrpytion check by setting an enviroment variable with the name `OAUTHLIB_INSECURE_TRANSPORT`. This is for obvious reasons ** NOT recommended** for productive systems.