You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "ZhouKang (Jira)" <ji...@apache.org> on 2019/10/29 12:39:00 UTC
[jira] [Commented] (KYLIN-4139) Compatible old user security xml
config when user upgrate new kylin version
[ https://issues.apache.org/jira/browse/KYLIN-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16961967#comment-16961967 ]
ZhouKang commented on KYLIN-4139:
---------------------------------
I notice that, in KYLIN-3531 (https://issues.apache.org/jira/browse/KYLIN-3531) save uppercase username in metadata,
and then in KYLIN-4103 (https://issues.apache.org/jira/browse/KYLIN-4103) make user name in granting operation of project is case insensitive
but in this issue, username in metadata is original.
what is the standard rule for username?
> Compatible old user security xml config when user upgrate new kylin version
> ----------------------------------------------------------------------------
>
> Key: KYLIN-4139
> URL: https://issues.apache.org/jira/browse/KYLIN-4139
> Project: Kylin
> Issue Type: Improvement
> Reporter: luguosheng
> Assignee: luguosheng
> Priority: Major
> Fix For: v3.0.0-beta
>
>
>
> Forward compatible
> # when user config 'spring.profiles.active=testing', sync old version user metadata with user config in kylinSecurity.xml
> Other improvement
> # Remove the logic of auto trans new user name to uppercase
--
This message was sent by Atlassian Jira
(v8.3.4#803005)