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
#nginx.ingress.kubernetes.io/limit-whitelist: "x.x.x.x/x" # Configure the internal network to be excluded from rate-limiting, you can specify a list of IPs or CIDRs to allow
8
+
#nginx.ingress.kubernetes.io/limit-connections: "20" # Limit the number of connections per IP address
9
+
#nginx.ingress.kubernetes.io/limit-rpm: "300" # Limit the number of requests per minute per IP address
10
+
#nginx.ingress.kubernetes.io/limit-rps: "10" # Limit the number of requests per second per IP address
Copy file name to clipboardExpand all lines: docs/external-password-api.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# External Password - API
1
+
# External Password API
2
2
3
3
Use an external password API when you need FoxIDs to (a) delegate password validation to an existing password store or policy engine, (b) notify an external system about password changes performed in FoxIDs, or (c) handle both scenarios.
4
4
@@ -11,7 +11,7 @@ If the built-in password policy rejects the password, the external password API
11
11
If you require both validation and change notification, and both can be handled by the same system, implement only the validation API.
12
12
When you receive a validation request where the password is accepted, perform your notification logic internally. Implement both endpoints only if you must call two different backend systems.
13
13
14
-
External password APIs are part of the possible password checks for [internal users](users-internal.md).
14
+
External password API can be [configured as password check](users-internal.md#password-check) for [internal users](users-internal.md).
Copy file name to clipboardExpand all lines: docs/users-external.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,7 @@
1
1
# External users
2
-
An external user is linked to one authentication method and can only be authenticated with that particular authentication method. External users can be linked to the authentication methods: OpenID Connect, SAML 2.0, External Login and Environment Link.
3
-
It is optional to use external users; they are not created by default.
2
+
You can use just-in-time (JIT) provisioning to create external users and associate them with an external identity.
3
+
An external user is associated with one authentication method (OpenID Connect, SAML 2.0, External Login, or Environment Link) and can only be authenticated using that authentication method.
4
+
Using external users is optional; they are not created by default.
4
5
5
6
All external users grouped under an authentication method are linked with the same claim type (e.g. the `sub` claim type) and the users are separated by unique claim values.
0 commit comments