andwati/zitadel
1
0
Fork 0
mirror of https://github.com/andwati/zitadel.git synced 2026-11-07 06:42:15 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(legal): merge rate limits (#5719)

Browse Source 
* formatting title configuration

* merge policy and metrics

* raising limits, editorial

* Update docs/docs/legal/rate-limit-policy.md

Co-authored-by: Elio Bischof <[email protected]>

* Apply suggestions from code review

Co-authored-by: Elio Bischof <[email protected]>

---------

Co-authored-by: Elio Bischof <[email protected]>
This commit is contained in:
mffap
2023-04-21 13:21:05 +00:00
committed by GitHub
co-authored by Elio Bischof
parent 5d6399da24
commit ebc140a234
3 changed files with 23 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/docs/guides/solution-scenarios/configurations.mdx
+3 -3
View File
@@ -27,9 +27,9 @@ More about the [scopes](/apis/openidoauth/scopes#reserved-scopes)
If you have an application that runs a dedicated domain for each customer you need to instruct ZITADEL to allow redirection for each domain specifically to safeguard against phishing attacks.
Example:
MyApplication: customer-a.app.com
ZITADEL Login: login.app.com
Example:
MyApplication: `customer-a.app.com`
ZITADEL Login: `login.app.com`
In the OIDC Authorization request you always have to send the redirect URI to where you like to be redirected after login.
To handle this scenario it is possible to register multiple URIs on each application in ZITADEL, the only criteria is that the requested URI has to match one of the registered URIs.