git.iko.soy/typeable/oauth2-proxy
on master help sign in
doc: cncf onboarding and sponsor update

Signed-off-by: Jan Larwig <jan@larwig.com>

commitf46dcc77a8202bf663ce66c1af2a16031e164ff5 authorJan Larwig <jan@larwig.com> dateThu 15 Jan 2026, 13:15 (9 months ago) parent34c2712
15 files changed+213−165
ADOPTERS.md−28 CODE_OF_CONDUCT.md+81−103 DCO.md+34 MAINTAINERS+2−5 MAINTAINERS.md+33 README.md+31−16 docs/docs/community/contribution.md+3−3 docs/docs/community/security.md+1−1 docs/docs/configuration/sessions.md+2−2 docs/docs/welcome.md+10 docs/docusaurus.config.js+1−1 docs/versioned_docs/version-7.14.x/community/contribution.md+3−3 docs/versioned_docs/version-7.14.x/community/security.md+1−1 docs/versioned_docs/version-7.14.x/configuration/sessions.md+2−2 docs/versioned_docs/version-7.14.x/welcome.md+9
ADOPTERS.mddeleted−28
@@ -1,28 +0,0 @@
1−# Adopters
2−
3−This list showcases organizations that leverage OAuth2-Proxy within their
4−infrastructure. If your organization uses OAuth2-Proxy and isn't yet listed, we
5−encourage you to add it!
6−
7−This list aims to be a comprehensive and trusted resource for the OAuth2-Proxy
8−community, demonstrating successful adoption across all kinds of industries.
9−
10−Contributing to this list is a simple way to impact the project's growth,
11−maturity, and momentum. Thank you to all adopters and contributors of the
12−OAuth2-Proxy project!
13−
14−## Updating this list
15−
16−To add your organization to this list, you can just [open a PR](https://github.com/oauth2-proxy/oauth2-proxy/pulls)
17−to directly update this list.
18−
19−Add your organization name, your github username and if you desire a short
20−description on how you utilize oauth2-proxy.
21−
22−## OAuth2-Proxy Adopters
23−
24−This list is sorted in the order that organizations were added to it.
25−
26−| Organization | Contact | Description of Use |
27−| ------------ | ------- | ------------------ |
28−| | | |
CODE_OF_CONDUCT.md+81−103
@@ -1,134 +1,112 @@
1−# Contributor Covenant Code of Conduct
1+## CNCF Community Code of Conduct v1.3
2+
3+Other languages available:
4+- [Arabic/العربية](https://github.com/cncf/foundation/blob/main/code-of-conduct-languages/ar.md)
5+- [Bengali/বাংলা](https://github.com/cncf/foundation/blob/main/code-of-conduct-languages/bn.md)
6+- [Bulgarian/Български](https://github.com/cncf/foundation/blob/main/code-of-conduct-languages/bg.md)
7+- [Chinese/中文](https://github.com/cncf/foundation/blob/main/code-of-conduct-languages/zh.md)
8+- [Czech/Česky](https://github.com/cncf/foundation/blob/main/code-of-conduct-languages/cs.md)
9+- [Farsi/فارسی](https://github.com/cncf/foundation/blob/main/code-of-conduct-languages/fa.md)
10+- [French/Français](https://github.com/cncf/foundation/blob/main/code-of-conduct-languages/fr.md)
11+- [German/Deutsch](https://github.com/cncf/foundation/blob/main/code-of-conduct-languages/de.md)
12+- [Hebrew/עברית](https://github.com/cncf/foundation/blob/main/code-of-conduct-languages/he.md)
13+- [Hindi/हिन्दी](https://github.com/cncf/foundation/blob/main/code-of-conduct-languages/hi.md)
14+- [Hungarian/Magyar](https://github.com/cncf/foundation/blob/main/code-of-conduct-languages/hu.md)
15+- [Indonesian/Bahasa Indonesia](https://github.com/cncf/foundation/blob/main/code-of-conduct-languages/id.md)
16+- [Italian/Italiano](https://github.com/cncf/foundation/blob/main/code-of-conduct-languages/it.md)
17+- [Japanese/日本語](https://github.com/cncf/foundation/blob/main/code-of-conduct-languages/ja.md)
18+- [Korean/한국어](https://github.com/cncf/foundation/blob/main/code-of-conduct-languages/ko.md)
19+- [Polish/Polski](https://github.com/cncf/foundation/blob/main/code-of-conduct-languages/pl.md)
20+- [Portuguese/Português](https://github.com/cncf/foundation/blob/main/code-of-conduct-languages/pt.md)
21+- [Russian/Русский](https://github.com/cncf/foundation/blob/main/code-of-conduct-languages/ru.md)
22+- [Spanish/Español](https://github.com/cncf/foundation/blob/main/code-of-conduct-languages/es.md)
23+- [Turkish/Türkçe](https://github.com/cncf/foundation/blob/main/code-of-conduct-languages/tr.md)
24+- [Ukrainian/Українська](https://github.com/cncf/foundation/blob/main/code-of-conduct-languages/uk.md)
25+- [Vietnamese/Tiếng Việt](https://github.com/cncf/foundation/blob/main/code-of-conduct-languages/vi.md)
26+
27+### Community Code of Conduct
28+
29+As contributors, maintainers, and participants in the CNCF community, and in the interest of fostering
30+an open and welcoming community, we pledge to respect all people who participate or contribute
31+through reporting issues, posting feature requests, updating documentation,
32+submitting pull requests or patches, attending conferences or events, or engaging in other community or project activities.
33+
34+We are committed to making participation in the CNCF community a harassment-free experience for everyone, regardless of age, body size, caste, disability, ethnicity, level of experience, family status, gender, gender identity and expression, marital status, military or veteran status, nationality, personal appearance, race, religion, sexual orientation, socioeconomic status, tribe, or any other dimension of diversity.
235
3−## Our Pledge
36+## Scope
37+
38+This code of conduct applies:
39+* within project and community spaces,
40+* in other spaces when an individual CNCF community participant's words or actions are directed at or are about a CNCF project, the CNCF community, or another CNCF community participant in the context of a CNCF activity.
441
5−We as members, contributors, and leaders pledge to make participation in our
6−community a harassment-free experience for everyone, regardless of age, body
7−size, visible or invisible disability, ethnicity, sex characteristics, gender
8−identity and expression, level of experience, education, socio-economic status,
9−nationality, personal appearance, race, caste, color, religion, or sexual
10−identity and orientation.
42+### CNCF Events
1143
12−We pledge to act and interact in ways that contribute to an open, welcoming,
13−diverse, inclusive, and healthy community.
44+CNCF events that are produced by the Linux Foundation with professional events staff are governed by the Linux Foundation [Events Code of Conduct](https://events.linuxfoundation.org/code-of-conduct/) available on the event page. This is designed to be used in conjunction with the CNCF Code of Conduct.
1445
1546## Our Standards
1647
17−Examples of behavior that contributes to a positive environment for our
18−community include:
48+The CNCF Community is open, inclusive and respectful. Every member of our community has the right to have their identity respected.
49+
50+Examples of behavior that contributes to a positive environment include but are not limited to:
1951
2052* Demonstrating empathy and kindness toward other people
2153* Being respectful of differing opinions, viewpoints, and experiences
2254* Giving and gracefully accepting constructive feedback
2355* Accepting responsibility and apologizing to those affected by our mistakes,
2456 and learning from the experience
25−* Focusing on what is best not just for us as individuals, but for the overall
26− community
57+* Focusing on what is best not just for us as individuals, but for the
58+ overall community
59+* Using welcoming and inclusive language
2760
28−Examples of unacceptable behavior include:
2961
30−* The use of sexualized language or imagery, and sexual attention or advances of
31− any kind
62+Examples of unacceptable behavior include but are not limited to:
63+
64+* The use of sexualized language or imagery
3265* Trolling, insulting or derogatory comments, and personal or political attacks
33−* Public or private harassment
34−* Publishing others' private information, such as a physical or email address,
35− without their explicit permission
66+* Public or private harassment in any form
67+* Publishing others' private information, such as a physical or email
68+ address, without their explicit permission
69+* Violence, threatening violence, or encouraging others to engage in violent behavior
70+* Stalking or following someone without their consent
71+* Unwelcome physical contact
72+* Unwelcome sexual or romantic attention or advances
73+* Using CNCF projects or community spaces for political campaigning or promotion of political causes
74+ that are unrelated to the advancement of cloud native technology. To clarify, this policy does not restrict individuals' personal attire, including attire that expresses personal beliefs or aspects of identity.
3675* Other conduct which could reasonably be considered inappropriate in a
3776 professional setting
3877
39−## Enforcement Responsibilities
40−
41−Community leaders are responsible for clarifying and enforcing our standards of
42−acceptable behavior and will take appropriate and fair corrective action in
43−response to any behavior that they deem inappropriate, threatening, offensive,
44−or harmful.
45−
46−Community leaders have the right and responsibility to remove, edit, or reject
47−comments, commits, code, wiki edits, issues, and other contributions that are
48−not aligned to this Code of Conduct, and will communicate reasons for moderation
49−decisions when appropriate.
50−
51−## Scope
52−
53−This Code of Conduct applies within all community spaces, and also applies when
54−an individual is officially representing the community in public spaces.
55−Examples of representing our community include using an official email address,
56−posting via an official social media account, or acting as an appointed
57−representative at an online or offline event.
58−
59−## Enforcement
78+The following behaviors are also prohibited:
79+* Providing knowingly false or misleading information in connection with a Code of Conduct investigation or otherwise intentionally tampering with an investigation.
80+* Retaliating against a person because they reported an incident or provided information about an incident as a witness.
6081
61−Instances of abusive, harassing, or otherwise unacceptable behavior may be
62−reported to the community leaders responsible for enforcement at
63−https://gophers.slack.com/messages/CM2RSS25N or directly contacting one of the
64−maintainers from the MAINTAINERS file.
65−All complaints will be reviewed and investigated promptly and fairly.
82+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct.
83+By adopting this Code of Conduct, project maintainers commit themselves to fairly and consistently applying these principles to every aspect
84+of managing a CNCF project.
85+Project maintainers who do not follow or enforce the Code of Conduct may be temporarily or permanently removed from the project team.
6686
67−All community leaders are obligated to respect the privacy and security of the
68−reporter of any incident.
87+## Reporting
6988
70−## Enforcement Guidelines
89+For incidents occurring in the Kubernetes community, contact the [Kubernetes Code of Conduct Committee](https://git.k8s.io/community/committee-code-of-conduct) via <conduct@kubernetes.io>. You can expect a response within three business days.
7190
72−Community leaders will follow these Community Impact Guidelines in determining
73−the consequences for any action they deem in violation of this Code of Conduct:
91+For other projects, or for incidents that are project-agnostic or impact multiple CNCF projects, please contact the [CNCF Code of Conduct Committee](https://www.cncf.io/conduct/committee/) via <conduct@cncf.io>. Alternatively, you can contact any of the individual members of the [CNCF Code of Conduct Committee](https://www.cncf.io/conduct/committee/) to submit your report. For more detailed instructions on how to submit a report, including how to submit a report anonymously, please see our [Incident Resolution Procedures](https://github.com/cncf/foundation/blob/main/code-of-conduct/coc-incident-resolution-procedures.md). You can expect a response within three business days.
7492
75−### 1. Correction
93+For incidents occurring at CNCF event that is produced by the Linux Foundation, please contact <eventconduct@cncf.io>.
7694
77−**Community Impact**: Use of inappropriate language or other behavior deemed
78−unprofessional or unwelcome in the community.
95+## Frequently asked questions
96+For more information about this Code of Conduct, please see the [CNCF Code of Conduct Frequently Asked Questions](https://www.cncf.io/conduct/faq/).
7997
80−**Consequence**: A private, written warning from community leaders, providing
81−clarity around the nature of the violation and an explanation of why the
82−behavior was inappropriate. A public apology may be requested.
83−
84−### 2. Warning
85−
86−**Community Impact**: A violation through a single incident or series of
87−actions.
88−
89−**Consequence**: A warning with consequences for continued behavior. No
90−interaction with the people involved, including unsolicited interaction with
91−those enforcing the Code of Conduct, for a specified period of time. This
92−includes avoiding interactions in community spaces as well as external channels
93−like social media. Violating these terms may lead to a temporary or permanent
94−ban.
95−
96−### 3. Temporary Ban
97−
98−**Community Impact**: A serious violation of community standards, including
99−sustained inappropriate behavior.
100−
101−**Consequence**: A temporary ban from any sort of interaction or public
102−communication with the community for a specified period of time. No public or
103−private interaction with the people involved, including unsolicited interaction
104−with those enforcing the Code of Conduct, is allowed during this period.
105−Violating these terms may lead to a permanent ban.
106−
107−### 4. Permanent Ban
108−
109−**Community Impact**: Demonstrating a pattern of violation of community
110−standards, including sustained inappropriate behavior, harassment of an
111−individual, or aggression toward or disparagement of classes of individuals.
112−
113−**Consequence**: A permanent ban from any sort of public interaction within the
114−community.
98+## Enforcement
11599
116−## Attribution
100+Upon review and investigation of a reported incident, the CoC response team that has jurisdiction will determine what action is appropriate based on this Code of Conduct and its related documentation.
117101
118−This Code of Conduct is adapted from the [Contributor Covenant][homepage],
119−version 2.1, available at
120−[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
102+For information about which Code of Conduct incidents are handled by project leadership, which incidents are handled by the CNCF Code of Conduct Committee, and which incidents are handled by the Linux Foundation (including its events team), see our [Jurisdiction Policy](https://github.com/cncf/foundation/blob/main/code-of-conduct/coc-committee-jurisdiction-policy.md).
121103
122−Community Impact Guidelines were inspired by
123−[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
104+## Amendments
124105
125−For answers to common questions about this code of conduct, see the FAQ at
126−[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
127−[https://www.contributor-covenant.org/translations][translations].
106+Consistent with the CNCF Charter, any substantive changes to this Code of Conduct must be approved by the Technical Oversight Committee.
128107
129−[homepage]: https://www.contributor-covenant.org
130−[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
131−[Mozilla CoC]: https://github.com/mozilla/diversity
132−[FAQ]: https://www.contributor-covenant.org/faq
133−[translations]: https://www.contributor-covenant.org/translations
108+## Acknowledgements
134109
110+This Code of Conduct is adapted from the Contributor Covenant
111+(http://contributor-covenant.org), version 2.0 available at
112+http://contributor-covenant.org/version/2/0/code_of_conduct/
DCO.mdnew file+34
@@ -0,0 +1,34 @@
1+Developer Certificate of Origin
2+Version 1.1
3+
4+Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
5+
6+Everyone is permitted to copy and distribute verbatim copies of this
7+license document, but changing it is not allowed.
8+
9+
10+Developer's Certificate of Origin 1.1
11+
12+By making a contribution to this project, I certify that:
13+
14+(a) The contribution was created in whole or in part by me and I
15+ have the right to submit it under the open source license
16+ indicated in the file; or
17+
18+(b) The contribution is based upon previous work that, to the best
19+ of my knowledge, is covered under an appropriate open source
20+ license and I have the right under that license to submit that
21+ work with modifications, whether created in whole or in part
22+ by me, under the same open source license (unless I am
23+ permitted to submit under a different license), as indicated
24+ in the file; or
25+
26+(c) The contribution was provided directly to me by some other
27+ person who certified (a), (b) or (c) and I have not modified
28+ it.
29+
30+(d) I understand and agree that this project and the contribution
31+ are public and that a record of the contribution (including all
32+ personal information I submit with it, including my sign-off) is
33+ maintained indefinitely and may be redistributed consistent with
34+ this project or the open source license(s) involved.
MAINTAINERS+2−5
@@ -1,5 +1,2 @@
1−Joel Speed <joel@oauth2-proxy.dev> (@JoelSpeed)
2−Nick Meves <nick@oauth2-proxy.dev> (@NickMeves)
3−Braunson <braunson@oauth2-proxy.dev> (@braunsonm)
4−Jan Larwig <jan@oauth2-proxy.dev> (@tuunit)
5−Koen van Zuijlen <koen@oauth2-proxy.dev> (@kvanzuijlen)
1+
2+Moved to https://github.com/oauth2-proxy/oauth2-proxy/blob/master/MAINTAINERS.md
MAINTAINERS.mdnew file+33
@@ -0,0 +1,33 @@
1+# Maintainers
2+
3+The table below lists all current maintainers for the oauth2-proxy as defined
4+by our [project governance](GOVERNANCE.md).
5+
6+| Name | GitHub Handle | Domains of reponsibility | Email Alias | Affiliation |
7+| ---------------- | ------------------------------------------------------ | ------------------------ | -------------------------- | ----------- |
8+| Joel Speed | [@JoelSpeed](https://github.com/joelspeed) | Governance, Core | joel@oauth2-proxy.dev | Red Hat |
9+| Jan Larwig | [@tuunit](https://github.com/tuunit) | Governance, Core | jan@oauth2-proxy.dev | IONOS Cloud |
10+| JJ Łakis | [@jjlakis](https://github.com/jjlakis) | Provider | jj@oauth2-proxy.dev | - |
11+| Koen van Zuijlen | [@kvanzuijlen](https://github.com/kvanzuijlen) | CI | koen@oauth2-proxy.dev | - |
12+| Pierluigi Lenoci | [@pierluigilenoci](https://github.com/pierluigilenoci) | Helm | pierluigi@oauth2-proxy.dev | SAP |
13+
14+## Emeritus Maintainers
15+
16+We would like to highlight that this project does have prior maintainers and
17+core contributors that, if they so wished, could (and should) be granted the
18+status of emeritus maintainers.
19+
20+| Name | GitHub Handle |
21+| ------------- | ------------------------------------------------------ |
22+| Nick Meves | [@NickMeves](https://github.com/NickMeves) |
23+| Braunson | [@braunsonm](https://github.com/braunsonm) |
24+| Henry Jenkins | [@steakunderscore](https://github.com/steakunderscore) |
25+
26+
27+## Security Response Team and GitHub Organization Owners
28+
29+The following maintainers are members of the security response team and owners
30+of the GitHub organization.
31+
32+- Joel Speed
33+- Jan Larwig
README.md+31−16
@@ -1,22 +1,24 @@
11[![Continuous Integration](https://github.com/oauth2-proxy/oauth2-proxy/actions/workflows/ci.yml/badge.svg)](https://github.com/oauth2-proxy/oauth2-proxy/actions/workflows/ci.yml)
2−[![Go Report Card](https://goreportcard.com/badge/github.com/oauth2-proxy/oauth2-proxy)](https://goreportcard.com/report/github.com/oauth2-proxy/oauth2-proxy)
3−[![GoDoc](https://godoc.org/github.com/oauth2-proxy/oauth2-proxy?status.svg)](https://godoc.org/github.com/oauth2-proxy/oauth2-proxy)
2+[![Go Report Card](https://goreportcard.com/badge/github.com/oauth2-proxy/oauth2-proxy)](https://goreportcard.com/report/github.com/oauth2-proxy/oauth2-proxy/v7)
3+[![GoDoc](https://godoc.org/github.com/oauth2-proxy/oauth2-proxy?status.svg)](https://godoc.org/github.com/oauth2-proxy/oauth2-proxy/v7)
44[![MIT licensed](https://img.shields.io/badge/license-MIT-blue.svg)](./LICENSE)
5−[![Maintainability](https://api.codeclimate.com/v1/badges/a58ff79407212e2beacb/maintainability)](https://codeclimate.com/github/oauth2-proxy/oauth2-proxy/maintainability)
6−[![Test Coverage](https://api.codeclimate.com/v1/badges/a58ff79407212e2beacb/test_coverage)](https://codeclimate.com/github/oauth2-proxy/oauth2-proxy/test_coverage)
5+[![Maintainability](https://qlty.sh/gh/oauth2-proxy/projects/oauth2-proxy/maintainability.svg)](https://qlty.sh/gh/oauth2-proxy/projects/oauth2-proxy)
6+[![Code Coverage](https://qlty.sh/gh/oauth2-proxy/projects/oauth2-proxy/coverage.svg)](https://qlty.sh/gh/oauth2-proxy/projects/oauth2-proxy)
7+[![OpenSSF Scorecard](https://api.scorecard.dev/projects/github.com/oauth2-proxy/oauth2-proxy/badge)](https://scorecard.dev/viewer/?uri=github.com/oauth2-proxy/oauth2-proxy)
8+[![OpenSSF Best Practices](https://www.bestpractices.dev/projects/11223/badge)](https://www.bestpractices.dev/projects/11223)
79[![FOSSA Status](https://app.fossa.com/api/projects/git%2Bgithub.com%2Foauth2-proxy%2Foauth2-proxy.svg?type=shield)](https://app.fossa.com/projects/git%2Bgithub.com%2Foauth2-proxy%2Foauth2-proxy?ref=badge_shield)
810
911![OAuth2 Proxy](docs/static/img/logos/OAuth2_Proxy_horizontal.svg)
1012
11−OAuth2-Proxy is a flexible, open-source tool that can act as either a standalone reverse proxy or a middleware component integrated into existing reverse proxy or load balancer setups. It provides a simple and secure way to protect your web applications with OAuth2 / OIDC authentication. As a reverse proxy, it intercepts requests to your application and redirects users to an OAuth2 provider for authentication. As a middleware, it can be seamlessly integrated into your existing infrastructure to handle authentication for multiple applications.
13+OAuth2 Proxy is a flexible, open-source tool that can act as either a standalone reverse proxy or a middleware component integrated into existing reverse proxy or load balancer setups. It provides a simple and secure way to protect your web applications with OAuth2 / OIDC authentication. As a reverse proxy, it intercepts requests to your application and redirects users to an OAuth2 provider for authentication. As a middleware, it can be seamlessly integrated into your existing infrastructure to handle authentication for multiple applications.
1214
13−OAuth2-Proxy supports a lot of OAuth2 as well as OIDC providers. Either through a generic OIDC client or a specific implementation for Google, Microsoft Entra ID, GitHub, login.gov and others. Through specialised provider implementations oauth2-proxy can extract more details about the user like preferred usernames and groups. Those details can then be forwarded as HTTP headers to your upstream applications.
15+OAuth2 Proxy supports a lot of OAuth2 as well as OIDC providers. Either through a generic OIDC client or a specific implementation for Google, Microsoft Entra ID, GitHub, login.gov and others. Through specialised provider implementations oauth2-proxy can extract more details about the user like preferred usernames and groups. Those details can then be forwarded as HTTP headers to your upstream applications.
1416
1517![Simplified Architecture](docs/static/img/simplified-architecture.svg)
1618
1719## Get Started
1820
19−OAuth2-Proxy's [Installation Docs](https://oauth2-proxy.github.io/oauth2-proxy/installation) cover how to install and configure your setup. Additionally you can take a further look at the [example setup files](https://github.com/oauth2-proxy/oauth2-proxy/tree/master/contrib/local-environment).
21+OAuth2 Proxy's [Installation Docs](https://oauth2-proxy.github.io/oauth2-proxy/installation) cover how to install and configure your setup. Additionally you can take a further look at the [example setup files](https://github.com/oauth2-proxy/oauth2-proxy/tree/master/contrib/local-environment).
2022
2123## Releases
2224
@@ -35,24 +37,26 @@ Since 2023-11-18 we build nightly images directly from the `master` branch and p
3537These images are considered unstable and therefore should **NOT** be used for production purposes unless you know what you're doing.
3638
3739## Sponsors
40+Would you like to sponsor the project then please contact us at [sponsors@oauth2-proxy.dev](mailto:sponsors@oauth2-proxy.dev)
3841
39−![Microsoft](https://upload.wikimedia.org/wikipedia/commons/9/96/Microsoft_logo_%282012%29.svg)
40−Microsoft Azure credits for open source projects
42+![SAP](https://avatars.githubusercontent.com/u/2531208?s=300&v=4)
4143
42−Would you like to sponsor the project then please contact us at [sponsors@oauth2-proxy.dev](mailto:sponsors@oauth2-proxy.dev)
44+SAP Open Source Program
45+
46+## Former Sponsors
47+![Microsoft](https://avatars.githubusercontent.com/u/6154722?s=100&v=4)
48+
49+Microsoft Azure credits for open source projects
4350
4451## Getting Involved
4552[![Slack](https://img.shields.io/badge/slack-Gopher_%23oauth2--proxy-red?logo=slack)](https://gophers.slack.com/archives/CM2RSS25N)
4653
4754Join the #oauth2-proxy [Slack channel](https://gophers.slack.com/archives/CM2RSS25N) to chat with other users of oauth2-proxy or reach out to the maintainers directly. Use the [public invite link](https://invite.slack.golangbridge.org/) to get an invite for the Gopher Slack space.
4855
49−OAuth2-Proxy is a community-driven project. We rely on the contribut️ions of our users to continually improve it. While review times can vary, we appreciate your patience and understanding. As a volunteer-driven project, we strive to keep this project stable and might take longer to merge changes.
56+OAuth2 Proxy is a community-driven project. We rely on the contribut️ions of our users to continually improve it. While review times can vary, we appreciate your patience and understanding. As a volunteer-driven project, we strive to keep this project stable and might take longer to merge changes.
5057
5158If you want to contribute to the project. Please see our [Contributing](https://oauth2-proxy.github.io/oauth2-proxy/community/contribution) guide.
5259
53−Who uses OAuth2-Proxy? Have a look at our new [ADOPTERS](ADOPTERS.md) file and
54−feel free to open a PR to add your organisation.
55−
5660Thanks to all the people who already contributed ❤
5761
5862<a href="https://github.com/oauth2-proxy/oauth2-proxy/graphs/contributors">
@@ -66,7 +70,7 @@ Made with [contrib.rocks](https://contrib.rocks).
6670
6771If you believe you have found a vulnerability within OAuth2 Proxy or any of its dependencies, please do **NOT** open an issue or PR on GitHub, please do **NOT** post any details publicly.
6872
69−Security disclosures **MUST** be done in private. If you have found an issue that you would like to bring to the attention of the maintainers, please compose an email and send it to the list of people listed in our [MAINTAINERS](MAINTAINERS) file.
73+Security disclosures **MUST** be done in private. If you have found an issue that you would like to bring to the attention of the maintainers, please compose an email and send it to the list of people listed in our [MAINTAINERS.md](MAINTAINERS.md) file.
7074
7175For more details read our full [Security Docs](https://oauth2-proxy.github.io/oauth2-proxy/community/security#security-disclosures)
7276
@@ -82,9 +86,20 @@ See [open redirect vulnerability](https://github.com/oauth2-proxy/oauth2-proxy/s
8286
8387**2020-03-29:** This project was formerly hosted as `pusher/oauth2_proxy` but has been renamed to `oauth2-proxy/oauth2-proxy`. Going forward, all images shall be available at `quay.io/oauth2-proxy/oauth2-proxy` and binaries will be named `oauth2-proxy`.
8488
89+## Code of Conduct
90+Participation in the OAuth2 Proxy project is governed by the [CNCF Code of Conduct](CODE_OF_CONDUCT.md).
91+
8592## License
8693
87−OAuth2-Proxy is distributed under [The MIT License](LICENSE).
94+OAuth2 Proxy is distributed under [The MIT License](LICENSE).
8895
8996
9097[![FOSSA Status](https://app.fossa.com/api/projects/git%2Bgithub.com%2Foauth2-proxy%2Foauth2-proxy.svg?type=large)](https://app.fossa.com/projects/git%2Bgithub.com%2Foauth2-proxy%2Foauth2-proxy?ref=badge_large)
98+
99+## Trademarks
100+
101+OAuth2 Proxy is a [Cloud Native Computing Foundation](https://cncf.io) Sandbox project.
102+
103+![CNCF](https://www.cncf.io/wp-content/uploads/2023/04/cncf-main-site-logo.svg)
104+
105+The Linux Foundation® (TLF) has registered trademarks and uses trademarks. For a list of TLF trademarks, see [Trademark Usage](https://www.linuxfoundation.org/legal/trademark-usage).
docs/docs/community/contribution.md+3−3
@@ -39,7 +39,7 @@ For starting oauth2-proxy locally open the debugging tab and create the `launch.
3939 "version": "0.2.0",
4040 "configurations": [
4141 {
42− "name": "Launch OAuth2-Proxy with Dex",
42+ "name": "Launch OAuth2 Proxy with Dex",
4343 "type": "go",
4444 "request": "launch",
4545 "mode": "auto",
@@ -52,7 +52,7 @@ For starting oauth2-proxy locally open the debugging tab and create the `launch.
5252 ]
5353 },
5454 {
55− "name": "Launch OAuth2-Proxy with Keycloak",
55+ "name": "Launch OAuth2 Proxy with Keycloak",
5656 "type": "go",
5757 "request": "launch",
5858 "mode": "auto",
@@ -85,7 +85,7 @@ The username and password for all setups is usually `admin@example.com` and `pas
8585
8686The docker compose setups expose the services with a dynamic reverse DNS resolver: localtest.me
8787
88−- OAuth2-Proxy: http://oauth2-proxy.localtest.me:4180
88+- OAuth2 Proxy: http://oauth2-proxy.localtest.me:4180
8989- Upstream: http://httpbin.localtest.me:8080
9090- Dex: http://dex.localtest.me:5556
9191
docs/docs/community/security.md+1−1
@@ -21,7 +21,7 @@ any details publicly.
2121Security disclosures MUST be done in private.
2222If you have found an issue that you would like to bring to the attention of the
2323maintenance team for OAuth2 Proxy, please compose an email and send it to the
24−list of maintainers in our [MAINTAINERS](https://github.com/oauth2-proxy/oauth2-proxy/blob/master/MAINTAINERS) file.
24+list of maintainers in our [MAINTAINERS.md](https://github.com/oauth2-proxy/oauth2-proxy/blob/master/MAINTAINERS.md) file.
2525
2626Please include as much detail as possible.
2727Ideally, your disclosure should include:
docs/docs/configuration/sessions.md+2−2
@@ -64,9 +64,9 @@ the refresh flow to get a new Access-Token. If it is longer, it might be that th
6464expired.
6565
6666The "cookie-refresh" value controls when OAuth2 Proxy tries to refresh an Access-Token. If it is set to "0", the
67−Access-Token will never be refreshed, even if it is already expired and a valid Refresh-Token is available. If set, OAuth2-Proxy will
67+Access-Token will never be refreshed, even if it is already expired and a valid Refresh-Token is available. If set, OAuth2 Proxy will
6868refresh the Access-Token after this many seconds whether it is still valid or not. According to the official OAuth2.0 specification
69−Access-Tokens are not required to follow a specific format. Therefore OAuth2-Proxy cannot check for any expiry date without an
69+Access-Tokens are not required to follow a specific format. Therefore OAuth2 Proxy cannot check for any expiry date without an
7070introspection endpoint. If an Access-Token expires and you have not set a corresponding "cookie-refresh" value, you will likely
7171encounter expiry issues.
7272
docs/docs/welcome.md+10
@@ -21,3 +21,13 @@ A list of changes can be seen in the [CHANGELOG](https://github.com/oauth2-proxy
2121## Architecture
2222
2323![OAuth2 Proxy Architecture](/img/simplified-architecture.svg)
24+
25+
26+## Cloud Native Computing Foundation
27+
28+OAuth2 Proxy is a [Cloud Native Computing Foundation](https://cncf.io) Sandbox project.
29+
30+![CNCF](https://www.cncf.io/wp-content/uploads/2023/04/cncf-main-site-logo.svg)
31+
32+The Linux Foundation® (TLF) has registered trademarks and uses trademarks. For a list of TLF trademarks, see [Trademark Usage](https://www.linuxfoundation.org/legal/trademark-usage).
33+
docs/docusaurus.config.js+1−1
@@ -118,7 +118,7 @@ const config = {
118118 },
119119 footer: {
120120 style: 'dark',
121− copyright: `Copyright © ${new Date().getFullYear()} OAuth2 Proxy.`,
121+ copyright: `Copyright © ${new Date().getFullYear()} OAuth2 Proxy a Series of LF Projects, LLC.<br>For website terms of use, trademark policy and other project policies please see lfprojects.org/policies/`,
122122 },
123123 prism: {
124124 theme: prismThemes.github,
docs/versioned_docs/version-7.14.x/community/contribution.md+3−3
@@ -39,7 +39,7 @@ For starting oauth2-proxy locally open the debugging tab and create the `launch.
3939 "version": "0.2.0",
4040 "configurations": [
4141 {
42− "name": "Launch OAuth2-Proxy with Dex",
42+ "name": "Launch OAuth2 Proxy with Dex",
4343 "type": "go",
4444 "request": "launch",
4545 "mode": "auto",
@@ -52,7 +52,7 @@ For starting oauth2-proxy locally open the debugging tab and create the `launch.
5252 ]
5353 },
5454 {
55− "name": "Launch OAuth2-Proxy with Keycloak",
55+ "name": "Launch OAuth2 Proxy with Keycloak",
5656 "type": "go",
5757 "request": "launch",
5858 "mode": "auto",
@@ -85,7 +85,7 @@ The username and password for all setups is usually `admin@example.com` and `pas
8585
8686The docker compose setups expose the services with a dynamic reverse DNS resolver: localtest.me
8787
88−- OAuth2-Proxy: http://oauth2-proxy.localtest.me:4180
88+- OAuth2 Proxy: http://oauth2-proxy.localtest.me:4180
8989- Upstream: http://httpbin.localtest.me:8080
9090- Dex: http://dex.localtest.me:5556
9191
docs/versioned_docs/version-7.14.x/community/security.md+1−1
@@ -21,7 +21,7 @@ any details publicly.
2121Security disclosures MUST be done in private.
2222If you have found an issue that you would like to bring to the attention of the
2323maintenance team for OAuth2 Proxy, please compose an email and send it to the
24−list of maintainers in our [MAINTAINERS](https://github.com/oauth2-proxy/oauth2-proxy/blob/master/MAINTAINERS) file.
24+list of maintainers in our [MAINTAINERS.md](https://github.com/oauth2-proxy/oauth2-proxy/blob/master/MAINTAINERS.md) file.
2525
2626Please include as much detail as possible.
2727Ideally, your disclosure should include:
docs/versioned_docs/version-7.14.x/configuration/sessions.md+2−2
@@ -64,9 +64,9 @@ the refresh flow to get a new Access-Token. If it is longer, it might be that th
6464expired.
6565
6666The "cookie-refresh" value controls when OAuth2 Proxy tries to refresh an Access-Token. If it is set to "0", the
67−Access-Token will never be refreshed, even if it is already expired and a valid Refresh-Token is available. If set, OAuth2-Proxy will
67+Access-Token will never be refreshed, even if it is already expired and a valid Refresh-Token is available. If set, OAuth2 Proxy will
6868refresh the Access-Token after this many seconds whether it is still valid or not. According to the official OAuth2.0 specification
69−Access-Tokens are not required to follow a specific format. Therefore OAuth2-Proxy cannot check for any expiry date without an
69+Access-Tokens are not required to follow a specific format. Therefore OAuth2 Proxy cannot check for any expiry date without an
7070introspection endpoint. If an Access-Token expires and you have not set a corresponding "cookie-refresh" value, you will likely
7171encounter expiry issues.
7272
docs/versioned_docs/version-7.14.x/welcome.md+9
@@ -21,3 +21,12 @@ A list of changes can be seen in the [CHANGELOG](https://github.com/oauth2-proxy
2121## Architecture
2222
2323![OAuth2 Proxy Architecture](/img/simplified-architecture.svg)
24+
25+## Cloud Native Computing Foundation
26+
27+OAuth2 Proxy is a [Cloud Native Computing Foundation](https://cncf.io) Sandbox project.
28+
29+![CNCF](https://www.cncf.io/wp-content/uploads/2023/04/cncf-main-site-logo.svg)
30+
31+The Linux Foundation® (TLF) has registered trademarks and uses trademarks. For a list of TLF trademarks, see [Trademark Usage](https://www.linuxfoundation.org/legal/trademark-usage).
32+