Kerberos on the HTTP Management API
by Darran Lofthouse
Following on from the discussion yesterday the following branch
illustrated how SPNEGO/Kerberos negotiation can be added to the HTTP API: -
https://github.com/darranl/jboss-as/tree/domain-management/kerberos-negot...
This was more to prove SPNEGO could be added to the HTTP server so tasks
such as long term handling of the cached authentications and providing
the user configuration are outstanding.
This does depend on the use of JAAS for the servers identity to be
established but the actual configuration requirements can be defined
simply so the use of JAAS internally becomes an implementation detail.
One point I have found however is that the SPNEGO authentication is
dependent on identifying the exact connection the inbound request is
received on - I can detect the address of the remote client but I can't
tell if it is just a case of a port being re-used or if it is really the
same connection. Unless we add some form of cookie based session
management this may also be a problem for other authentication mechanisms.
Regards,
Darran Lofthouse.
14 years
the cli status
by Alexey Loubyansky
I started an article on the CLI here
http://community.jboss.org/docs/DOC-16581
which describes the currently supported features. Brian has just pulled
it into the master.
You are welcome to give feedback, compensate my English and doc writing
skills...
Thanks,
Alexey
14 years
Hosts connecting to Hosts other than the Master Domain Controller
by Darran Lofthouse
The connection that is established from hosts to the master domain
controller is using the exposed native API, this API can be exposed on
any host and as has been discussed on another thread can pass requests
up to the master domain controller if it is a domain request not local
to that node.
Could we have a deployment scenario where hosts connect to hosts with
only a slave domain controller and those hosts connect to the master
domain controller?
Something like: -
Host --> Host --> Host(With Master Domain Controller)
Regards,
Darran Lofthouse.
14 years
Operations that aren't really about domain management
by Darran Lofthouse
We will talk more about this in the context of the management API
security but I just quickly wanted to check if it can make sense to
define operations that can be invoked through the management APIs that
are not strictly performing domain management tasks.
e.g. Say we have a master domain controller and a remote node connected
to this domain controller - If there is a task that only the master
domain controller could perform could the remote node make a call to the
master domain controller?
Regards,
Darran Lofthouse.
14 years
Fwd: 7.0.0 Alpha 2 git master build fails while building Messaging subsystem
by Prabaharan Gopalan
Somewhere i did a reply instead of replyAll. :( resending it to the list.
---------- Forwarded message ----------
From: Prabaharan Gopalan <prabugp(a)gmail.com>
Date: Wed, Mar 2, 2011 at 4:12 PM
Subject: Re: [jboss-as7-dev] 7.0.0 Alpha 2 git master build fails while
building Messaging subsystem
To: Carlo de Wolf <cdewolf(a)redhat.com>
In fact I'm looking at the surefire reports and see IllegalAccessErrors.
Attaching the xml to this thread. I hope the attachment gets through.
As for pushing, i didn't know that push does make it to the upstream. (As
you might have figured out by now, i'm new to github as well).
I'll push it shortly.
On Wed, Mar 2, 2011 at 4:03 PM, Carlo de Wolf <cdewolf(a)redhat.com> wrote:
> Pushing it to your github does not make it an actual contribution to the
> upstream. It makes it visible for everybody else.
> Your fork is what you make of it. :-)
>
> Post these failures in the thread, so we can all contemplate. :-)
> Did you look into the surefire reports? Maybe it contains interesting bits
> to attach to the thread.
>
> Carlo
>
>
> I did not push it.. today is my first day with JBoss, and i'm not sure
> whether to do it or not and new to git too.. if it's ok to do, then i'd do
> my first push. :).. moreover, i'm yet to build the AS completely. Now
> getting test failures in Smoke Tests:
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.as.test.surefire.xml.ParseAndMarshalModelsTestCase
> Tests run: 3, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 1.082 sec
> <<< FAILURE
>
> Results :
>
> Tests in error:
>
> testStandaloneXml(org.jboss.as.test.surefire.xml.ParseAndMarshalModelsTestCase)
>
> testDomainXml(org.jboss.as.test.surefire.xml.ParseAndMarshalModelsTestCase)
>
> Tests run: 3, Failures: 0, Errors: 2, Skipped: 0
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] JBoss Application Server: Test Suite: Smoke Tests . FAILURE
> [11.676s]
> [INFO] JBoss Application Server: Web Services Tests Integration Subsystem
> SKIPPED
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 13.196s
> [INFO] Finished at: Wed Mar 02 15:48:26 IST 2011
> [INFO] Final Memory: 38M/91M
>
>
>
> On Wed, Mar 2, 2011 at 3:51 PM, Carlo de Wolf <cdewolf(a)redhat.com> wrote:
>
>> Did you push that fix to your github repo?
>> If it's not already fixed, it might be cherry picked.
>>
>> Carlo
>>
>> I was on JDK 1.6_06. And then saw this:
>> https://issues.jboss.org/browse/JBAS-8649
>>
>> Updated to JDK 1.6_20 and the issue is fixed. But the first one
>> (Messaging subsystem compilation error) is still a valid one.
>>
>> On Wed, Mar 2, 2011 at 12:03 PM, Prabaharan Gopalan <prabugp(a)gmail.com>wrote:
>>
>>> Had talked to dmlloyd and figured the issue is with
>>> the mapper.parseDocument(operations,
>>> XMLInputFactory.newFacotry().createXMLStreamReader(reader));
>>> line SubsystemParsingUnitTestCase class. And which should be newInstance
>>> rather than newFactory.
>>>
>>> Now i modified the code locally, but am getting a new error. This is in
>>> Arquillian common container.
>>>
>>> [ERROR]
>>> \Praba\Work\Workspaces\jboss-as\arquillian\container-common\src\main\java\org\jboss\as\arquillian\container\common\JBossASDeploymentPackager.java:[59,16]
>>> inconvertible types
>>> [ERROR] found : org.jboss.shrinkwrap.api.Archive<capture#607 of ?>
>>> [ERROR] required: org.jboss.shrinkwrap.api.spec.WebArchive
>>>
>>> Trying to find out more why this should be so. Should i be raising JIRA
>>> for these things with the possible fixes? what is the process?
>>>
>>
>>
>>
>> --
>> -GP.
>>
>>
>> _______________________________________________
>> jboss-as7-dev mailing listjboss-as7-dev@lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>>
>>
>
>
> --
> -GP.
>
>
>
--
-GP.
--
-GP.
14 years
AS7 deployment not working
by Richard Opalka
Hi Folks,
I'm getting
---
09:34:56,938 ERROR [org.jboss.as.protocol.connection] (pool-2-thread-1)
Failed to read a message: java.io.EOFException
at org.jboss.as.protocol.StreamUtils.readInt(StreamUtils.java:122)
at
org.jboss.as.controller.remote.ModelControllerOperationHandlerImpl$ExecuteOperation.readRequest(ModelControllerOperationHandlerImpl.java:144)
at
org.jboss.as.protocol.mgmt.ManagementResponse$1.handle(ManagementResponse.java:92)
at
org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:59)
at
org.jboss.as.protocol.ConnectionImpl.safeHandleMessage(ConnectionImpl.java:254)
at
org.jboss.as.protocol.ConnectionImpl$1$1.run(ConnectionImpl.java:213)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
[:1.6.0_20]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
[:1.6.0_20]
at java.lang.Thread.run(Thread.java:636) [:1.6.0_20]
---
against AS7 jboss-as master and archives remote deployment doesn't work :(
Seems this issue have been introduced with Kabir refactoring steps?
Rio
--
Richard Opalka
ropalka(a)redhat.com
JBoss, by Red Hat
Office: +420 222 365 200
Mobile: +420 731 186 942
14 years
Server Instances
by Heiko Braun
Stupid question, but is //host/servers/<xyz> equivalent to a server instance?
Ike
14 years
7.0.0 Alpha 2 git master build fails while building Messaging subsystem
by Prabaharan Gopalan
First off, I am new to this community. So, if i'm not doing something right,
forgive me and help me save myself from having to apologize in the future.
I did a git clone of the master (from git(a)github.com:<user>/jboss-as.git)
and did a build install. I am getting a compilation error in the messaging
subsystem. I don't have maven installed on my machine. And uses the one
comes with jboss. Everything till the messaging subsystem is building
properly.
I am on a 32-bit Win7 machine. And, i could also use any link that explains
the overall architecture and how all these components interact with each
other.
the stacktrace below:
[INFO] JBoss Application Server: Messaging Subsystem ..... FAILURE [3.750s]
[INFO] JBoss Application Server: OSGi Config Admin ....... SKIPPED
[INFO] JBoss Application Server: Security Subsystem ...... SKIPPED
[INFO] JBoss Application Server: Remoting Subsystem ...... SKIPPED
[INFO] JBoss Application Server: Service Archive Subsystem SKIPPED
[INFO] JBoss Application Server: Web Services Subsystem .. SKIPPED
[INFO] JBoss Application Server: Web Services Server Integration Subsystem
SKIPPED
[INFO] JBoss Application Server: Build ................... SKIPPED
[INFO] JBoss Application Server: Arquillian: Common Container SKIPPED
[INFO] JBoss Application Server: Arquillian: Embedded Container SKIPPED
[INFO] JBoss Application Server: Arquillian: Managed Container SKIPPED
[INFO] JBoss Application Server: Arquillian: Remote Container SKIPPED
[INFO] JBoss Application Server: Demos ................... SKIPPED
[INFO] JBoss Application Server: Microcontainer Subsystem SKIPPED
[INFO] JBoss Application Server: OSGi Integration Plugin . SKIPPED
[INFO] JBoss Application Server: Test Suite: Aggregator .. SKIPPED
[INFO] JBoss Application Server: Test Suite: Smoke Tests . SKIPPED
[INFO] JBoss Application Server: Web Services Tests Integration Subsystem
SKIPPED
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 5.965s
[INFO] Finished at: Wed Mar 02 08:39:04 IST 2011
[INFO] Final Memory: 33M/59M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.1:testCompile
(default-testCompile) on project jboss-as-messaging: Compilation failure
[ERROR]
\Praba\Work\Workspaces\jboss-as\messaging\src\test\java\org\jboss\as\messaging\test\SubsystemParsingUnitTestCase.java:[87,56]
cannot find symbol
[ERROR] symbol : method newFactory()
[ERROR] location: class javax.xml.stream.XMLInputFactory
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-compiler-plugin:2.1:testCompile
(default-testCompile) on project jboss-as-messaging: Compila
\Praba\Work\Workspaces\jboss-as\messaging\src\test\java\org\jboss\as\messaging\test\SubsystemParsingUnitTestCase.java:[87,56]
cannot find symbol
symbol : method newFactory()
location: class javax.xml.stream.XMLInputFactory
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:534)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation
failure
\Praba\Work\Workspaces\jboss-as\messaging\src\test\java\org\jboss\as\messaging\test\SubsystemParsingUnitTestCase.java:[87,56]
cannot find symbol
symbol : method newFactory()
location: class javax.xml.stream.XMLInputFactory
at
org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:613)
at
org.apache.maven.plugin.TestCompilerMojo.execute(TestCompilerMojo.java:146)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
[ERROR]
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
Press any key to continue . . .
--
with luv,
GP.
14 years
