Add third-party logins page

Add missing participant creation

Author: gounux

documentation/reference/qfieldcloud/logins.en.md

@@ -0,0 +1,84 @@
+---
+title: Third-party login
+tx_slug: documentation_reference_qfieldcloud_sso_auth
+---
+
+# Third-party authentication
+
+QFieldCloud and QField / QFieldSync clients allow authentication using regular login and password, for a user that is already registered on QFieldCloud.
+
+It is also possible to authenticate using a third-party identity provider (e.g. Google, [OpenID Connect](https://openid.net/developers/how-connect-works/)).
+
+Here is a sequence diagram of how a third-party login happens in QFieldCloud (in the browser):
+
+```mermaid
+sequenceDiagram
+    autonumber
+
+    actor User
+    participant QFC as QFieldCloud
+
+    User ->> QFC: Access login page
+    QFC -->> User: Display login form with configured third-party login buttons
+
+    User ->> QFC: Click third-party login button
+
+    create participant IDP as Identity Provider
+    QFC ->> IDP: Redirect to IDP for login
+    IDP -->> User: Display IDP's login form
+
+    User ->> IDP: Log in using IDP's credentials
+    destroy IDP
+
+    IDP ->> QFC: Redirect back with auth details
+
+    alt User does not already have a QFieldCloud account
+    note over QFC: QFieldCloud account is created using IDP auth details
+    end
+
+    QFC -->> User: User is logged in
+```
+
+Here is a sequence diagram of how third-party authentication happens in QField and QFieldSync:
+
+```mermaid
+sequenceDiagram
+    autonumber
+
+    participant IDP as Identity Provider
+    actor User
+    participant QF as QField / QFieldSync
+    participant QFC as QFieldCloud
+
+    User ->>+ QF: Open the QFieldCloud login dialog
+
+    QF ->> QFC: Ask for configured third-party ID providers
+    QFC -->> QF: Answer with the list of configured third-party ID providers
+    QF -->>- User: Display a button for each third-party ID provider
+
+    User ->>+ QF: Click on 'Login with XYZ' provider button
+
+    Note over QF: A QgsAuthMethodConfig of type OAuth2 is created<br/>QGIS auth manager recognizes that the user is not authenticated yet<br/> QGIS auth manager then redirects to the IDP for authenticating the user
+
+    QF ->>+ IDP: Redirect to IDP for login
+    IDP -->> User: Display IDP's login form in a browser
+    User ->> IDP: Log in using IDP's credentials in the browser
+    IDP ->>- QF: Answer with auth details and an id_token token
+
+    QF ->>+ QFC: Ask for current user's informations
+    Note over QF,QFC: The id_token provided by IDP is in in the X-QFC-ID-Token HTTP header<br/>The IDP provider type (e.g. "google") is in the X-QFC-IDP-ID header
+
+    QFC -->>- QF: Answer with user information (username, avatar, etc.)
+    QF -->>- User: User is logged in and authenticated
+
+    loop send HTTP regular requests (e.g. file synchronization)
+        QF ->> QFC: Send a request (e.g. file Download/Upload)
+        Note over QF,QFC: The id_token provided by IDP is in in the X-QFC-ID-Token HTTP header<br/>The IDP provider type (e.g. "google") is in the X-QFC-IDP-ID header
+        QFC -->> QF: Reply to the request
+    end
+
+    loop refresh token regularly
+        QF ->> IDP: Ask for a new token
+        IDP -->> QF: Send a refreshed token
+    end
+```