[JBoss JIRA] (ELY-776) Eliminate reference to "slot" from module configurations
by David Lloyd (JIRA)
David Lloyd created ELY-776:
-------------------------------
Summary: Eliminate reference to "slot" from module configurations
Key: ELY-776
URL: https://issues.jboss.org/browse/ELY-776
Project: WildFly Elytron
Issue Type: Enhancement
Components: Authentication Client
Reporter: David Lloyd
The final version of our client XSD should accept a name for modules but no slot. Instead, either the new name-only APIs should be used or a ModuleIdentifier created via that class's "fromString" method. Module slots are deprecated.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7639) Missing XSD for wildfly-config.xml
by Josef Cacek (JIRA)
Josef Cacek created WFLY-7639:
---------------------------------
Summary: Missing XSD for wildfly-config.xml
Key: WFLY-7639
URL: https://issues.jboss.org/browse/WFLY-7639
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Josef Cacek
Assignee: Darran Lofthouse
Priority: Critical
There is a new client configuration required in `wildfly-config.xml` (more in JBEAP-7104), but the `docs/schema` folder doesn't contain its XSD (schema definition).
We have to provide one with a sufficient description of the elements and attributes.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7638) It is not possible to set secure-socket-binding without security-realm in HTTP management interface
by Ondrej Lukas (JIRA)
Ondrej Lukas created WFLY-7638:
----------------------------------
Summary: It is not possible to set secure-socket-binding without security-realm in HTTP management interface
Key: WFLY-7638
URL: https://issues.jboss.org/browse/WFLY-7638
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Ondrej Lukas
Assignee: Darran Lofthouse
Priority: Critical
I am not able to add {{secure-socket-binding}} attribute for management-interface=http-interface resource which does not include {{security-realm}} attribute. This means that "Elytron-only" authentication and SSL configuration for HTTP interface is not possible.
Trying this issue for management-interface=native-interface is blocked by JBEAP-7424.
As workaround, if security-realm is also added then authentication with Elytron works correctly (added security-realm is not used because Elytron-related attributes in HTTP management interface have higher priority).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7638) It is not possible to set secure-socket-binding without security-realm in HTTP management interface
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/WFLY-7638?page=com.atlassian.jira.plugin.... ]
Ondrej Lukas updated WFLY-7638:
-------------------------------
Affects Version/s: 11.0.0.Alpha1
> It is not possible to set secure-socket-binding without security-realm in HTTP management interface
> ---------------------------------------------------------------------------------------------------
>
> Key: WFLY-7638
> URL: https://issues.jboss.org/browse/WFLY-7638
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Priority: Critical
>
> I am not able to add {{secure-socket-binding}} attribute for management-interface=http-interface resource which does not include {{security-realm}} attribute. This means that "Elytron-only" authentication and SSL configuration for HTTP interface is not possible.
> Trying this issue for management-interface=native-interface is blocked by JBEAP-7424.
> As workaround, if security-realm is also added then authentication with Elytron works correctly (added security-realm is not used because Elytron-related attributes in HTTP management interface have higher priority).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7637) It is not possible to set Elytron for native management interface
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/WFLY-7637?page=com.atlassian.jira.plugin.... ]
Ondrej Lukas updated WFLY-7637:
-------------------------------
Affects Version/s: 11.0.0.Alpha1
> It is not possible to set Elytron for native management interface
> -----------------------------------------------------------------
>
> Key: WFLY-7637
> URL: https://issues.jboss.org/browse/WFLY-7637
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Priority: Blocker
>
> I am not able to correctly configure native management interface to use Elytron.
> I am adding some binding for native interface:
> {code}
> /socket-binding-group=standard-sockets/socket-binding=native:add(port=9999)
> {code}
> And then adding native management interface which uses Elytron sasl-authentication-factory ({{application-sasl-authentication}} is predefined in standalone-elytron.xml):
> {code}
> /core-service=management/management-interface=native-interface:add(sasl-authentication-factory=application-sasl-authentication,socket-binding=native)
> {
> "outcome" => "failed",
> "failure-description" => {
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.sasl-authentication-factory"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.remoting.server.management is missing [org.wildfly.security.sasl-authentication-factory]"]
> },
> "rolled-back" => true
> }
> {code}
> Following exception occurs in server log:
> {code}
> ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) WFLYCTL0013: Operation ("add") failed - address: ([
> ("core-service" => "management"),
> ("management-interface" => "native-interface")
> ]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.sasl-authentication-factory"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.remoting.server.management is missing [org.wildfly.security.sasl-authentication-factory]"]
> }
> INFO [org.jboss.as.controller] (management-handler-thread - 2) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service org.wildfly.security.sasl-authentication-factory (missing) dependents: [service jboss.remoting.server.management]
> {code}
> The same exception is thrown when I am trying to set SSL through Elytron {{ssl-context}} attribute in management native-interface.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7637) It is not possible to set Elytron for native management interface
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/WFLY-7637?page=com.atlassian.jira.plugin.... ]
Ondrej Lukas updated WFLY-7637:
-------------------------------
Priority: Blocker (was: Critical)
> It is not possible to set Elytron for native management interface
> -----------------------------------------------------------------
>
> Key: WFLY-7637
> URL: https://issues.jboss.org/browse/WFLY-7637
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Priority: Blocker
>
> I am not able to correctly configure native management interface to use Elytron.
> I am adding some binding for native interface:
> {code}
> /socket-binding-group=standard-sockets/socket-binding=native:add(port=9999)
> {code}
> And then adding native management interface which uses Elytron sasl-authentication-factory ({{application-sasl-authentication}} is predefined in standalone-elytron.xml):
> {code}
> /core-service=management/management-interface=native-interface:add(sasl-authentication-factory=application-sasl-authentication,socket-binding=native)
> {
> "outcome" => "failed",
> "failure-description" => {
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.sasl-authentication-factory"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.remoting.server.management is missing [org.wildfly.security.sasl-authentication-factory]"]
> },
> "rolled-back" => true
> }
> {code}
> Following exception occurs in server log:
> {code}
> ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) WFLYCTL0013: Operation ("add") failed - address: ([
> ("core-service" => "management"),
> ("management-interface" => "native-interface")
> ]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.sasl-authentication-factory"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.remoting.server.management is missing [org.wildfly.security.sasl-authentication-factory]"]
> }
> INFO [org.jboss.as.controller] (management-handler-thread - 2) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service org.wildfly.security.sasl-authentication-factory (missing) dependents: [service jboss.remoting.server.management]
> {code}
> The same exception is thrown when I am trying to set SSL through Elytron {{ssl-context}} attribute in management native-interface.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7637) It is not possible to set Elytron for native management interface
by Ondrej Lukas (JIRA)
Ondrej Lukas created WFLY-7637:
----------------------------------
Summary: It is not possible to set Elytron for native management interface
Key: WFLY-7637
URL: https://issues.jboss.org/browse/WFLY-7637
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Ondrej Lukas
Assignee: Darran Lofthouse
Priority: Critical
I am not able to correctly configure native management interface to use Elytron.
I am adding some binding for native interface:
{code}
/socket-binding-group=standard-sockets/socket-binding=native:add(port=9999)
{code}
And then adding native management interface which uses Elytron sasl-authentication-factory ({{application-sasl-authentication}} is predefined in standalone-elytron.xml):
{code}
/core-service=management/management-interface=native-interface:add(sasl-authentication-factory=application-sasl-authentication,socket-binding=native)
{
"outcome" => "failed",
"failure-description" => {
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.sasl-authentication-factory"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.remoting.server.management is missing [org.wildfly.security.sasl-authentication-factory]"]
},
"rolled-back" => true
}
{code}
Following exception occurs in server log:
{code}
ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) WFLYCTL0013: Operation ("add") failed - address: ([
("core-service" => "management"),
("management-interface" => "native-interface")
]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.sasl-authentication-factory"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.remoting.server.management is missing [org.wildfly.security.sasl-authentication-factory]"]
}
INFO [org.jboss.as.controller] (management-handler-thread - 2) WFLYCTL0183: Service status report
WFLYCTL0184: New missing/unsatisfied dependencies:
service org.wildfly.security.sasl-authentication-factory (missing) dependents: [service jboss.remoting.server.management]
{code}
The same exception is thrown when I am trying to set SSL through Elytron {{ssl-context}} attribute in management native-interface.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFCORE-2011) Inconsistency of formatter and named-formatter in console logging handler
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2011?page=com.atlassian.jira.plugi... ]
Brian Stansberry reassigned WFCORE-2011:
----------------------------------------
Assignee: ted won (was: Brian Stansberry)
> Inconsistency of formatter and named-formatter in console logging handler
> -------------------------------------------------------------------------
>
> Key: WFCORE-2011
> URL: https://issues.jboss.org/browse/WFCORE-2011
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 3.0.0.Alpha13
> Environment: It is possible to reproduce with all profiles and all modes.
> All WildFly profiles
> All WildFly clustering mode
> * standalone mode
> * domain mode
> Reporter: ted won
> Assignee: ted won
> Priority: Minor
> Labels: logging
> Attachments: COLOR-PATTERN.png, CONSOLE-console-handler.png
>
>
> In logging subsystem the default CONSOLE console-handler is defined with COLOR-PATTERN named-formatter.
> And the COLOR-PATTERN named-formatter is defined with: {noformat}"%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n"{noformat}
> It is working as it is defined with colors in a console.
> {code:title=standalone.xml}
> ...
> <subsystem xmlns="urn:jboss:domain:logging:3.0">
> <console-handler name="CONSOLE">
> <level name="INFO"/>
> <formatter>
> <named-formatter name="COLOR-PATTERN"/>
> </formatter>
> </console-handler>
> ...
> <formatter name="COLOR-PATTERN">
> <pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n"/>
> </formatter>
> </subsystem>
> ...
> {code}
> However there is a inconsistency in the CLI and WildFly admin console views.
> In the CLI, CONSOLE formatter is: {noformat}"%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n"{noformat} It is wrong and different with the working logging format in a console.
> {code:title=JBoss CLI}
> [standalone@localhost:9990 /] /subsystem=logging/console-handler=CONSOLE:read-resource
> {
> "outcome" => "success",
> "result" => {
> "autoflush" => true,
> "enabled" => true,
> "encoding" => undefined,
> "filter" => undefined,
> "filter-spec" => undefined,
> "formatter" => "%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n",
> "level" => "INFO",
> "name" => "CONSOLE",
> "named-formatter" => "COLOR-PATTERN",
> "target" => "System.out"
> }
> }
> {code}
> It should be fixed like below:
> {code:title=Expected result}
> [standalone@localhost:9990 /] /subsystem=logging/console-handler=CONSOLE:read-resource
> {
> "outcome" => "success",
> "result" => {
> "autoflush" => true,
> "enabled" => true,
> "encoding" => undefined,
> "filter" => undefined,
> "filter-spec" => undefined,
> "formatter" => undefined,
> "level" => "INFO",
> "name" => "CONSOLE",
> "named-formatter" => "COLOR-PATTERN",
> "target" => "System.out"
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (ELY-368) Add optional Supplier<Provider[]> to realm implementations.
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-368?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-368:
---------------------------------
Component/s: Realms
> Add optional Supplier<Provider[]> to realm implementations.
> -----------------------------------------------------------
>
> Key: ELY-368
> URL: https://issues.jboss.org/browse/ELY-368
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: Realms
> Reporter: David Lloyd
> Assignee: Darran Lofthouse
> Priority: Critical
> Fix For: 1.1.0.Beta15
>
>
> Realms use key factories, certificate factories, password factories, etc. Most of the time they just use the default installed providers. Enhance the realms to accept an optional {{Supplier<Provider[]>}} which will be used to load these kinds of things. The default supplier should be {{Security::getProviders()}}.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFCORE-2011) Inconsistency of formatter and named-formatter in console logging handler
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2011?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-2011:
------------------------------------------
Great; I'll assign this back to you then. Thanks for your help. :)
> Inconsistency of formatter and named-formatter in console logging handler
> -------------------------------------------------------------------------
>
> Key: WFCORE-2011
> URL: https://issues.jboss.org/browse/WFCORE-2011
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 3.0.0.Alpha13
> Environment: It is possible to reproduce with all profiles and all modes.
> All WildFly profiles
> All WildFly clustering mode
> * standalone mode
> * domain mode
> Reporter: ted won
> Assignee: Brian Stansberry
> Priority: Minor
> Labels: logging
> Attachments: COLOR-PATTERN.png, CONSOLE-console-handler.png
>
>
> In logging subsystem the default CONSOLE console-handler is defined with COLOR-PATTERN named-formatter.
> And the COLOR-PATTERN named-formatter is defined with: {noformat}"%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n"{noformat}
> It is working as it is defined with colors in a console.
> {code:title=standalone.xml}
> ...
> <subsystem xmlns="urn:jboss:domain:logging:3.0">
> <console-handler name="CONSOLE">
> <level name="INFO"/>
> <formatter>
> <named-formatter name="COLOR-PATTERN"/>
> </formatter>
> </console-handler>
> ...
> <formatter name="COLOR-PATTERN">
> <pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n"/>
> </formatter>
> </subsystem>
> ...
> {code}
> However there is a inconsistency in the CLI and WildFly admin console views.
> In the CLI, CONSOLE formatter is: {noformat}"%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n"{noformat} It is wrong and different with the working logging format in a console.
> {code:title=JBoss CLI}
> [standalone@localhost:9990 /] /subsystem=logging/console-handler=CONSOLE:read-resource
> {
> "outcome" => "success",
> "result" => {
> "autoflush" => true,
> "enabled" => true,
> "encoding" => undefined,
> "filter" => undefined,
> "filter-spec" => undefined,
> "formatter" => "%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n",
> "level" => "INFO",
> "name" => "CONSOLE",
> "named-formatter" => "COLOR-PATTERN",
> "target" => "System.out"
> }
> }
> {code}
> It should be fixed like below:
> {code:title=Expected result}
> [standalone@localhost:9990 /] /subsystem=logging/console-handler=CONSOLE:read-resource
> {
> "outcome" => "success",
> "result" => {
> "autoflush" => true,
> "enabled" => true,
> "encoding" => undefined,
> "filter" => undefined,
> "filter-spec" => undefined,
> "formatter" => undefined,
> "level" => "INFO",
> "name" => "CONSOLE",
> "named-formatter" => "COLOR-PATTERN",
> "target" => "System.out"
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months