[JBoss JIRA] (WFLY-10611) [GSS](7.1.z) Missing subsystem component to use a custom audit endpoint
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-10611?page=com.atlassian.jira.plugin... ]
Jan Kalina updated WFLY-10611:
------------------------------
Description:
Elytron has the ability to create custom audit endpoints to develop your own audit logs. Nevertheless there is no configuration under the {{subsystem=elytron}} to configure a custom audit class (something like {{subsystem=elytron/custom-audit-log=example:add(...}} is needed).
Feature implementation is in WFCORE-3819, this issue is for tests and docs into wildfly.
was:Elytron has the ability to create custom audit endpoints to develop your own audit logs. Nevertheless there is no configuration under the {{subsystem=elytron}} to configure a custom audit class (something like {{subsystem=elytron/custom-audit-log=example:add(...}} is needed).
> [GSS](7.1.z) Missing subsystem component to use a custom audit endpoint
> -----------------------------------------------------------------------
>
> Key: WFLY-10611
> URL: https://issues.jboss.org/browse/WFLY-10611
> Project: WildFly
> Issue Type: Feature Request
> Components: Security
> Affects Versions: 13.0.0.Final
> Reporter: Jan Kalina
> Assignee: Jan Kalina
>
> Elytron has the ability to create custom audit endpoints to develop your own audit logs. Nevertheless there is no configuration under the {{subsystem=elytron}} to configure a custom audit class (something like {{subsystem=elytron/custom-audit-log=example:add(...}} is needed).
> Feature implementation is in WFCORE-3819, this issue is for tests and docs into wildfly.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFCORE-3940) [GSS](7.1.z) Missing subsystem component to use a custom audit endpoint
by Jan Kalina (JIRA)
Jan Kalina created WFCORE-3940:
----------------------------------
Summary: [GSS](7.1.z) Missing subsystem component to use a custom audit endpoint
Key: WFCORE-3940
URL: https://issues.jboss.org/browse/WFCORE-3940
Project: WildFly Core
Issue Type: Feature Request
Components: Security
Affects Versions: 5.0.0.Alpha7
Reporter: Jan Kalina
Assignee: Jan Kalina
Elytron has the ability to create custom audit endpoints to develop your own audit logs. Nevertheless there is no configuration under the {{subsystem=elytron}} to configure a custom audit class (something like {{subsystem=elytron/custom-audit-log=example:add(...}} is needed).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10611) [GSS](7.1.z) Missing subsystem component to use a custom audit endpoint
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-10611?page=com.atlassian.jira.plugin... ]
Jan Kalina moved WFCORE-3940 to WFLY-10611:
-------------------------------------------
Project: WildFly (was: WildFly Core)
Key: WFLY-10611 (was: WFCORE-3940)
Component/s: Security
(was: Security)
Affects Version/s: 13.0.0.Final
(was: 5.0.0.Alpha7)
> [GSS](7.1.z) Missing subsystem component to use a custom audit endpoint
> -----------------------------------------------------------------------
>
> Key: WFLY-10611
> URL: https://issues.jboss.org/browse/WFLY-10611
> Project: WildFly
> Issue Type: Feature Request
> Components: Security
> Affects Versions: 13.0.0.Final
> Reporter: Jan Kalina
> Assignee: Jan Kalina
>
> Elytron has the ability to create custom audit endpoints to develop your own audit logs. Nevertheless there is no configuration under the {{subsystem=elytron}} to configure a custom audit class (something like {{subsystem=elytron/custom-audit-log=example:add(...}} is needed).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFCORE-3939) Add PersistentResourceXMLParser support for logical grouping of child resources
by Paul Ferraro (JIRA)
Paul Ferraro created WFCORE-3939:
------------------------------------
Summary: Add PersistentResourceXMLParser support for logical grouping of child resources
Key: WFCORE-3939
URL: https://issues.jboss.org/browse/WFCORE-3939
Project: WildFly Core
Issue Type: Enhancement
Components: Management
Affects Versions: 6.0.0.Alpha1
Reporter: Paul Ferraro
Assignee: Paul Ferraro
One of the limitations of PersistentResourceXMLParser preventing its use within the clustering subsystems is the lack of the ability to group child resources. For example, the JGroups subsystem's root resource contains 2 attributes and 2 child resources, where child resources are logically grouped within an attribute groups. The JGroups subsystem in one such example:
{code:xml}
<channels default="...">
<channel name="..." stack="..."/>
<channel name="..."/>
</channels>
<stacks default="...">
<stack name="..."/>
<stack name="..."/>
</stacks>
{code}
Here, we need the ability to group specific children within the element of an attribute group.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10469) Dropped message did not match the computed checksum
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-10469?page=com.atlassian.jira.plugin... ]
Radoslav Husar commented on WFLY-10469:
---------------------------------------
JGroups upgrade in WFLY-10610 brings in fixes for ASYM_ENCRYPT so this scenario should be revalidated after resolution.
> Dropped message did not match the computed checksum
> ---------------------------------------------------
>
> Key: WFLY-10469
> URL: https://issues.jboss.org/browse/WFLY-10469
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Reporter: Romain Pelisse
> Assignee: Paul Ferraro
>
> We saw this error during failover scenario *eap-7x-failover-http-session-shutdown-dist-async-auth-asymEncrypt* (scenario with "AUTH" and "ASYM_ENCRYPT" protocols enabled) (21 occurences).
> The error started to occur on *server*
> {code}
> 04:42:59,767 WARN [org.jgroups.protocols.ASYM_ENCRYPT] (thread-20,ee,perf21) perf21: exception occurred decrypting message
> [JBossINF] 04:42:59,768 ERROR [org.jgroups.protocols.ASYM_ENCRYPT] (thread-10,ee,perf21) perf21: dropped message from perf20 as the message's checksum (3775292975120264796) did not match the computed checksum (2347657351)
> [JBossINF] 04:42:59,768 WARN [org.jgroups.protocols.ASYM_ENCRYPT] (thread-10,ee,perf21) perf21: unrecognized cipher; discarding message from perf20
> {code}
> together with decrypting WARN messages 2 seconds after new cluster view was received:
> {code}
> 04:42:57,878 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (thread-6,ee,perf21) ISPN000094: Received new cluster view for channel ejb: [perf19|4] (3) [perf19, perf21, perf20]
> {code}
> Link to server log:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/perflab_eap-7x-failov...
> Client did not log any error at that time.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10073) Key requester node_X is not in current view Y; ignoring key request
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-10073?page=com.atlassian.jira.plugin... ]
Radoslav Husar commented on WFLY-10073:
---------------------------------------
JGroups upgrade in WFLY-10610 brings in fixes for ASYM_ENCRYPT so this scenario should be revalidated after resolution.
> Key requester node_X is not in current view Y; ignoring key request
> -------------------------------------------------------------------
>
> Key: WFLY-10073
> URL: https://issues.jboss.org/browse/WFLY-10073
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Reporter: Daniel Čihák
> Assignee: Paul Ferraro
>
> Four errors were logged on *server* during failover scenario *eap-7x-failover-http-session-shutdown-dist-async-auth-asymEncrypt* (scenario with "AUTH" and "ASYM_ENCRYPT" protocols enabled) during new cluster view receiving:
> {code}
> 04:47:29,691 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (thread-7,ee,perf21) ISPN000094: Received new cluster view for channel ejb: [perf21|8] (3) [perf21, perf18, perf19]
> [JBossINF] 04:47:29,692 WARN [org.jgroups.protocols.ASYM_ENCRYPT] (thread-1,ee,perf21) perf21: unrecognized cipher; discarding message from perf20
> [JBossINF] 04:47:29,692 ERROR [org.jgroups.protocols.ASYM_ENCRYPT] (thread-9,ee,perf21) key requester perf20 is not in current view [perf21|8] (3) [perf21, perf18, perf19]; ignoring key request
> [JBossINF] 04:47:29,692 ERROR [org.jgroups.protocols.ASYM_ENCRYPT] (thread-1,ee,perf21) key requester perf20 is not in current view [perf21|8] (3) [perf21, perf18, perf19]; ignoring key request
> [JBossINF] 04:47:29,694 ERROR [org.jgroups.protocols.ASYM_ENCRYPT] (thread-13,ee,perf21) key requester perf20 is not in current view [perf21|8] (3) [perf21, perf18, perf19]; ignoring key request
> [JBossINF] 04:47:29,694 ERROR [org.jgroups.protocols.ASYM_ENCRYPT] (thread-13,ee,perf21) key requester perf20 is not in current view [perf21|8] (3) [perf21, perf18, perf19]; ignoring key request
> [JBossINF] 04:48:37,553 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (thread-2,ee,perf21) ISPN000094: Received new cluster view for channel server: [perf21|9] (4) [perf21, perf18, perf19, perf20]
> {code}
> WARN message was logged just before:
> {code}
> 04:47:29,692 WARN [org.jgroups.protocols.ASYM_ENCRYPT] (thread-1,ee,perf21) perf21: unrecognized cipher; discarding message from perf20
> {code}
> Link to server log:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/perflab_eap-7x-failov...
> There are two WARN exceptions logged on client at the same time:
> {code}
> 04:47:28:988 EST [WARN ][Runner - 1066] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Invalid response code: 500 Content: <html><head><title>Error</title></head><body>Internal Server Error</body></html>>
> org.jboss.smartfrog.loaddriver.RequestProcessingException: Invalid response code: 500 Content: <html><head><title>Error</title></head><body>Internal Server Error</body></html>
> at org.jboss.smartfrog.loaddriver.http.HttpRequestProcessorFactoryImpl$HttpRequestProcessor.processRequest(HttpRequestProcessorFactoryImpl.java:163)
> at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
> at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:103)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> Link to client log:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/perflab_eap-7x-failov...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month