April 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4195) Pass through Digest authentication against LDAP

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-4195: ------------------------------------- Summary: Pass through Digest authentication against LDAP Key: AS7-4195 URL: https://issues.jboss.org/browse/AS7-4195 Project: Application Server 7 Issue Type: Task Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.2.0.Alpha1 It is possible for a client to authenticate against an LDAP server using Digest authentication. This task is to make use of this with both our SASL mechanism and HTTP authenticator to provide a pass through check. We need AS7-3691 first and then this needs to be implemented in a way that can consistently be used for both SASL and HTTP Digest. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
2
0 / 0

[JBoss JIRA] (AS7-3691) A Negotiated HTTP Authenticator

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-3691: ------------------------------------- Summary: A Negotiated HTTP Authenticator Key: AS7-3691 URL: https://issues.jboss.org/browse/AS7-3691 Project: Application Server 7 Issue Type: Task Components: Domain Management, Security, Web Reporter: Darran Lofthouse Assignee: Darran Lofthouse Historically we have become constrained by an assumption that there should be a single authentication mechanism assigned to a web application. The HTTP specification however allows for multiple mechanisms to be used in parallel - this task is to investigate the feasibility of writing a single authenticator that is compatible with both JBoss Web and the Sun HTTP server used within AS7 to support a negotiated authentication using a single authenticator backed by a CallbackHandler based realm. The most common example is fallback from SPNEGO to a username / password based mechanism but for domain management we have also a case of trying to use CLIENT-CERT authentication first and then fallback if that is not possible. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
5
0 / 0

[JBoss JIRA] (AS7-4224) Please add a more intuitive way to configure access logging

by Alex Holmansky (JIRA)

Alex Holmansky created AS7-4224: ----------------------------------- Summary: Please add a more intuitive way to configure access logging Key: AS7-4224 URL: https://issues.jboss.org/browse/AS7-4224 Project: Application Server 7 Issue Type: Enhancement Components: CLI, Console Affects Versions: 7.1.0.Final Environment: Windows 7, CentOS 6 Reporter: Alex Holmansky Assignee: Alexey Loubyansky Priority: Minor There's currently no intuitive way to configure access logging in the web subsystem. In the CLI I can get to what seems like the right area: [standalone@localhost:9999 /] cd /subsystem=web/virtual-server=default-host [standalone@localhost:9999 virtual-server=default-host] ls access-log rewrite sso alias=["localhost","example.com"] default-web-module=ROOT.war enable-welcome-root=true and even [standalone@localhost:9999 virtual-server=default-host] cd access-log [standalone@localhost:9999 access-log] pwd /subsystem=web/virtual-server=default-host/access-log but it's absolutely unclear what to do next. In the web Admin Console this should be under Web->Servlet/HTTP->Virtual Servers, but is missing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

5
10
0 / 0

[JBoss JIRA] (AS7-2487) Implementation of a more complex ACL scheme for domain management

by Darran Lofthouse (Created) (JIRA)

Implementation of a more complex ACL scheme for domain management ----------------------------------------------------------------- Key: AS7-2487 URL: https://issues.jboss.org/browse/AS7-2487 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse 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: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
2
0 / 0

[JBoss JIRA] (AS7-2543) JBoss Admin Console Does not allow to modify attributes like Driver

by Vimal Kansal (Created) (JIRA)

JBoss Admin Console Does not allow to modify attributes like Driver ------------------------------------------------------------------- Key: AS7-2543 URL: https://issues.jboss.org/browse/AS7-2543 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Vimal Kansal Assignee: Heiko Braun Once a datasource has been defined, I can not change the driver associated with it on console. Edit button allows editing of only JNDI name and the Connection properties. I can't change the driver. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
1
0 / 0

[JBoss JIRA] (AS7-4287) Console loading is slow over WAN with high ping

by Radim Kolář (JIRA)

