[JBoss JIRA] (AS7-3464) add-user.sh - possibility of setting another Realms should be considered again
by Tom Fonteyne (JIRA)
[ https://issues.jboss.org/browse/AS7-3464?page=com.atlassian.jira.plugin.s... ]
Tom Fonteyne commented on AS7-3464:
-----------------------------------
Just wondering if it would not be better/cleaner to create a CLI command for this instead of the script ?
I know that assumes an initial connection from localhost to be able to add the first user.
> add-user.sh - possibility of setting another Realms should be considered again
> ------------------------------------------------------------------------------
>
> Key: AS7-3464
> URL: https://issues.jboss.org/browse/AS7-3464
> Project: Application Server 7
> Issue Type: Bug
> Components: Security
> Affects Versions: 7.1.0.CR1b
> Reporter: Pavel Janousek
> Assignee: Darran Lofthouse
> Priority: Minor
> Fix For: 7.2.0.Alpha1
>
>
> I'm aware of add-user.sh isn't general tool for managing an user/groups/roles credential store at all. Is it supposed only as shorthand for quick definition of users access to admin console out of the box. Well..
> According previous paragraph it isn't to much meaningful for me to bring possibility of specify another realm during the invocation of this tool. I think already - Admin console can use another realm than ManagementRealm by change default configuration. I think already too - property file can't contain users definition belong multiple realms. As is stated in comment in the begin of file mgmt-users.properties, this file is for "declaration of users for the realm 'ManagementRealm'".
> I think we should avoid to insert new user with different realm there (it is possible now). add-user.sh doesn't manage any other file and other property file(s) can't be specified during invocation.
> I think this present situation/behavior should confuse hard our end-users - especially users with their own experiences with other JEE servers (Apache Geronimo, Sun/Oracle GlassFish etc.).
> Because we don't provide/support any tool for general CRUD managing of credential store of type like property file(s) - like other JEE app. servers do, we really should use this script/tool only as way to simple very basic user creation in default AS7 environment, because we can't support this tool in any other situation with present behavior and in a such changed environments behavior or final state is hardly understandable (if we create property file (by other way) with the same username, but in different realms, we can't log to admin console never more; if we have users in one realm, switch AS7 instance to use other "admin" realm, we can't add any from existing user to this new realm; we don't know which user belongs to which realm later etc.)
> So conclusion - I think we should remove specification of Realm from input process of add-user.sh script at all and use this script only to define users belongs to ManagementRealm realm and manages only properly mgmt-users.properties files (standalone and domain configuration)
--
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, 10 months
[JBoss JIRA] (AS7-4837) JMXPropertyEditorsTestCase fails JDK7
by Tomaz Cerar (JIRA)
Tomaz Cerar created AS7-4837:
--------------------------------
Summary: JMXPropertyEditorsTestCase fails JDK7
Key: AS7-4837
URL: https://issues.jboss.org/browse/AS7-4837
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.2.Final (EAP)
Environment: Oracle JDK7
Reporter: Tomaz Cerar
Assignee: Bartosz Baranowski
Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1
There are many tests that fail on JDK7
maven report:
{noformat}
Failed tests: testAtomicBoolean(org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase): Found null attribute value for 'AtomicBoolean'
testAtomicInteger(org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase): Found null attribute value for 'AtomicInteger'
testAtomicLong(org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase): Found null attribute value for 'AtomicLong'
testBigDecimal(org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase): Found null attribute value for 'BigDecimal'
testBigInteger(org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase): Found null attribute value for 'BigInteger'
testClazz(org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase): Found null attribute value for 'Clazz'
testFile(org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase): Found null attribute value for 'File'
testLocale(org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase): Found null attribute value for 'Locale'
testURI(org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase): Found null attribute value for 'URI'
testURL(org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase): Found null attribute value for 'URL'
testCharacterArray(org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase): Found null attribute value for 'CharacterArray'
testClassArray(org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase): Found null attribute value for 'ClassArray'
testInetAddress(org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase): Found null attribute value for 'InetAddress'
testInetAddressArray(org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase): Found null attribute value for 'InetAddressArray'
testObjectCharacter(org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase): Found null attribute value for 'ObjectChar'
testProperties(org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase): Found null attribute value for 'Properties'
Tests in error:
testChar(org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase): Could not deploy to container: {(..)
{noformat}
--
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, 10 months
[JBoss JIRA] (AS7-5347) javax.naming.Context.list("java:module") failed
by Cheng Fang (JIRA)
Cheng Fang created AS7-5347:
-------------------------------
Summary: javax.naming.Context.list("java:module") failed
Key: AS7-5347
URL: https://issues.jboss.org/browse/AS7-5347
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.1.Final
Reporter: Cheng Fang
Assignee: Eduardo Martins
In a simple web app with ejb packaged in, invoke InitialContext.list("java:module") within a servlet service method failed with the following exception:
{noformat}
23:26:18,642 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/test].[test.TestServlet]] (http-/127.0.0.1:8080-1) Servlet.service() for servlet test.TestServlet threw exception: java.lang.RuntimeException: javax.naming.NamingException: JBAS014558: No EjbContext available as no EJB invocation is active [Root exception is java.lang.IllegalStateException: JBAS014558: No EjbContext available as no EJB invocation is active]
at test.NamingTest.list(NamingTest.java:53) [classes:]
at test.TestServlet.doListing(TestServlet.java:28) [classes:]
at test.TestServlet.processRequest(TestServlet.java:22) [classes:]
at test.TestServlet.doGet(TestServlet.java:44) [classes:]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [jboss-servlet-api_3.0_spec-1.0.2.Final.jar:1.0.2.Final]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final.jar:1.0.2.Final]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.16.Final.jar:]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.16.Final.jar:]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.16.Final.jar:]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.16.Final.jar:]
at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:156) [jboss-as-web-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.16.Final.jar:]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.16.Final.jar:]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.16.Final.jar:]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.16.Final.jar:]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.16.Final.jar:]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:679) [jbossweb-7.0.16.Final.jar:]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931) [jbossweb-7.0.16.Final.jar:]
at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_33]
Caused by: javax.naming.NamingException: JBAS014558: No EjbContext available as no EJB invocation is active [Root exception is java.lang.IllegalStateException: JBAS014558: No EjbContext available as no EJB invocation is active]
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:135)
at org.jboss.as.naming.ServiceBasedNamingStore.list(ServiceBasedNamingStore.java:166)
at org.jboss.as.naming.NamingContext.list(NamingContext.java:288)
at org.jboss.as.naming.InitialContext.list(InitialContext.java:161)
at org.jboss.as.naming.NamingContext.list(NamingContext.java:304)
at javax.naming.InitialContext.list(InitialContext.java:436) [classes.jar:1.6.0_33]
at test.NamingTest.list(NamingTest.java:51) [classes:]
... 18 more
Caused by: java.lang.IllegalStateException: JBAS014558: No EjbContext available as no EJB invocation is active
at org.jboss.as.ejb3.context.CurrentInvocationContext.getEjbContext(CurrentInvocationContext.java:48) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.ejb3.deployment.processors.EjbContextJndiBindingProcessor$1.getInstance(EjbContextJndiBindingProcessor.java:120) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:133)
... 24 more
{noformat}
--
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, 10 months
[JBoss JIRA] (AS7-5409) CLONE - Unable to disable -Djava.net.preferIPv4=true in domain mode without editing domain.conf
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-5409?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry moved JBPAPP-9726 to AS7-5409:
-----------------------------------------------
Project: Application Server 7 (was: JBoss Enterprise Application Platform)
Key: AS7-5409 (was: JBPAPP-9726)
Workflow: GIT Pull Request workflow (was: jira)
Affects Version/s: 7.1.2.Final (EAP)
(was: EAP 6.0.0 ER 5)
Release Notes Docs Status: (was: Documented as Known Issue)
Release Notes Text: (was: If you use a command-line argument to bind to an IPv6 address at start-up, the server fails to start with the default configuration. The preferred workaround is to set the bind address in the configuration file, either <filename>domain.xml</filename> or <filename>standalone.xml</filename>. If you need to pass the IP address on the command line, add the <code>java.net.preferIPv4Stack=false</code> setting to your command. The following is an example of such a command.)
Component/s: Domain Management
(was: System)
(was: Documentation)
(was: Server boot)
Security: (was: Public)
Fix Version/s: 7.1.3.Final (EAP)
7.2.0.Alpha1
(was: TBD EAP 6)
Docs QE Status: (was: NEW)
> CLONE - Unable to disable -Djava.net.preferIPv4=true in domain mode without editing domain.conf
> -----------------------------------------------------------------------------------------------
>
> Key: AS7-5409
> URL: https://issues.jboss.org/browse/AS7-5409
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 7.1.2.Final (EAP)
> Reporter: Jan Martiska
> Assignee: Brian Stansberry
> Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1
>
>
> Try running EAP domain mode like this:
> {noformat}
> bin/domain.sh -Djava.net.preferIPv4Stack=false -bmanagement=::1
> {noformat}
> It will fail:
> {noformat}
> [Host Controller] 09:40:49,647 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.network.management: org.jboss.msc.service.StartException in service jboss.network.management: JBAS015810: failed to resolve interface management
> [Host Controller] at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:97) [jboss-as-server-7.1.1.Final-redhat-1.jar:7.1.1.Final-redhat-1]
> [Host Controller] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
> [Host Controller] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
> [Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30]
> [Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30]
> [Host Controller] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
> {noformat}
> Other interfaces work and can be bound to ipv6, just 'management' does not. (In standalone mode, this issue is not present.)
> Blocks testing of Admin console,Native+HTTP interfaces in domain mode in IPv6, not marking as blocker because workaround exists.
--
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, 10 months