envoyproxy
[OAuth2] Timeline for graduation of OAuth2 filter to beta/GA
Title: Timeline for graduation of OAuth2 filter to beta/GA
Description:
OAuth2 filter documentation mentions that it is currently under active development. The extensions metadata specifies the status as alpha - is there a timeline or milestone by which this filter can be considered stable for production use? In other words, when is this expected to graduate to GA?
Also is there a plan to support additional grant types besides the authz code flow?
Relevant: https://github.com/envoyproxy/envoy/issues/14088
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions.
@derekargueta @snowp @kyessenov - Would you be able to provide the likely promotion timeline for this filter?
The criteria are listed here https://github.com/envoyproxy/envoy/blob/main/EXTENSION_POLICY.md#extension-stability-and-security-posture. The main signal for this extension is sufficient burn time in production. If an end-user can report on experience running it in production without issues, the other signals are mostly technical quality.
The criteria are listed here https://github.com/envoyproxy/envoy/blob/main/EXTENSION_POLICY.md#extension-stability-and-security-posture. The main signal for this extension is sufficient burn time in production. If an end-user can report on experience running it in production without issues, the other signals are mostly technical quality.
Serious users aren't ready to try it in production when they see the flag alpha. Aren't we in the chicken and egg conundrum?
@deva26 yes it is, but the first step needs to be done by the interested end-user to provide qualification. We cannot do that alone in OSS without production access.