April 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-1259) Tracer improvements

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-1259: -------------------------------------- Summary: Tracer improvements Key: JBJCA-1259 URL: https://issues.jboss.org/browse/JBJCA-1259 Project: IronJacamar Issue Type: Task Components: Core Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.2.4.Final Add the following events: * PUSH_CCM_CONTEXT * POP_CCM_CONTEXT * REGISTER_CCM_CONNECTION * UNREGISTER_CCM_CONNECTION * CCM_USER_TRANSACTION * UNKNOWN_CCM_CONNECTION * CLOSE_CCM_CONNECTION * VERSION Add 2nd payload field Create reports for CCM interaction Add -ignore-tracking command line option -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1605) API changes

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1605?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-1605: --------------------------- Description: API changes to be done in 4.0, which break code: * MessageDispatcher: remove MessageListener * Merge AsyncRequestHandler and RequestHandler, OR make them 2 separate interfaces, ie. AsyncRH doesn't extend RH * Remove @Deprecated methods, properties or classes * Remove direct access to Message in JChannel.send() methods (to prevent passing in the same message more than once) * Make {{RspFilter}} --> {{RspFilter<T>}} * {{ProtocolStack.findProtocol(Class<?> clazz)}} should return generic type {{<T extends Protocol>>}}, so no casting is needed. Requires changes to a number of methods in the same class. was: API changes to be done in 4.0, which break code: * MessageDispatcher: remove MessageListener * Merge AsyncRequestHandler and RequestHandler, OR make them 2 separate interfaces, ie. AsyncRH doesn't extend RH * Remove @Deprecated methods, properties or classes * Remove direct access to Message in JChannel.send() methods (to prevent passing in the same message more than once) * Make {{RspFilter}} --> {{RspFilter<T>}} > API changes > ----------- > > Key: JGRP-1605 > URL: https://issues.jboss.org/browse/JGRP-1605 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 4.0 > > > API changes to be done in 4.0, which break code: > * MessageDispatcher: remove MessageListener > * Merge AsyncRequestHandler and RequestHandler, OR make them 2 separate interfaces, ie. AsyncRH doesn't extend RH > * Remove @Deprecated methods, properties or classes > * Remove direct access to Message in JChannel.send() methods (to prevent passing in the same message more than once) > * Make {{RspFilter}} --> {{RspFilter<T>}} > * {{ProtocolStack.findProtocol(Class<?> clazz)}} should return generic type {{<T extends Protocol>>}}, so no casting is needed. Requires changes to a number of methods in the same class. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-92) The HTTPS protocol (https-remoting-jmx) is currently not working because of a broken protocol check.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-92?page=com.atlassian.jira.plugin.... ] Darran Lofthouse resolved REMJMX-92. ------------------------------------ Resolution: Done > The HTTPS protocol (https-remoting-jmx) is currently not working because of a broken protocol check. > ---------------------------------------------------------------------------------------------------- > > Key: REMJMX-92 > URL: https://issues.jboss.org/browse/REMJMX-92 > Project: Remoting JMX > Issue Type: Bug > Components: Connection > Affects Versions: 2.0.1.CR1 > Reporter: Philippe Marschall > Assignee: Darran Lofthouse > Fix For: 2.0.1.CR2 > > > The HTTPS protocol (https-remoting-jmx) is currently not working because of a broken protocol check. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-103) Add Full Kerberos Support

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-103?page=com.atlassian.jira.plugin... ] Darran Lofthouse updated WFCORE-103: ------------------------------------ Fix Version/s: 2.0.0.Alpha1 (was: 1.0.0.CR1) > Add Full Kerberos Support > ------------------------- > > Key: WFCORE-103 > URL: https://issues.jboss.org/browse/WFCORE-103 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: management_security, > Fix For: 2.0.0.Alpha1 > > > There are a number of steps required to full add Kerberos support - this is a top level tracking task to be resolved once all steps are complete. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-496) add-user.sh - if password contains § it is not possible to log into the webinterface

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-496?page=com.atlassian.jira.plugin... ] Darran Lofthouse updated WFCORE-496: ------------------------------------ Fix Version/s: 2.0.0.Alpha1 (was: 1.0.0.CR1) > add-user.sh - if password contains § it is not possible to log into the webinterface > ------------------------------------------------------------------------------------ > > Key: WFCORE-496 > URL: https://issues.jboss.org/browse/WFCORE-496 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Environment: wheezy, Firefox 34.0.5, Chrome 36.0.1985.125 > Reporter: do ev > Assignee: Darran Lofthouse > Fix For: 2.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-372) Cache role mapping results for the span of the overall operation

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-372?page=com.atlassian.jira.plugin... ] Darran Lofthouse updated WFCORE-372: ------------------------------------ Fix Version/s: 2.0.0.Alpha1 (was: 1.0.0.CR1) > Cache role mapping results for the span of the overall operation > ---------------------------------------------------------------- > > Key: WFCORE-372 > URL: https://issues.jboss.org/browse/WFCORE-372 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Darran Lofthouse > Labels: access_control, management_security, > Fix For: 2.0.0.Alpha1 > > > Look into caching role mapping results for the duration of an overall operation. This would be an impl detail of the RoleMapper. With our standard mappers, the mapping results should not be changing in the middle of an operation, so I believe they should be cacheable. > Likely place to cache them is as an attachment in a context object that will be passed in to the Authorizer. It would have to be passed in to the RoleMapper as well. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-299) HTTP Management Interface Configuration

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-299?page=com.atlassian.jira.plugin... ] Darran Lofthouse updated WFCORE-299: ------------------------------------ Fix Version/s: 2.0.0.Alpha1 (was: 1.0.0.CR1) > HTTP Management Interface Configuration > --------------------------------------- > > Key: WFCORE-299 > URL: https://issues.jboss.org/browse/WFCORE-299 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: management_security,, management_sso > Fix For: 2.0.0.Alpha1 > > > Various configuration items are required for the HTTP Management interface, this is a parent task to combine them. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-137) Add Kerberos tests to domain-management module

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-137?page=com.atlassian.jira.plugin... ] Darran Lofthouse updated WFCORE-137: ------------------------------------ Fix Version/s: 2.0.0.Alpha1 (was: 1.0.0.CR1) > Add Kerberos tests to domain-management module > ---------------------------------------------- > > Key: WFCORE-137 > URL: https://issues.jboss.org/browse/WFCORE-137 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 2.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-301) Configuration of individual contexts for http management interface.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-301?page=com.atlassian.jira.plugin... ] Darran Lofthouse updated WFCORE-301: ------------------------------------ Fix Version/s: 2.0.0.Alpha1 (was: 1.0.0.CR1) > Configuration of individual contexts for http management interface. > ------------------------------------------------------------------- > > Key: WFCORE-301 > URL: https://issues.jboss.org/browse/WFCORE-301 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 2.0.0.Alpha1 > > > At the moment all management requests are handled over the '/management' context, we also have a '/console' context to serve up the files for the admin console. > The '/management' context is secured using standard HTTP mechanisms, this decision was taken so that clients could be written in different languages and all they would need to know is how to use standard authentication mechanisms. Due to problems where web browsers could run malicious scripts cross origin resource sharing is completely disabled for this context. > We need to start to open up the handling of cross origin requests for a couple of reasons: - > - Enabling Keycloak SSO support. > - Alternative console distribution options > The '/management' context is going to be retained as-is for legacy clients, possibly even switched off by default. > A new context can then be added using non-browser based authentication, this could be SSO Keycloak or could be a form of Digest authentication where the response is handled by the console and not the web browser - either way as the browser is bypassed it is no longer at risk of sending malicious cross origin requests. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-304) Enable user agent and address filters.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-304?page=com.atlassian.jira.plugin... ] Darran Lofthouse updated WFCORE-304: ------------------------------------ Fix Version/s: 2.0.0.Alpha1 (was: 1.0.0.CR1) > Enable user agent and address filters. > -------------------------------------- > > Key: WFCORE-304 > URL: https://issues.jboss.org/browse/WFCORE-304 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 2.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2015