[jboss-jira] [JBoss JIRA] (WFCORE-2795) Writing invalid value for cipher-suite-filter attribute of Elytron *-ssl-context should result in failure

Yeray Borges (JIRA) issues at jboss.org
Thu May 11 04:15:00 EDT 2017


     [ https://issues.jboss.org/browse/WFCORE-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yeray Borges moved JBEAP-10851 to WFCORE-2795:
----------------------------------------------

              Project: WildFly Core  (was: JBoss Enterprise Application Platform)
                  Key: WFCORE-2795  (was: JBEAP-10851)
             Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
          Component/s: Security
                           (was: Security)
                           (was: User Experience)
    Affects Version/s:     (was: 7.1.0.DR8)


> Writing invalid value for cipher-suite-filter attribute of Elytron *-ssl-context should result in failure
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: WFCORE-2795
>                 URL: https://issues.jboss.org/browse/WFCORE-2795
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Security
>            Reporter: Yeray Borges
>            Assignee: Yeray Borges
>              Labels: cipher-suite, error_handling, ssl, user_experience, validation
>
> Writing invalid value for {{cipher-suite-filter}} attribute of {{*-ssl-context}} results in {{"outcome" => "success"}} and requires reload. After reload there are errors in server log, but there is no notice in CLI. A user should be notified immediately that entered value is not correct -- the operation should fail.
> Furthermore, when an invalid combination of {{cipher-suite-filter}} and {{protocols}} is entered, the operation passes and there are errors in server log after reload only. Again, a user should be notified immediately that entered combination of values is not correct -- the operation should fail. Should I create separate JIRA issue for this?



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)


More information about the jboss-jira mailing list