[JBoss JIRA] (WFCORE-4486) Support for multiple security realms - Failover
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFCORE-4486?page=com.atlassian.jira.plug... ]
Brian Stansberry updated WFCORE-4486:
-------------------------------------
[~mmazanek] [~fjuma] [~jmesnil] AIUI this is not expected for WildFly 19 so I'm going to remove the Fix Version that implies it is.
> Support for multiple security realms - Failover
> -----------------------------------------------
>
> Key: WFCORE-4486
> URL: https://issues.redhat.com/browse/WFCORE-4486
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Security
> Reporter: Farah Juma
> Assignee: Martin Mazanek
> Priority: Major
> Labels: CD17-Deferred, EAP-CD19
>
> Our security realms are able to indicate unavailability by throwing a RealmUnavailableException
> We should support fail over to an alternative realm.
> A common request is fail over to a local file based realm if an LDAP or database server has gone down allowing administrators to retain access to the server.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFCORE-4486) Support for multiple security realms - Failover
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFCORE-4486?page=com.atlassian.jira.plug... ]
Brian Stansberry updated WFCORE-4486:
-------------------------------------
Fix Version/s: (was: 11.0.0.Beta6)
> Support for multiple security realms - Failover
> -----------------------------------------------
>
> Key: WFCORE-4486
> URL: https://issues.redhat.com/browse/WFCORE-4486
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Security
> Reporter: Farah Juma
> Assignee: Martin Mazanek
> Priority: Major
> Labels: CD17-Deferred, EAP-CD19
>
> Our security realms are able to indicate unavailability by throwing a RealmUnavailableException
> We should support fail over to an alternative realm.
> A common request is fail over to a local file based realm if an LDAP or database server has gone down allowing administrators to retain access to the server.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFLY-12900) Clustering TS: Default to non-multicast discovery protocol
by Radoslav Husar (Jira)
[ https://issues.redhat.com/browse/WFLY-12900?page=com.atlassian.jira.plugi... ]
Radoslav Husar updated WFLY-12900:
----------------------------------
Description: We have been slowly making progress on reducing reliance on multicast to run the clustering test suite by default given the complexity of system configuration (e.g. multicast on {{::1}} workarounds). The goal is to use a default non-multicast-based protocol by defaut. (was: We have been slowly making progress on reducing reliance on multicast to run the clustering test suite by default given the complexity of system configuration (e.g. multicast on ::1 workarounds). The goal is to use a default non-multicast-based protocol by defaut.)
> Clustering TS: Default to non-multicast discovery protocol
> ----------------------------------------------------------
>
> Key: WFLY-12900
> URL: https://issues.redhat.com/browse/WFLY-12900
> Project: WildFly
> Issue Type: Task
> Components: Clustering, Test Suite
> Affects Versions: 18.0.1.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Critical
>
> We have been slowly making progress on reducing reliance on multicast to run the clustering test suite by default given the complexity of system configuration (e.g. multicast on {{::1}} workarounds). The goal is to use a default non-multicast-based protocol by defaut.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFCORE-4781) Ability to enable shutdown operation for EmbeddedServer
by Jean Francois Denise (Jira)
Jean Francois Denise created WFCORE-4781:
--------------------------------------------
Summary: Ability to enable shutdown operation for EmbeddedServer
Key: WFCORE-4781
URL: https://issues.redhat.com/browse/WFCORE-4781
Project: WildFly Core
Issue Type: Enhancement
Components: Embedded
Affects Versions: 11.0.0.Beta5
Reporter: Jean Francois Denise
Assignee: James Perkins
Having the shutdown operation available for embedded is needed when the embedder process and embedded server shutdown phase are bound.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFLY-12900) Clustering TS: Default to non-multicast discovery protocol
by Radoslav Husar (Jira)
Radoslav Husar created WFLY-12900:
-------------------------------------
Summary: Clustering TS: Default to non-multicast discovery protocol
Key: WFLY-12900
URL: https://issues.redhat.com/browse/WFLY-12900
Project: WildFly
Issue Type: Task
Components: Clustering, Test Suite
Reporter: Radoslav Husar
Assignee: Paul Ferraro
We have been slowly making progress on reducing reliance on multicast to run the clustering test suite by default given the complexity of system configuration (e.g. multicast on ::1 workarounds). The goal is to use a default non-multicast-based protocol by defaut.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFLY-12900) Clustering TS: Default to non-multicast discovery protocol
by Radoslav Husar (Jira)
[ https://issues.redhat.com/browse/WFLY-12900?page=com.atlassian.jira.plugi... ]
Radoslav Husar reassigned WFLY-12900:
-------------------------------------
Assignee: Radoslav Husar (was: Paul Ferraro)
> Clustering TS: Default to non-multicast discovery protocol
> ----------------------------------------------------------
>
> Key: WFLY-12900
> URL: https://issues.redhat.com/browse/WFLY-12900
> Project: WildFly
> Issue Type: Task
> Components: Clustering, Test Suite
> Affects Versions: 18.0.1.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Critical
>
> We have been slowly making progress on reducing reliance on multicast to run the clustering test suite by default given the complexity of system configuration (e.g. multicast on ::1 workarounds). The goal is to use a default non-multicast-based protocol by defaut.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (DROOLS-4564) Reconnecting the Kie-server to the controller while using the WebSocket connection problem
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-4564?page=com.atlassian.jira.plug... ]
Mario Fusco updated DROOLS-4564:
--------------------------------
Sprint: 2020 Week 01-03 (from Dec 30)
> Reconnecting the Kie-server to the controller while using the WebSocket connection problem
> ------------------------------------------------------------------------------------------
>
> Key: DROOLS-4564
> URL: https://issues.redhat.com/browse/DROOLS-4564
> Project: Drools
> Issue Type: Bug
> Components: integration, kie server
> Affects Versions: 7.24.0.Final
> Reporter: Marcin Kasza
> Assignee: Mario Fusco
> Priority: Major
>
> When the kie-server connects to the controller / workbench via web-sockets and this connection fails (e.g., due to network problems), the kie-server will try to reconnect.
> Reconnect thread started in WebSocketClientImpl (kie-server-controller-websocket-common), fails with NPE with log message: _WebSocketClientImpl: Unable to reconnect to the controller through the Null socket because of null_
> NPE is thrown because session.getRequestURI returns NULL value
> at this.session = container.connectToServer(this, this.config, session.getRequestURI());
> In my case kie-server (WebSocketContainer) running on tomcat 8.5
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months