Skip to content
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

Integrate OAuth Authorization into Strimzi #2428

Closed
ppatierno opened this issue Jan 20, 2020 · 3 comments · Fixed by #2432
Closed

Integrate OAuth Authorization into Strimzi #2428

ppatierno opened this issue Jan 20, 2020 · 3 comments · Fixed by #2432

Comments

@ppatierno
Copy link
Member

ppatierno commented Jan 20, 2020

This issue is about integrating into Strimzi the OAuth Authorization provided by Keycloak.
It's related to this strimzi/strimzi-kafka-oauth#24 and providing the right CRD additions into the Kafka resource for enabling this type of authorization (other than the simple one already in place).
Authorization should have a new keycloak type and the related configuration parameters in the CRD.
Following a proposal for that.

# ...
authorization:
  type: keycloak
  tokenEndpointUri: <URL of the Keycloak's token endpoint>
  clientId: <A client id of the OAuth client definition in Keycloak>
  delegateToKafkaAcls: false #if fallback to Simple authz if no access provided by Keycloak
  tlsTrustedCertificates:
     - secretName: oauth-server-cert
       certificate: ca.crt
  disableTlsHostnameVerification: false
  superUsers:
    - Alice
    - CN=Bob
@ppatierno
Copy link
Member Author

@mstruk @scholzj any thoughts?

@mstruk
Copy link
Contributor

mstruk commented Jan 20, 2020

Yes, looks good.
Maybe we should also support

 clientSecret:
   secretName: my-cluster-oauth
   key: clientSecret

But currently KeycloakRBACAuthorizer doesn't support it, so maybe we add it later.

@ppatierno
Copy link
Member Author

I forgot superUsers field, just added.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants