[
https://issues.jboss.org/browse/ELY-783?page=com.atlassian.jira.plugin.sy...
]
Yeray Borges commented on ELY-783:
----------------------------------
Verified using Bouncy Castle as security provider, which allows aliases in uppercase. SSL
works fine using this provider. That means alias-filter is case sensitive and that was the
intention since alias case sensitivity is dependent of the provider implementation.
Issue should be managed as documentation in this case.
alias-filter from Elytron key-store does not work for non-lower-case
alias with JKS
-----------------------------------------------------------------------------------
Key: ELY-783
URL:
https://issues.jboss.org/browse/ELY-783
Project: WildFly Elytron
Issue Type: Bug
Affects Versions: 1.1.0.Beta13
Reporter: Ondrej Lukas
Assignee: Yeray Borges
In case when {{alias-filter}} attribute from Elytron {{key-store}} references
non-lower-case alias (e.g. elytronAppServer) then SSL is not working. In case when this
alias is set to lower-case in alias-filter (e.g. elytronappserver), then SSL works
correctly.
It seems JKS always transforms aliases to lower-case (even if they are created with some
upper-case characters). However legacy security solution was able to use alias filter with
non-lower-case characters to assign key from JKS keystore (probably through some internal
{{.toLowerCase()}}).
In case it is intended to do not use alias-filter with some upper-case for JKS then this
issue can be changed to documentation issue. This is different behavior than was provided
by legacy solution.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)