[jboss-jira] [JBoss JIRA] (AS7-5134) Unable to not set key-alias for ssl

Tue Aug 14 18:00:17 EDT 2012

    [ https://issues.jboss.org/browse/AS7-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711583#comment-12711583 ] 

Brian Stansberry commented on AS7-5134:
---------------------------------------

If your configuration file uses the 1.0 or 1.1 xsd schema for the web subsystem and doesn't specify a key-alias, EAP will manually add "jboss" as the key-alias. When the configuration persists following any subsequent change, the schema version of the subsystem will be changed to 1.2 but key-alias="jboss" will be written to the file.  If the configuration file uses the 1.2 schema version and doesn't specify a key-alias, no key alias will be used.

This behavior preserves compatibility with previous releases (an old config will not suddenly have a change in behavior when an upgrade to 7.2 is done) while providing the desired behavior going forward.

> Unable to not set key-alias for ssl
> -----------------------------------
>
>                 Key: AS7-5134
>                 URL: https://issues.jboss.org/browse/AS7-5134
>             Project: Application Server 7
>          Issue Type: Enhancement
>          Components: Web
>    Affects Versions: 7.1.2.Final (EAP)
>            Reporter: Tomaz Cerar
>            Assignee: Tomaz Cerar
>             Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1
>
>
> when running in FIPS mode key-alias should not be set as this triggers exception as non FIPS complaint key managers are used.
> as key-alias has default value of 'jboss' it will always get set even if user does not define it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira