[JBoss JIRA] (ELY-1712) Enhanced Audit Logging - RFC support and Configuring Reconnects
by Justin Cook (Jira)
[ https://issues.jboss.org/browse/ELY-1712?page=com.atlassian.jira.plugin.s... ]
Justin Cook updated ELY-1712:
-----------------------------
Description:
Currently, Audit Logging in Elytron does not have the same capabilities as Legacy Security. This task is to enhance Elytron Audit Logging to have support for RFC5424/RFC3164 and add the additional ability to configure reconnect attempts.
was:
This RFE for Enhanced Audit Logging in WildFly Elytron is for:
* RFC5424 Support
* RFC3164 Support
* Reliability vs Speed Customization
> Enhanced Audit Logging - RFC support and Configuring Reconnects
> ---------------------------------------------------------------
>
> Key: ELY-1712
> URL: https://issues.jboss.org/browse/ELY-1712
> Project: WildFly Elytron
> Issue Type: Feature Request
> Components: Audit
> Reporter: Justin Cook
> Assignee: Justin Cook
> Priority: Major
> Fix For: 1.10.0.CR5
>
>
> Currently, Audit Logging in Elytron does not have the same capabilities as Legacy Security. This task is to enhance Elytron Audit Logging to have support for RFC5424/RFC3164 and add the additional ability to configure reconnect attempts.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (WFCORE-4551) Cannot add Elytron jdbc-realm using embedded server in admin mode
by Ashley Abdel-Sayed (Jira)
[ https://issues.jboss.org/browse/WFCORE-4551?page=com.atlassian.jira.plugi... ]
Ashley Abdel-Sayed reassigned WFCORE-4551:
------------------------------------------
Assignee: Ashley Abdel-Sayed
> Cannot add Elytron jdbc-realm using embedded server in admin mode
> -----------------------------------------------------------------
>
> Key: WFCORE-4551
> URL: https://issues.jboss.org/browse/WFCORE-4551
> Project: WildFly Core
> Issue Type: Bug
> Components: Embedded, Security
> Affects Versions: 8.0.0.Final, 9.0.1.Final
> Reporter: David Gill
> Assignee: Ashley Abdel-Sayed
> Priority: Critical
>
> On a fresh a Wildfly install (tested on 16.final and 17.final) the following jboss-cli commands will fail to add an Elytron jdbc-realm to an embedded server using the ExampleDS data source that is predefined out-of-the-box:
> {noformat}
> embed-server --server-config=standalone.xml
> /subsystem=elytron/jdbc-realm=MyRealm:add(principal-query=[{sql="SELECT * FROM Users WHERE username = ?", data-source=ExampleDS}])
> {noformat}
> Resulting in this error:
> {noformat}
> ERROR [org.jboss.as.controller.management-operation] (pool-3-thread-1) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "elytron"),
> ("jdbc-realm" => "MyRealm")
> ]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.data-source.ExampleDS"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.security.security-realm.MyRealm is missing [org.wildfly.data-source.ExampleDS]"]
> }
> {
> "outcome" => "failed",
> "failure-description" => {
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.data-source.ExampleDS"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.security.security-realm.MyRealm is missing [org.wildfly.data-source.ExampleDS]"]
> },
> "rolled-back" => true
> }
> {noformat}
> If you instead embed the server using {{--admin-only=false}} then the jdbc-realm will be added successfully.
> A workaround seems to be to first add and remove some other type of realm with the same name as the jdbc-realm you want to add, here for example using an identity-realm:
> {noformat}
> embed-server --server-config=standalone.xml
> # First add & remove a dummy realm with the same name as the jdbc-realm you want to add
> /subsystem=elytron/identity-realm=MyRealm:add(identity='dummy identity realm')
> /subsystem=elytron/identity-realm=MyRealm:remove
> # Now the jdbc-realm will add successfully
> /subsystem=elytron/jdbc-realm=MyRealm:add(principal-query=[{sql="SELECT * FROM Users WHERE username = ?", data-source=ExampleDS}])
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (WFCORE-4581) Defining management-interface with https-only socket-bindings causes server to shut down instantly
by Jeff Mesnil (Jira)
[ https://issues.jboss.org/browse/WFCORE-4581?page=com.atlassian.jira.plugi... ]
Jeff Mesnil reassigned WFCORE-4581:
-----------------------------------
Assignee: Richard Opalka (was: Jeff Mesnil)
> Defining management-interface with https-only socket-bindings causes server to shut down instantly
> --------------------------------------------------------------------------------------------------
>
> Key: WFCORE-4581
> URL: https://issues.jboss.org/browse/WFCORE-4581
> Project: WildFly Core
> Issue Type: Bug
> Reporter: Bartosz Spyrko
> Assignee: Richard Opalka
> Priority: Major
>
> management interface is configured to support only https connections:
> {noformat}
> <management-interfaces>
> <http-interface security-realm="ManagementRealm">
> <http-upgrade enabled="true"/>
> <socket-binding https="management-https"/>
> </http-interface>
> </management-interfaces>
> {noformat}
> On startup the server will not report any errors, but will immediately shutdown:
> {noformat}
> $ ./bin/standalone.sh
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /Users/spyrkob/workspaces/set/tools/installer/wildfly-core/build/target/wildfly-core-9.0.0.Beta4-SNAPSHOT
> JAVA: /Library/Java/JavaVirtualMachines/jdk1.8.0_152.jdk/Contents/Home/bin/java
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> 16:45:34,016 INFO [org.jboss.modules] (main) JBoss Modules version 1.9.1.Final
> 16:45:34,483 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.5.Final
> 16:45:34,496 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
> 16:45:34,660 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Core 9.0.0.Beta4-SNAPSHOT starting
> 16:45:35,383 INFO [org.wildfly.security] (ServerService Thread Pool -- 6) ELY00001: WildFly Elytron version 1.9.0.CR4
> 16:45:35,536 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 16:45:35,569 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0040: Creating http management service using secure-socket-binding (management-https)
> 16:45:35,592 INFO [org.xnio] (MSC service thread 1-6) XNIO version 3.7.1.Final
> 16:45:35,600 INFO [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.7.1.Final
> 16:45:35,672 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 5.0.9.Final
> 16:45:35,694 INFO [org.jboss.as.patching] (MSC service thread 1-7) WFLYPAT0050: WildFly cumulative patch ID is: base, one-off patches include: none
> 16:45:35,715 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-7) WFLYDM0111: Keystore /Users/spyrkob/workspaces/set/tools/installer/wildfly-core/build/target/wildfly-core-9.0.0.Beta4-SNAPSHOT/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
> 16:45:35,896 WARN [org.jboss.as.domain.http.api.undertow] (MSC service thread 1-7) WFLYDMHTTP0003: Unable to load console module for slot main, disabling console
> 16:45:35,982 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> 16:45:35,988 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0050: WildFly Core 9.0.0.Beta4-SNAPSHOT stopped in 2ms
> {noformat}
> In previous release this was a valid settings, the problem seems to have been introduced by WFCORE-4442
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (WFCORE-4581) Defining management-interface with https-only socket-bindings causes server to shut down instantly
by Jeff Mesnil (Jira)
[ https://issues.jboss.org/browse/WFCORE-4581?page=com.atlassian.jira.plugi... ]
Jeff Mesnil commented on WFCORE-4581:
-------------------------------------
[~ropalka] could you look at this regression please?
> Defining management-interface with https-only socket-bindings causes server to shut down instantly
> --------------------------------------------------------------------------------------------------
>
> Key: WFCORE-4581
> URL: https://issues.jboss.org/browse/WFCORE-4581
> Project: WildFly Core
> Issue Type: Bug
> Reporter: Bartosz Spyrko
> Assignee: Richard Opalka
> Priority: Major
>
> management interface is configured to support only https connections:
> {noformat}
> <management-interfaces>
> <http-interface security-realm="ManagementRealm">
> <http-upgrade enabled="true"/>
> <socket-binding https="management-https"/>
> </http-interface>
> </management-interfaces>
> {noformat}
> On startup the server will not report any errors, but will immediately shutdown:
> {noformat}
> $ ./bin/standalone.sh
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /Users/spyrkob/workspaces/set/tools/installer/wildfly-core/build/target/wildfly-core-9.0.0.Beta4-SNAPSHOT
> JAVA: /Library/Java/JavaVirtualMachines/jdk1.8.0_152.jdk/Contents/Home/bin/java
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> 16:45:34,016 INFO [org.jboss.modules] (main) JBoss Modules version 1.9.1.Final
> 16:45:34,483 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.5.Final
> 16:45:34,496 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
> 16:45:34,660 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Core 9.0.0.Beta4-SNAPSHOT starting
> 16:45:35,383 INFO [org.wildfly.security] (ServerService Thread Pool -- 6) ELY00001: WildFly Elytron version 1.9.0.CR4
> 16:45:35,536 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 16:45:35,569 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0040: Creating http management service using secure-socket-binding (management-https)
> 16:45:35,592 INFO [org.xnio] (MSC service thread 1-6) XNIO version 3.7.1.Final
> 16:45:35,600 INFO [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.7.1.Final
> 16:45:35,672 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 5.0.9.Final
> 16:45:35,694 INFO [org.jboss.as.patching] (MSC service thread 1-7) WFLYPAT0050: WildFly cumulative patch ID is: base, one-off patches include: none
> 16:45:35,715 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-7) WFLYDM0111: Keystore /Users/spyrkob/workspaces/set/tools/installer/wildfly-core/build/target/wildfly-core-9.0.0.Beta4-SNAPSHOT/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
> 16:45:35,896 WARN [org.jboss.as.domain.http.api.undertow] (MSC service thread 1-7) WFLYDMHTTP0003: Unable to load console module for slot main, disabling console
> 16:45:35,982 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> 16:45:35,988 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0050: WildFly Core 9.0.0.Beta4-SNAPSHOT stopped in 2ms
> {noformat}
> In previous release this was a valid settings, the problem seems to have been introduced by WFCORE-4442
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months