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: docs/topics/policy.md
+6-8Lines changed: 6 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,11 +24,10 @@ As such, they usually can be bypassed through the admin API or the CLI if needed
24
24
25
25
### User attributes
26
26
27
-
The policy is evaluated in three different scenarios:
27
+
The policy is evaluated in the following different scenarios:
28
28
29
-
-[`register.rego`]: During user registration, either with password credentials or with an upstream OAuth 2.0 provider. This calls the [`email.rego`]and [`password.rego`] policies as well.
29
+
-[`register.rego`]: During user registration, either with password credentials or with an upstream OAuth 2.0 provider. This calls the [`email.rego`]policy as well.
30
30
-[`email.rego`]: When a user adds a new email address to their account.
31
-
-[`password.rego`]: When a user changes their password.
32
31
33
32
### Client registration
34
33
@@ -69,8 +68,7 @@ This is especially important as in the future it will make it possible to implem
69
68
To understand the authorization process and how sessions are created, refer to the [authorization and sessions](./authorization.md) section.
0 commit comments