TheArchive/zitadel
1
0
Fork 0
mirror of https://github.com/zitadel/zitadel.git synced 2024-12-12 02:54:20 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: security txt (#1655)

Browse Source 
* docs: security txt

* fix broken links
This commit is contained in:
Florian Forster 2021-04-23 00:25:21 +02:00 committed by GitHub
parent c0878e4509
commit 0ef4faaff0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/docs/quickstarts/go.md
View File

@ -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.

4
docs/static/security.txt vendored Normal file
View File

@ -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