THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
This page is meant as a template for writing a KIP. To create a KIP choose Tools->Copy on this page and modify with your content and replace the heading with the next KIP number and a description of your issue. Replace anything in italics with your own description.
Status
Current state: ["Under Discussion"] Accepted
Discussion thread: here
JIRA: Jira server ASF JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key KAFKA-5764
...
However, this may not be desired given how different operating system handle usernames, whereas where some are case-sensitive and some are case-insensitive. For example, Linux is case-sensitive and Windows is case-insensitive. To help with this issue, the rule can support to force the translated result to be all lower case.Reference
Proposed Changes
We propose to extend "sasl.kerberos.principal.to.local.rules" config rule format/syntax by supporting an optional "/L" (toLowerCase) at the end of the rule. Since usernames are locale insensitive strings, we propose to use Locale.ENGLISH for the case conversion
...
| Code Block |
|---|
If the source string is joe-qa-cl1/host@EXAMPLE.COM, the result will be joe-qa If the source string is JOE-QA-cl1/host@EXAMPLE.COM, the result will be joe-qa-upper If the source string is joe_user/host@EXAMPLE.COM, the result will be joe_user If the source string is JOE_USER/host@EXAMPLE.COM, the result will be joe_use |
...
However, it must be noted that this does not affect how pattern matches on input and therefore that will still be case-sensitive.
...