December 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4665) Re visit authentication tokens

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/AS7-4665?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated AS7-4665: ---------------------------------- Fix Version/s: 7.3.0.Alpha1 (was: 7.2.0.Alpha1) > Re visit authentication tokens > ------------------------------ > > Key: AS7-4665 > URL: https://issues.jboss.org/browse/AS7-4665 > Project: Application Server 7 > Issue Type: Sub-task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: Common_Authentication > Fix For: 7.3.0.Alpha1 > > > We had previously considered authentication tokens for the realm secured interfaces, this issue is just to track re-considering them again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-4693) Implement Trust for users requesting to run as a different user.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/AS7-4693?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated AS7-4693: ---------------------------------- Fix Version/s: 7.3.0.Alpha1 (was: 7.2.0.Alpha1) > Implement Trust for users requesting to run as a different user. > ---------------------------------------------------------------- > > Key: AS7-4693 > URL: https://issues.jboss.org/browse/AS7-4693 > Project: Application Server 7 > Issue Type: Sub-task > Components: Remoting, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 7.3.0.Alpha1 > > > Where SASL is used for authentication users can request to authenticate as themselves but to be authorized to connect to the server as a different user. > A couple of examples where this could be used: - > - A user granting access to another user to log into their account. > - A user with two levels of access e.g. normal and admin and requesting they have admin level access. > Another area we are looking to use this feature is where one server connects to another server but want to be able to run requests on the remote server using the identity of a specified user. > This Jira issue is to enhance the security realms to allow for trust permissions to be defined - initially this will be local to a single realm but will subsequently be opened up to work across different realms. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-5047) Allow more control over authentication for server to server communication through remote-outbound-connection

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/AS7-5047?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated AS7-5047: ---------------------------------- Fix Version/s: 7.3.0.Alpha1 (was: 7.2.0.Alpha1) > Allow more control over authentication for server to server communication through remote-outbound-connection > ------------------------------------------------------------------------------------------------------------ > > Key: AS7-5047 > URL: https://issues.jboss.org/browse/AS7-5047 > Project: Application Server 7 > Issue Type: Sub-task > Components: Remoting, Security > Affects Versions: 7.1.1.Final, 7.1.2.Final (EAP) > Reporter: jaikiran pai > Assignee: Darran Lofthouse > Fix For: 7.3.0.Alpha1 > > > Right now for server to server communication via a remote-outbound-connection, we expect a static username to be specified (along with the security realm). User applications which use this remote-outbound-connection, for example an EJB application, do not have much control over the user/pass information, since the username is static. This further acts a drawback since the username that's used to connect to the remote server will be used as the (application) user who invoked the EJB. > It would be good to allow more control over the authentication for the remote-outbound-connection. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-5901) Connection Reauthentication and Security Propagation

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/AS7-5901?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated AS7-5901: ---------------------------------- Fix Version/s: 7.3.0.Alpha1 (was: 7.2.0.Alpha1) > Connection Reauthentication and Security Propagation > ---------------------------------------------------- > > Key: AS7-5901 > URL: https://issues.jboss.org/browse/AS7-5901 > Project: Application Server 7 > Issue Type: Task > Components: EJB, Remoting, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 7.3.0.Alpha1 > > > This task is a top level task to coordinate the addition of support for switching to different security identities on an existing connection over Remoting. > This is to predominantly cover two major scenarios: - > - Clients using a single connection but require different calls to be executed as different users, in this case the client has the information required to start a new authentication as a different user. > - Server to server communication where the first server has already authenticated a remote user - for this scenario the first server needs a way to tell the second server what identity to run the call as. > The following document is building up the requirements and design considerations and decisions: - > https://community.jboss.org/wiki/ConnectionRe-AuthenticationAndSecurityPr... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1547) RELAY2: provide timing stats

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1547?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1547: -------------------------------- The stats are visible through JMX or probe, e.g. probe.sh jmx=RELAY2.num,avg,time > RELAY2: provide timing stats > ---------------------------- > > Key: JGRP-1547 > URL: https://issues.jboss.org/browse/JGRP-1547 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 3.3 > > > Provide the following stats: > - Number of forwarded messages / total time / avg (min,max,median,99th percentile ?) > - Number of forwarded msgs received > - xsite forwards / avg etc > - xsite forwards received > - local forwards > - local forwards received > - local deliveries > Ability to reset all stats, plus avg/median time for all sends -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1547) RELAY2: provide timing stats

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1547?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-1547. ---------------------------- Resolution: Done > RELAY2: provide timing stats > ---------------------------- > > Key: JGRP-1547 > URL: https://issues.jboss.org/browse/JGRP-1547 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 3.3 > > > Provide the following stats: > - Number of forwarded messages / total time / avg (min,max,median,99th percentile ?) > - Number of forwarded msgs received > - xsite forwards / avg etc > - xsite forwards received > - local forwards > - local forwards received > - local deliveries > Ability to reset all stats, plus avg/median time for all sends -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6110) Update to console 1.5.0

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-6110?page=com.atlassian.jira.plugin.s... ] Heiko Braun updated AS7-6110: ----------------------------- Description: Merry Christmas: http://hbraun.info/2012/12/jboss-as7-console-1-5-0-released/ > Update to console 1.5.0 > ----------------------- > > Key: AS7-6110 > URL: https://issues.jboss.org/browse/AS7-6110 > Project: Application Server 7 > Issue Type: Feature Request > Components: Build System, Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Priority: Blocker > Fix For: 7.2.0.CR1 > > > Merry Christmas: http://hbraun.info/2012/12/jboss-as7-console-1-5-0-released/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6241) Upgrade to JBossWS 4.1.1.Final

by Richard Opalka (JIRA)

Richard Opalka created AS7-6241: ----------------------------------- Summary: Upgrade to JBossWS 4.1.1.Final Key: AS7-6241 URL: https://issues.jboss.org/browse/AS7-6241 Project: Application Server 7 Issue Type: Task Components: Web Services Reporter: Richard Opalka Assignee: Richard Opalka Fix For: 7.2.0.Alpha1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6240) Only remove XA recovery module if it is defined

by Jesper Pedersen (JIRA)

Jesper Pedersen created AS7-6240: ------------------------------------ Summary: Only remove XA recovery module if it is defined Key: AS7-6240 URL: https://issues.jboss.org/browse/AS7-6240 Project: Application Server 7 Issue Type: Task Components: JCA Affects Versions: 7.1.3.Final (EAP) Reporter: Jesper Pedersen Assignee: Stefano Maestri Fix For: 7.2.0.Alpha1 AbstractResourceAdapterDeploymentService needs to check if the recovery module is null before removing it -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-953) Add a WARN for missing <recovery> element

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-953?page=com.atlassian.jira.plugin.... ] Jesper Pedersen commented on JBJCA-953: --------------------------------------- Same goes for datasources without a security definition > Add a WARN for missing <recovery> element > ----------------------------------------- > > Key: JBJCA-953 > URL: https://issues.jboss.org/browse/JBJCA-953 > Project: IronJacamar > Issue Type: Task > Components: Deployer > Affects Versions: 1.0.14.Final, 1.1.0.Beta3 > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 1.0.15.Final, 1.1.0.Beta4 > > > Resource adapters that uses no security or application security needs to have an explicit <recovery> element in order for XA recovery to be enabled -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2012