[jboss-jira] [JBoss JIRA] (WFLY-7661) Mark also ssl-session-cache-size and ssl-session-timeout attributes as deprecated in Undertow's https-listener

[Stuart Douglas (JIRA)]

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

Stuart Douglas moved JBEAP-7481 to WFLY-7661:
---------------------------------------------

              Project: WildFly  (was: JBoss Enterprise Application Platform)
                  Key: WFLY-7661  (was: JBEAP-7481)
             Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
          Component/s: Web (Undertow)
                           (was: Web (Undertow))
    Affects Version/s:     (was: 7.1.0.DR8)


> Mark also ssl-session-cache-size and ssl-session-timeout attributes as deprecated in Undertow's https-listener
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-7661
>                 URL: https://issues.jboss.org/browse/WFLY-7661
>             Project: WildFly
>          Issue Type: Bug
>          Components: Web (Undertow)
>            Reporter: Stuart Douglas
>            Assignee: Stuart Douglas
>
> Some of Undertow's https-listener attributes have been marked as deprecated recently due to the Elytron subsystem added into 7.1. Although there are still two attributes, that I think should be marked as deprecated but they have not been marked so yet. These are:
> {code}
>             "ssl-session-cache-size" => {
>                 "type" => INT,
>                 "description" => "The maximum number of active SSL sessions",
>                 "expressions-allowed" => true,
>                 "nillable" => true,
>                 "access-type" => "read-write",
>                 "storage" => "configuration",
>                 "restart-required" => "no-services"
>             },
>             "ssl-session-timeout" => {
>                 "type" => INT,
>                 "description" => "The timeout for SSL sessions, in seconds",
>                 "expressions-allowed" => true,
>                 "nillable" => true,
>                 "unit" => "SECONDS",
>                 "access-type" => "read-write",
>                 "storage" => "configuration",
>                 "restart-required" => "no-services"
>             },
> {code}
> Both can be set via Elytron ssl-context:
> {code}
> /subsystem=elytron/server-ssl-context=mytest:read-resource-description
> ...
>             "maximum-session-cache-size" => {
>                 "type" => INT,
>                 "description" => "The maximum number of SSL sessions to be cached.",
>                 "expressions-allowed" => true,
>                 "nillable" => true,
>                 "default" => 0,
>                 "access-type" => "read-write",
>                 "storage" => "configuration",
>                 "restart-required" => "resource-services"
>             },
> ...
>             "session-timeout" => {
>                 "type" => INT,
>                 "description" => "The timeout for SSL sessions.",
>                 "expressions-allowed" => true,
>                 "nillable" => true,
>                 "default" => 0,
>                 "access-type" => "read-write",
>                 "storage" => "configuration",
>                 "restart-required" => "resource-services"
>             },
> ...
> {code}



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