-
Notifications
You must be signed in to change notification settings - Fork 73
Deprecate and remove the type: oauth and type: keycloak APIs
#175
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecate and remove the type: oauth and type: keycloak APIs
#175
Conversation
Signed-off-by: Jakub Scholz <www@scholzj.com>
type: oauth and type: keycloak APIstype: oauth and type: keycloak APIs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM :)
113-deprecate-and-remove-oauth-authentication-and-authorization.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks.
113-deprecate-and-remove-oauth-authentication-and-authorization.md
Outdated
Show resolved
Hide resolved
113-deprecate-and-remove-oauth-authentication-and-authorization.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Make sense LGTM 👍 . Thanks for the proposal @scholzj. Just a few stylistic nits.
113-deprecate-and-remove-oauth-authentication-and-authorization.md
Outdated
Show resolved
Hide resolved
113-deprecate-and-remove-oauth-authentication-and-authorization.md
Outdated
Show resolved
Hide resolved
113-deprecate-and-remove-oauth-authentication-and-authorization.md
Outdated
Show resolved
Hide resolved
113-deprecate-and-remove-oauth-authentication-and-authorization.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. The proposed change retains support for OAuth (with type: custom option), while reducing the maintenance overhead. This seems like a good balance.
113-deprecate-and-remove-oauth-authentication-and-authorization.md
Outdated
Show resolved
Hide resolved
113-deprecate-and-remove-oauth-authentication-and-authorization.md
Outdated
Show resolved
Hide resolved
113-deprecate-and-remove-oauth-authentication-and-authorization.md
Outdated
Show resolved
Hide resolved
|
|
||
| This proposal suggests deprecating the `type: oauth` authentication and `type: keycloak` authorization from the Strimzi API and its removal in the [Strimzi `v1` CRD API](https://github.com/strimzi/proposals/pull/174). | ||
| The APIs will be replaced by `type: custom` authentication and authorization. | ||
| This proposal does not propose deprecating the Strimzi OAuth library subproject or not bundling it with the Strimzi container images. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we comment here on the anticipated future of the project in terms of maintenance?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added a note that the development and maintenance of the OAuth project continues as before.
113-deprecate-and-remove-oauth-authentication-and-authorization.md
Outdated
Show resolved
Hide resolved
113-deprecate-and-remove-oauth-authentication-and-authorization.md
Outdated
Show resolved
Hide resolved
113-deprecate-and-remove-oauth-authentication-and-authorization.md
Outdated
Show resolved
Hide resolved
113-deprecate-and-remove-oauth-authentication-and-authorization.md
Outdated
Show resolved
Hide resolved
| ### Documentation | ||
|
|
||
| The examples of using the `type: custom` configuration will be added to the documentation. | ||
| The existing documentation using the OAuth APIs should be removed while ensuring the things it covers are well documented in the OAuth library documentation/README. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we removing at deprecation phase or when we drop support as v1?
Would we need to consider any migration guidance?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should remove it right with the deprecation to not have new users start using it. We should also have some simple migration guide -> i.e. not covering every single option, just some high level pointing to the OAuth README for the more detailed docs on all options. I updated the proposal with it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The users having to manually migrate their configurations seems like a potential problem for users. We should maybe document a mapping table how each config option in Strimzi maps to the JAAS config parameter, e.g. clientId -> oauth.client.id
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That would make sense I guess, yes. I added the mapping table to the proposal.
113-deprecate-and-remove-oauth-authentication-and-authorization.md
Outdated
Show resolved
Hide resolved
Co-authored-by: PaulRMellor <47596553+PaulRMellor@users.noreply.github.com> Co-authored-by: Lukáš Král <53821852+im-konge@users.noreply.github.com> Co-authored-by: Maros Orsak <maros.orsak159@gmail.com> Signed-off-by: Jakub Scholz <www@scholzj.com>
Signed-off-by: Jakub Scholz <www@scholzj.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Signed-off-by: Jakub Scholz <www@scholzj.com>
|
This proposal has now 4 binding and 2 non-binding +1 votes. I will keep it open until Tuesday EOB to see if there are any more comments. |
Signed-off-by: Jakub Scholz <www@scholzj.com>
…imzi#175) * Deprecated the type: oauth and type: keycloak APIs Signed-off-by: Jakub Scholz <www@scholzj.com> * Apply suggestions from code review Co-authored-by: PaulRMellor <47596553+PaulRMellor@users.noreply.github.com> Co-authored-by: Lukáš Král <53821852+im-konge@users.noreply.github.com> Co-authored-by: Maros Orsak <maros.orsak159@gmail.com> Signed-off-by: Jakub Scholz <www@scholzj.com> * Review comments LK, PM, TS Signed-off-by: Jakub Scholz <www@scholzj.com> * Review comments MS Signed-off-by: Jakub Scholz <www@scholzj.com> * Update index Signed-off-by: Jakub Scholz <www@scholzj.com> --------- Signed-off-by: Jakub Scholz <www@scholzj.com> Co-authored-by: PaulRMellor <47596553+PaulRMellor@users.noreply.github.com> Co-authored-by: Lukáš Král <53821852+im-konge@users.noreply.github.com> Co-authored-by: Maros Orsak <maros.orsak159@gmail.com>
This proposal suggests deprecating the
type: oauthauthentication andtype: keycloakauthorization from the Strimzi API and its removal in the Strimziv1CRD API. The APIs will be replaced bytype: customauthentication and authorization. This proposal does not propose deprecating the Strimzi OAuth library subproject or not bundling it with the Strimzi container images.