Identity Service - Revision history

Victor: /* Back End Scripting */

2022-02-22T15:53:12Z

Back End Scripting

2022-02-22T15:52:59Z

Back End Scripting

2022-02-22T15:52:43Z

Back End Scripting

2022-02-22T15:52:15Z

Single Page Application

2022-02-22T15:48:20Z

The Application

2022-02-22T15:47:20Z

2022-02-22T15:46:44Z

Single Page Application

2022-02-22T15:46:23Z

Server Side Application

2022-02-22T15:45:59Z

Authentication Grant Types

2022-02-22T15:45:22Z

@@ Line 57: / Line 57: @@
 * POST to https://id.lfs.net/oauth2/access_token
-grant_type    => 'client_credentials',
+** grant_type    => 'client_credentials',
-client_id     => 'CLIENT_ID',
+** client_id     => 'CLIENT_ID',
-client_secret => 'CLIENT_SECRET',
+** client_secret => 'CLIENT_SECRET',
 * receive access token immediately

@@ Line 57: / Line 57: @@
 * POST to https://id.lfs.net/oauth2/access_token
-  grant_type    => 'client_credentials',
+grant_type    => 'client_credentials',
-  client_id     => 'CLIENT_ID',
+client_id     => 'CLIENT_ID',
-  client_secret => 'CLIENT_SECRET',
+client_secret => 'CLIENT_SECRET',
 * receive access token immediately

←Older revision		Revision as of 15:52, 22 February 2022
Line 55:		Line 55:

	... stuffs here ...		... stuffs here ...
		+
		+	* POST to https://id.lfs.net/oauth2/access_token
		+	grant_type => 'client_credentials',
		+	client_id => 'CLIENT_ID',
		+	client_secret => 'CLIENT_SECRET',
		+	* receive access token immediately

	== Authentication Scopes ==		== Authentication Scopes ==

←Older revision		Revision as of 15:52, 22 February 2022
Line 41:		Line 41:

	... stuffs here ...		... stuffs here ...
		+
		+	* https://id.lfs.net/oauth2/authorize?response_type=code&client_id=CLIENT_ID&redirect_uri=REDIRECT_URI&scope=openid%20profile&state=CSRFTOKEN
		+	* receive redirect URI (goes to lfs.net's login page)
		+	* client logs in if not already logged in
		+	* client must accept scopes requested by Application
		+	* client is redirected to id.lfs.net one final time
		+	* client is redirected to Application redirect URI

	=== Back End Scripting ===		=== Back End Scripting ===

@@ Line 15: / Line 15: @@
 An Application must have a name and one redirect uri pointing to a callback endpoint on your website where authenticated users will return to after authentication. A redirect uri is also required even if you only use the LFS API for your own (back end) purposes. In that case you can enter a fictional redirect uri.
-Upon registration of an Application you will receive a Client ID and a Client Secret that you must store in order to perform Identity Authentications later on. Note that the Client Secret will only be shown to you once, after Application registration.
+Once your Application is registered, you will receive a Client ID and a Client Secret that you must store in order to perform Identity Authentications later on. Note that the Client Secret will only be shown to you once, after Application registration.
 == Authentication Grant Types ==

@@ Line 51: / Line 51: @@
 == Authentication Scopes ==
 Scope information here.
 == Usage Examples ==
 examples (are these needed? Maybe the grant explanations above should be enough - I don't think I should start providing actual code examples here - there are plenty available out on the nets.)
 === Single Page Applications ===

@@ Line 34: / Line 34: @@
 === Single Page Application ===
-If you have your own javascript driven website where you want to allow your users to login using their own LFS credentials or just confirm their LFS identity to e.g. sign them up for races, you must use this grant type. You will also have the option of accessing certain information of these LFS accounts by using [[Identity_Service#Authentication_Scopes|scopes]] during the authentication process.
+If you have your own javascript driven website or application where you want to allow your users to login using their own LFS credentials or just confirm their LFS identity to e.g. sign them up for races, you must use this grant type. You will also have the option of accessing certain information of these LFS accounts by using [[Identity_Service#Authentication_Scopes|scopes]] during the authentication process.
 For this purpose you should use the Authorization Code Grant with PKCE.

@@ Line 25: / Line 25: @@
 === Server Side Application ===
-If you have your own server side website (e.g. back end driven with PHP) where you want to allow your users to login using their own LFS credentials or just confirm their LFS identity to e.g. sign them up for races, you must use this grant type. You will also have the option of accessing certain information of these LFS accounts by using [[Identity_Service#Authentication_Scopes|scopes]] during the authentication process.
+If you have your own server side website or application (e.g. back end driven with PHP) where you want to allow your users to login using their own LFS credentials or just confirm their LFS identity to e.g. sign them up for races, you must use this grant type. You will also have the option of accessing certain information of these LFS accounts by using [[Identity_Service#Authentication_Scopes|scopes]] during the authentication process.
 For this purpose you should use the Authorization Code Grant.

@@ Line 24: / Line 24: @@
 * '''Client Credentials Grant''', used with back end scripts
-=== Server Side Website ===
+=== Server Side Application ===
 If you have your own server side website (e.g. back end driven with PHP) where you want to allow your users to login using their own LFS credentials or just confirm their LFS identity to e.g. sign them up for races, you must use this grant type. You will also have the option of accessing certain information of these LFS accounts by using [[Identity_Service#Authentication_Scopes|scopes]] during the authentication process.