Difference between revisions of "Identity Service"
m (Protected "Identity Service" ([Edit=Sysops only] (indefinite) [Move=Sysops only] (indefinite))) |
|||
| Line 1: | Line 1: | ||
== Introduction == | == Introduction == | ||
| − | + | The LFS Identity Service -based on Oauth2- allows you to integrate LFS user authentication into your own website. Identity tokens are also required for using the LFS API. Both purposes are often used together; your website can authenticate an LFS user visiting your own website to perform actions on your website, on behalf of the LFS user. These actions are performed using the LFS API. Though you can also use the LFS API alone via (back end) scripts, to fetch and / or update information related to your own LFS account. | |
== Application == | == Application == | ||
Revision as of 14:39, 22 February 2022
Introduction
The LFS Identity Service -based on Oauth2- allows you to integrate LFS user authentication into your own website. Identity tokens are also required for using the LFS API. Both purposes are often used together; your website can authenticate an LFS user visiting your own website to perform actions on your website, on behalf of the LFS user. These actions are performed using the LFS API. Though you can also use the LFS API alone via (back end) scripts, to fetch and / or update information related to your own LFS account.
Application
An Application is always required for Oauth2 authentications, for each flow. An Application must have 1 redirect uri, even if it's not used (e.g. with implicit flows / with Client Secret) https://www.lfs.net/account/api
Authentication Flows
2 main flows: - for single page applications - for back end scripts
Single Page Applications
explanation here
Back End Scripting
explanation here
Usage
examples
Single Page Applications
example here
Back End Scripting
example here
