[JBoss JIRA] (WFLY-7453) Resource description should not contain javadoc style links
by Martin Švehla (JIRA)
[ https://issues.jboss.org/browse/WFLY-7453?page=com.atlassian.jira.plugin.... ]
Martin Švehla updated WFLY-7453:
--------------------------------
Labels: user_experience (was: )
> Resource description should not contain javadoc style links
> -----------------------------------------------------------
>
> Key: WFLY-7453
> URL: https://issues.jboss.org/browse/WFLY-7453
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Reporter: Martin Švehla
> Assignee: Jason Greene
> Priority: Minor
> Labels: user_experience
>
> Description of the attribute {{date-format}} in
> {code}
> /core-service=management/access=audit/json-formatter=json-formatter
> {code}
> has following description:
> {panel}
> The date format to use as understood by \{@link java.text.SimpleDateFormat}. Will be ignored if include-date=\"false\".
> {panel}
> The description string shouldn't contain javadoc style @link
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7453) Resource description should not contain javadoc style links
by Martin Švehla (JIRA)
[ https://issues.jboss.org/browse/WFLY-7453?page=com.atlassian.jira.plugin.... ]
Martin Švehla moved JBEAP-6808 to WFLY-7453:
--------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-7453 (was: JBEAP-6808)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Server
(was: Server)
(was: User Experience)
> Resource description should not contain javadoc style links
> -----------------------------------------------------------
>
> Key: WFLY-7453
> URL: https://issues.jboss.org/browse/WFLY-7453
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Reporter: Martin Švehla
> Assignee: Jason Greene
> Priority: Minor
>
> Description of the attribute {{date-format}} in
> {code}
> /core-service=management/access=audit/json-formatter=json-formatter
> {code}
> has following description:
> {panel}
> The date format to use as understood by \{@link java.text.SimpleDateFormat}. Will be ignored if include-date=\"false\".
> {panel}
> The description string shouldn't contain javadoc style @link
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFCORE-1921) Problem with capability-reference to resource whose name is number with ZERO(s) prefix.
by Hynek Švábek (JIRA)
Hynek Švábek created WFCORE-1921:
------------------------------------
Summary: Problem with capability-reference to resource whose name is number with ZERO(s) prefix.
Key: WFCORE-1921
URL: https://issues.jboss.org/browse/WFCORE-1921
Project: WildFly Core
Issue Type: Bug
Components: CLI
Reporter: Hynek Švábek
Problem with resources which name contains only NUMBERS.
Particularly the number which beginning with ZERO(s).
*Scenario*
* I have resources which name contains only numbers with ZERO(s) prefix
* I want set capability-reference to it
* e.g. /subsystem=elytron/aggregate-role-mapper001=aggregateRoleMapper:add(role-mappers=[001,111])
*Actual result*
{code}
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0369: Required capabilities are not available:
org.wildfly.security.role-mapper.1; There are no known registration points which can provide this capability.",
"rolled-back" => true
}
{code}
*Expected result*
{code}
Success
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFCORE-1921) Problem with capability-reference to resource whose name is number with ZERO(s) prefix.
by Hynek Švábek (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1921?page=com.atlassian.jira.plugi... ]
Hynek Švábek reassigned WFCORE-1921:
------------------------------------
Assignee: Jean-Francois Denise
> Problem with capability-reference to resource whose name is number with ZERO(s) prefix.
> ---------------------------------------------------------------------------------------
>
> Key: WFCORE-1921
> URL: https://issues.jboss.org/browse/WFCORE-1921
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Reporter: Hynek Švábek
> Assignee: Jean-Francois Denise
>
> Problem with resources which name contains only NUMBERS.
> Particularly the number which beginning with ZERO(s).
> *Scenario*
> * I have resources which name contains only numbers with ZERO(s) prefix
> * I want set capability-reference to it
> * e.g. /subsystem=elytron/aggregate-role-mapper001=aggregateRoleMapper:add(role-mappers=[001,111])
> *Actual result*
> {code}
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0369: Required capabilities are not available:
> org.wildfly.security.role-mapper.1; There are no known registration points which can provide this capability.",
> "rolled-back" => true
> }
> {code}
> *Expected result*
> {code}
> Success
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7452) Insufficient failure-description for filters of Elytron configurable-sasl-server-factory
by Ondrej Lukas (JIRA)
Ondrej Lukas created WFLY-7452:
----------------------------------
Summary: Insufficient failure-description for filters of Elytron configurable-sasl-server-factory
Key: WFLY-7452
URL: https://issues.jboss.org/browse/WFLY-7452
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Ondrej Lukas
Assignee: Darran Lofthouse
Priority: Minor
In case when both {{pattern-filter}} and {{predefined-filter}} are set in one Object in CLI command for {{filters}} of Elytron {{configurable-sasl-server-factory}} then it finishes with insufficient failure-description:
{code}
/subsystem=elytron/configurable-sasl-server-factory=someFactory:add(sasl-server-factory=global,filters=[{pattern-filter=(.*),predefined-filter=BINDING}])
{
"outcome" => "failed",
"failure-description" => "WFLYELY01014: Invalid [filters] definition.",
"rolled-back" => true
}
{code}
This failure-description is not wrong but it is also not helpful. Improve failure-description to say that only one of {{pattern-filter}} and {{predefined-filter}} can be set in one Object in list of filters.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7452) Insufficient failure-description for filters of Elytron configurable-sasl-server-factory
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/WFLY-7452?page=com.atlassian.jira.plugin.... ]
Ondrej Lukas updated WFLY-7452:
-------------------------------
Affects Version/s: 11.0.0.Alpha1
> Insufficient failure-description for filters of Elytron configurable-sasl-server-factory
> ----------------------------------------------------------------------------------------
>
> Key: WFLY-7452
> URL: https://issues.jboss.org/browse/WFLY-7452
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Priority: Minor
> Labels: user_experience
>
> In case when both {{pattern-filter}} and {{predefined-filter}} are set in one Object in CLI command for {{filters}} of Elytron {{configurable-sasl-server-factory}} then it finishes with insufficient failure-description:
> {code}
> /subsystem=elytron/configurable-sasl-server-factory=someFactory:add(sasl-server-factory=global,filters=[{pattern-filter=(.*),predefined-filter=BINDING}])
> {
> "outcome" => "failed",
> "failure-description" => "WFLYELY01014: Invalid [filters] definition.",
> "rolled-back" => true
> }
> {code}
> This failure-description is not wrong but it is also not helpful. Improve failure-description to say that only one of {{pattern-filter}} and {{predefined-filter}} can be set in one Object in list of filters.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7452) Insufficient failure-description for filters of Elytron configurable-sasl-server-factory
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/WFLY-7452?page=com.atlassian.jira.plugin.... ]
Ondrej Lukas updated WFLY-7452:
-------------------------------
Labels: user_experience (was: )
> Insufficient failure-description for filters of Elytron configurable-sasl-server-factory
> ----------------------------------------------------------------------------------------
>
> Key: WFLY-7452
> URL: https://issues.jboss.org/browse/WFLY-7452
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Priority: Minor
> Labels: user_experience
>
> In case when both {{pattern-filter}} and {{predefined-filter}} are set in one Object in CLI command for {{filters}} of Elytron {{configurable-sasl-server-factory}} then it finishes with insufficient failure-description:
> {code}
> /subsystem=elytron/configurable-sasl-server-factory=someFactory:add(sasl-server-factory=global,filters=[{pattern-filter=(.*),predefined-filter=BINDING}])
> {
> "outcome" => "failed",
> "failure-description" => "WFLYELY01014: Invalid [filters] definition.",
> "rolled-back" => true
> }
> {code}
> This failure-description is not wrong but it is also not helpful. Improve failure-description to say that only one of {{pattern-filter}} and {{predefined-filter}} can be set in one Object in list of filters.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7080) Creating ssl context with only required attribute cause NPE
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/WFLY-7080?page=com.atlassian.jira.plugin.... ]
Martin Choma updated WFLY-7080:
-------------------------------
Labels: user_experience (was: )
> Creating ssl context with only required attribute cause NPE
> -----------------------------------------------------------
>
> Key: WFLY-7080
> URL: https://issues.jboss.org/browse/WFLY-7080
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Martin Choma
> Assignee: Jan Kalina
> Priority: Critical
> Labels: user_experience
> Fix For: 11.0.0.Alpha1
>
>
> {noformat}
> [standalone@localhost:9990 /] /subsystem=elytron/server-ssl-context=server2:add(protocols=[TLSv1_2])
> {
> "outcome" => "failed",
> "failure-description" => {
> "WFLYCTL0080: Failed services" => {"org.wildfly.security.ssl-context.server2" => "org.jboss.msc.service.StartException in service org.wildfly.security.ssl-context.server2: Failed to start service
> Caused by: java.lang.NullPointerException"},
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.ssl-context.server2"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
> },
> "rolled-back" => true
> }
> {noformat}
> In log of server there is exception:
> {noformat}
> 07:12:21,014 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service org.wildfly.security.ssl-context.server2: org.jboss.msc.service.StartException in service org.wildfly.security.ssl-context.server2: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NullPointerException
> at org.wildfly.security.ssl.SSLContextBuilder.lambda$build$0(SSLContextBuilder.java:275)
> at org.wildfly.security.OneTimeSecurityFactory.create(OneTimeSecurityFactory.java:45)
> at org.wildfly.extension.elytron.SSLDefinitions$3.lambda$getValueSupplier$1(SSLDefinitions.java:411)
> at org.wildfly.extension.elytron.TrivialService.start(TrivialService.java:53)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> ... 3 more
> 07:12:21,016 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 6) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "elytron"),
> ("server-ssl-context" => "server2")
> ]) - failure description: {
> "WFLYCTL0080: Failed services" => {"org.wildfly.security.ssl-context.server2" => "org.jboss.msc.service.StartException in service org.wildfly.security.ssl-context.server2: Failed to start service
> Caused by: java.lang.NullPointerException"},
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.ssl-context.server2"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7451) Extra commas in descriptions of *-outbound-socket-binding CLI resources
by Ondrej Kotek (JIRA)
[ https://issues.jboss.org/browse/WFLY-7451?page=com.atlassian.jira.plugin.... ]
Ondrej Kotek reassigned WFLY-7451:
----------------------------------
Assignee: Jason Greene (was: Catherine Robson)
> Extra commas in descriptions of *-outbound-socket-binding CLI resources
> -----------------------------------------------------------------------
>
> Key: WFLY-7451
> URL: https://issues.jboss.org/browse/WFLY-7451
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Reporter: Ondrej Kotek
> Assignee: Jason Greene
> Priority: Trivial
> Labels: user_experience
>
> There are extra commas in descriptions of children resources of _socket-binding-group_ CLI resource (_local-destination-outbound-socket-binding_ and _remote-destination-outbound-socket-binding_).
> E.g., there is "Configuration information for a, local destination, outbound socket binding.", there should be "Configuration information for a local destination outbound socket binding."
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months