Radim Kolář created AS7-4287: -------------------------------- Summary: Console loading is slow over WAN with high ping Key: AS7-4287 URL: https://issues.jboss.org/browse/AS7-4287 Project: Application Server 7 Issue Type: Task Components: Console Affects Versions: 7.1.1.Final Reporter: Radim Kolář Assignee: Heiko Braun Priority: Minor Console loading over WAN network with 250ms ping is very slow. it takes about 1 minute or maybe evenmore to load. I suspect that GWT application is splitted into too many small fragments with GWT splitpoints, which can make loading faster but only if ping time to server is low. On Europe -> USA link it will be very slow. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
5
0 / 0

[JBoss JIRA] (AS7-3694) Allow management client to associate metadata with DeploymentUnit

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-3694: ----------------------------------- Summary: Allow management client to associate metadata with DeploymentUnit Key: AS7-3694 URL: https://issues.jboss.org/browse/AS7-3694 Project: Application Server 7 Issue Type: Feature Request Components: OSGi, Server Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.2.0.Alpha1 Currently there is no way to pass some metadata through the deployment API such that they could show up with the DU. As a client I'd like to say autostart=false and in my DUP I'd like to pick that up and not start a deployment (i.e. a bundle) automatically Generally it should be possible for the client to set some properties for the deployment in a generic way such that they get associated with the DeploymentUnit -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
18
0 / 0

[JBoss JIRA] (AS7-3472) replacing domain controller

by Matej Lazar (JIRA)

Matej Lazar created AS7-3472: -------------------------------- Summary: replacing domain controller Key: AS7-3472 URL: https://issues.jboss.org/browse/AS7-3472 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Affects Versions: 7.1.0.CR1b Reporter: Matej Lazar Assignee: Brian Stansberry Replacing domain controller using operations: /host=node1:remove-local-domain-controller /host=node1:write-remote-domain-controller(host=172.16.254.128, port=9999) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

5
8
0 / 0

[JBoss JIRA] (AS7-4292) Invalid bundle deployment does not fail in domain

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-4292: ----------------------------------- Summary: Invalid bundle deployment does not fail in domain Key: AS7-4292 URL: https://issues.jboss.org/browse/AS7-4292 Project: Application Server 7 Issue Type: Bug Components: Domain Management, OSGi Reporter: Thomas Diesler Assignee: Brian Stansberry Fix For: 7.1.2.Final Running org.jboss.as.test.integration.domain.suites.OSGiBundleLifecyleTestCase Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 35.653 sec <<< FAILURE! on the server I see {code} 15:20:28,619 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit.bad-bundle.STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit.bad-bundle.STRUCTURE: Failed to process phase STRUCTURE of deployment "bad-bundle" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_29] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_29] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_29] Caused by: java.lang.NumberFormatException: For input string: "bogus" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) [rt.jar:1.6.0_29] at java.lang.Integer.parseInt(Integer.java:449) [rt.jar:1.6.0_29] at java.lang.Integer.parseInt(Integer.java:499) [rt.jar:1.6.0_29] at org.osgi.framework.Version.<init>(Version.java:125) at org.osgi.framework.Version.parseVersion(Version.java:218) at org.jboss.osgi.spi.BundleInfo.validateBundleManifest(BundleInfo.java:204) at org.jboss.osgi.spi.BundleInfo.isValidBundleManifest(BundleInfo.java:153) at org.jboss.as.osgi.deployment.OSGiManifestStructureProcessor.deploy(OSGiManifestStructureProcessor.java:63) {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
7
0 / 0

[JBoss JIRA] (AS7-3693) Console does not support install/start semantic for bundles

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-3693: ----------------------------------- Summary: Console does not support install/start semantic for bundles Key: AS7-3693 URL: https://issues.jboss.org/browse/AS7-3693 Project: Application Server 7 Issue Type: Bug Components: Console, Domain Management, OSGi Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: 7.1.1.Final Currently, when deploy a bundle through the console it is started automatically. For a set of bundles it means that you must install them in order otherwise they might not resolve. Digging up the related issues ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
5
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 April 2012