You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/client-applications.rst
+50-4Lines changed: 50 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -109,8 +109,8 @@ client registration. Here is an example of dynamic registration you can implemen
109
109
client_id = response.json["client_id"]
110
110
client_secret = response.json["client_secret"]
111
111
112
-
Nominal authentication case
113
-
---------------------------
112
+
Nominal authentication workflow
113
+
-------------------------------
114
114
115
115
Let us suppose that your application have a ``/protected`` that redirects users
116
116
to the IAM server if unauthenticated.
@@ -180,8 +180,8 @@ They allow you to skip the login, password and consent pages:
180
180
# 4. now you have access to the protected page
181
181
res = test_client.get("/protected")
182
182
183
-
Error cases
184
-
-----------
183
+
Authentication workflow errors
184
+
------------------------------
185
185
186
186
The `OAuth2 <https://datatracker.ietf.org/doc/html/rfc6749>`_ and the `OpenID Connect <https://openid.net/specs/openid-connect-core-1_0.html>`_ specifications details how things might go wrong:
187
187
@@ -209,3 +209,49 @@ The `OIDC error codes <https://openid.net/specs/openid-connect-core-1_0.html#Aut
209
209
210
210
You might or might not be interested in testing how your application behaves when it encounters those situations,
211
211
depending on the situation and how much you trust the libraries that helps your application perform the authentication process.
212
+
213
+
Account creation workflow
214
+
-------------------------
215
+
216
+
The `Initiating User Registration via OpenID Connect 1.0 <https://openid.net/specs/openid-connect-prompt-create-1_0.html>`_
217
+
specification details how to initiate an account creation workflow at the IAM
218
+
by setting the ``prompt=create`` authorization request parameter.
219
+
220
+
In the following example, we suppose that the ``/create`` endpoint redirects
221
+
to the IAM authorization endpoint with the ``prompt=create`` parameters.
0 commit comments