Stephen Lecrenski

Got it working with this code. Bit unelegant but works even for horizontal scrolling. ```html ... col1header col2header {{...}} {{...}} ``` ```javascript function updateInnerCollection() { ... var $thead = repeatContainer[0].parentNode.children[0];...

Understood on requirement to write custom authorizer. Plan on using group prefix naming conventions to authorize requests for simplicity of authorization with sufficient level of granularity defined in group suffix...

Yes I have confirmed I am using the Introspection Endpoint. Please find the filtered configuration below. ```bash listener.name.clientoap.sasl.enabled.mechanisms=PLAIN listener.name.clientoap.oauthbearer.connections.max.reauth.ms=3600000 listener.name.clientoap.plain.sasl.server.callback.handler.class=io.strimzi.kafka.oauth.server.plain.JaasServerOauthOverPlainValidatorCallbackHandler listener.name.clientoap.plain.sasl.jaas.config=org.apache.kafka.common.security.plain.PlainLoginModule required \ oauth.client.id="{FILTERED}" \ oauth.client.secret="{FILTERED}" \ oauth.token.endpoint.uri="{FILTERED}" \ oauth.introspection.endpoint.uri="{FILTERED}"...

How does that help my requirement? I guess I could update the groups object in the OAuthKafkaPrincipal during initial authorization events in my custom authorizer. Hopefully it’s mutable. If not...

Ok so that did pickup the groups during authentication event. So I guess I can go with that for now. Seems a bit hacky tho..? Hopefully things will continue to...

Or you could completely ignore this. That works too. Last commit was about a year ago is this no longer maintained?