commit 5e9566

Commit `5e9566`

2024-02-16 03:04:40 Hargata Softworks: updated guide with screenshots

0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9

`openid.md` ..
@@ 12,12 12,12 @@
	OpenIDConfig__Scope=The scope for retrieving the user's email claim(usually it's just 'email')
	```

-	The following sample shows how to set up OIDC with Google as the provider
+	The following sample shows how to set up OIDC with Google as the provider with the LubeLogger instance running on https://localhost:5011

	```
	OpenIDConfig__Name=Google
-	OpenIDConfig__ClientId=<your Google API Client Id>.apps.googleusercontent.com
-	OpenIDConfig__ClientSecret=<your Google API Client Password>
+	OpenIDConfig__ClientId=xxx.apps.googleusercontent.com
+	OpenIDConfig__ClientSecret=<your Google API Client Secret>
	OpenIDConfig__AuthURL=https://accounts.google.com/o/oauth2/auth
	OpenIDConfig__TokenURL=https://oauth2.googleapis.com/token
	OpenIDConfig__RedirectURL=https://localhost:5011/Login/RemoteAuth
@@ 25,3 25,11 @@
	```

	Once you have all these environment variables injected correctly, you should see the ability to login via your OIDC provider. Note: Currently LubeLogger only supports one OIDC provider.
+
+	![](/OpenID/a/image-1708052127031.png)
+
+	![](/OpenID/a/image-1708052614261.png)
+
+	LubeLogger uses the user's email address to authenticate against a registered user, the email address provided by the OIDC provider must match the email address of the user in the system. This in turns means that before a user can login via OIDC they must first register an account on LubeLogger with a valid token, otherwise you will encounter this 'error' log in the console. Note that this is an informational log which means you have to set your LogLevel appropriately in order to see this info log.
+
+	![](/OpenID/a/image-1708052421948.png)

Commit `5e9566`