From 0ef4faaff0df7b5365c95f05d8070a5d3393ef40 Mon Sep 17 00:00:00 2001 From: Florian Forster Date: Fri, 23 Apr 2021 00:25:21 +0200 Subject: [PATCH] docs: security txt (#1655) * docs: security txt * fix broken links --- docs/docs/quickstarts/go.md | 6 +++--- docs/static/security.txt | 4 ++++ 2 files changed, 7 insertions(+), 3 deletions(-) create mode 100644 docs/static/security.txt diff --git a/docs/docs/quickstarts/go.md b/docs/docs/quickstarts/go.md index fafefa853..b2080a6e3 100644 --- a/docs/docs/quickstarts/go.md +++ b/docs/docs/quickstarts/go.md @@ -12,9 +12,9 @@ At the end of the guide you should have an application able read the details of The client [SDK](https://github.com/caos/zitadel-go) will handle all necessary OAuth 2.0 requests and send the required headers to the ZITADEL API using our [OIDC client library](https://github.com/caos/oidc). All that is required, is a service account with an Org Owner role assigned and its key JSON. -However, we recommend you read the guide on [how to access ZITADEL API](../guides/access-zitadel-apis) and the associated guides for a basic knowledge of : - - [Recommended Authorization Flows](../guides/oauth-recommended-flows) - - [Service Users](../guides/serviceusers) +However, we recommend you read the guide on [how to access ZITADEL API](../guides/usage/access-zitadel-apis) and the associated guides for a basic knowledge of : + - [Recommended Authorization Flows](../guides/usage/oauth-recommended-flows) + - [Service Users](../guides/usage/serviceusers) > Be sure to have a valid key JSON and that its service account is either ORG_OWNER or at least ORG_OWNER_VIEWER before you continue with this guide. diff --git a/docs/static/security.txt b/docs/static/security.txt new file mode 100644 index 000000000..1230c025d --- /dev/null +++ b/docs/static/security.txt @@ -0,0 +1,4 @@ +Contact: mailto:security@zitadel.ch +Expires: Fri, 31 Dec 2021 23:00 +0200 +Preferred-Languages: en, de +Canonical: https://docs.zitadel.ch/security.txt \ No newline at end of file