7d855efb1f
The PKCE flow according to [RFC 7636](https://datatracker.ietf.org/doc/html/rfc7636) allows for secure authorization without the requirement to provide a client secret for the OAuth app. It is implemented in Gitea since #5378 (v1.8.0), however without being able to omit client secret. Since #21316 Gitea supports setting client type at OAuth app registration. As public clients are already forced to use PKCE since #21316, in this PR the client secret check is being skipped if a public client is detected. As Gitea seems to implement PKCE authorization correctly according to the spec, this would allow for PKCE flow without providing a client secret. Also add some docs for it, please check language as I'm not a native English speaker. Closes #17107 Closes #25047 |
||
|---|---|---|
| .. | ||
| assets/js | ||
| content | ||
| layouts | ||
| scripts | ||
| static | ||
| .gitignore | ||
| config.yaml | ||
| LICENSE | ||
| Makefile | ||
| README_ZH.md | ||
| README.md | ||
Gitea: Docs
Hosting
These pages are hosted using netlifycms and get
automatically updated on every push to the master branch.
Install
These pages use the Hugo static site generator.
If you are planning to contribute you'll want to download and install Hugo on
your local machine.
The installation of Hugo is out of the scope of this document, so please take
the official install instructions to
get Hugo up and running.
Development
To generate the website and serve it on localhost:1313
just execute this command and stop it with Ctrl+C:
make server
When you are done with your changes just create a pull request, after merging
the pull request the website will be updated automatically.
Contributing
Fork -> Patch -> Push -> Pull Request
Authors
License
This project is under the Apache-2.0 License. See the LICENSE file
for the full license text.
Copyright
Copyright (c) 2016 The Gitea Authors <https://gitea.io>