Skip to content

Conversation

@scholzj
Copy link
Member

@scholzj scholzj commented Sep 10, 2025

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

Signed-off-by: Jakub Scholz <www@scholzj.com>
@scholzj scholzj changed the title Deprecated and remove the type: oauth and type: keycloak APIs Deprecate and remove the type: oauth and type: keycloak APIs Sep 10, 2025
Copy link
Contributor

@tinaselenge tinaselenge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM :)

Copy link
Member

@im-konge im-konge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks.

Copy link
Member

@see-quick see-quick left a 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.

Copy link
Contributor

@PaulRMellor PaulRMellor left a 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.


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.
Copy link
Contributor

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?

Copy link
Member Author

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.

### 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.
Copy link
Contributor

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?

Copy link
Member Author

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.

Copy link

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

Copy link
Member Author

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.

scholzj and others added 2 commits September 11, 2025 20:16
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>
Copy link
Member

@ppatierno ppatierno left a 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>
@scholzj
Copy link
Member Author

scholzj commented Sep 14, 2025

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>
@scholzj scholzj merged commit 0f336b5 into strimzi:main Sep 16, 2025
1 check passed
@scholzj scholzj deleted the deprecated-type-oauth-and-type-keycloak-apis branch September 16, 2025 17:28
im-konge added a commit to im-konge/proposals that referenced this pull request Sep 19, 2025
…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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants