[JBoss JIRA] (WFLY-8416) Create BroadcastEndpoint implementation using WF clustering API
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-8416?page=com.atlassian.jira.plugin.... ]
Paul Ferraro updated WFLY-8416:
-------------------------------
Description: The upgrade to JGroups 4.0 will break the JGroups BroadcastEndpoint implementation in ActiveMQ Artemis (which uses JGroups 3.x). JGroups is only used to broadcast/receive a byte[] to the cluster. This can be easily implemented using the WildFly clustering API. Such an implementation will simplify the transition to JGroups 4.0 and future-proof WildFly from any new API breakage as well as abstract away concepts like fork channels, etc. (was: The upgrade to JGroups 4.0 will break the JGroups BroadcastEndpoint implementation in ActiveMQ Artemis (which uses JGroups 3.x). JGroups is only used to broadcast/receive a byte[] to the cluster. This can be easily implemented using the WildFly clustering API. Such an implementation will simplify the transition to JGroups 4.0 and future-proof WildFly from any new API breakage.)
> Create BroadcastEndpoint implementation using WF clustering API
> ---------------------------------------------------------------
>
> Key: WFLY-8416
> URL: https://issues.jboss.org/browse/WFLY-8416
> Project: WildFly
> Issue Type: Task
> Components: Clustering, JMS
> Affects Versions: 10.1.0.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Fix For: 12.0.0.Alpha1
>
>
> The upgrade to JGroups 4.0 will break the JGroups BroadcastEndpoint implementation in ActiveMQ Artemis (which uses JGroups 3.x). JGroups is only used to broadcast/receive a byte[] to the cluster. This can be easily implemented using the WildFly clustering API. Such an implementation will simplify the transition to JGroups 4.0 and future-proof WildFly from any new API breakage as well as abstract away concepts like fork channels, etc.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (DROOLS-1493) Improve temporal operators to support java.time classes
by Mario Fusco (JIRA)
Mario Fusco created DROOLS-1493:
-----------------------------------
Summary: Improve temporal operators to support java.time classes
Key: DROOLS-1493
URL: https://issues.jboss.org/browse/DROOLS-1493
Project: Drools
Issue Type: Enhancement
Components: core engine
Affects Versions: 7.0.0.Beta7
Reporter: chandra vudumula
Assignee: Mario Fusco
Attachments: image-2017-03-20-11-45-20-413.png
Hi,
I am trying to create a rule using UI,i have a filed LocalDateTime have to compare using after or before.
but in UI i am unable to see those options, its just showing default options like :equal to", "not equal to"...
Added dependencies in sourceObject and didnt helped
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2571) Support Bearer Token Credential type in CLI
by Pedro Igor (JIRA)
Pedro Igor created WFCORE-2571:
----------------------------------
Summary: Support Bearer Token Credential type in CLI
Key: WFCORE-2571
URL: https://issues.jboss.org/browse/WFCORE-2571
Project: WildFly Core
Issue Type: Enhancement
Components: CLI
Affects Versions: 3.0.0.Beta10
Reporter: Pedro Igor
Assignee: Pedro Igor
CLI should be able to support bearer token credentials in order to support integration with OAuth2 and OpenID Connect compliant authorization servers.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2409) Review elytron kerberos-security-factory resource
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2409?page=com.atlassian.jira.plugi... ]
Jan Kalina commented on WFCORE-2409:
------------------------------------
Resolved in PR92, except this point: *server*
> Review elytron kerberos-security-factory resource
> -------------------------------------------------
>
> Key: WFCORE-2409
> URL: https://issues.jboss.org/browse/WFCORE-2409
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 3.0.0.Beta7
> Reporter: Martin Choma
> Assignee: Darran Lofthouse
> Priority: Critical
> Labels: user_experience
> Fix For: 4.0.0.Alpha1
>
>
> * {{mechanism-oids}}
> ** Minimal command for kerberos security factory creation is {code}/subsystem=elytron/kerberos-security-factory=kerberos:add(principal=mchoma, path=/path/to/keytab, mechanism-oids=[1.2.840.113554.1.2.2]){code}
> ** I don't think it is user-friendly to require user to specify mechanism-oids. I think some reasonable default value should be used here.
> * {{minimum-remaining-lifetime}}
> ** please, specify units in documentation, e.g. seconds/minutes
> * {{relative-to}}
> ** as just path reference can be used here, probably should be just "expressions-allowed" => false
> ** In legacy settings it is documented better: "The name of another previously named path, or of one of the standard paths provided by the system. If 'relative-to' is provided, the value of the 'path' attribute is treated as relative to the path specified by this attribute."
> * {{server}}
> ** I assume based on {{server}} attribute INITIATE_ONLY or ACCEPT_ONLY is configured on GSSCredential [1]. Wouldn't it be useful to have also possibility to set INITIATE_AND_ACCEPT? Couldn't that be useful for example in case of identity propagation.
> * {{for-hosts}}
> ** comparing to legacy security {{kerberosIdentityType}} I am missing for-hosts. Elytron won't provide such feature?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (HAWKULARQE-76) Add Provider - Security Protocol
by Hayk Hovsepyan (JIRA)
Hayk Hovsepyan created HAWKULARQE-76:
----------------------------------------
Summary: Add Provider - Security Protocol
Key: HAWKULARQE-76
URL: https://issues.jboss.org/browse/HAWKULARQE-76
Project: Hawkular QE
Issue Type: Task
Reporter: Hayk Hovsepyan
Assignee: Michael Foley
Priority: Critical
In Add New Provider page there is a new field: "Security Protocol", for validating connection.
It needs to be tested and automated in Provider CRUD tests.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month