2 Replies Latest reply on May 2, 2005 9:26 PM by John Schult

    Netboot from a server that requires Basic Authentication

    Jason Essington Newbie

      I Started fooling with netboot on JBoss 4.0.2rc1 last weekend, and found that it didn't want to netboot from a server that required authentication.

      I fooled around with org.jboss.Main and org.jboss.net.protocol.http.DavURLLister and by adding about 15 lines of code, I managed to get JBoss to netboot with Authentication using a url in the form http://user:pass@someserver.com/webdav/pass@someserver.com/webdav/

      Is netboot even really supported in the 4.x line of servers, or has it been abandoned in favor of some other technology? If so, what replaces the netboot functionality.

      I ask because my current solution has a big problem. The User and password become available on the command line (via ps) and through the system properties (jboss.xxx.url) when the url is registered. There would certainly be a better way to solve the authentication problem, but is it worth the effort if netboot is a waning technology?

      -jason

        • 1. Re: Netboot from a server that requires Basic Authentication
          Scott Stark Master

          Its still supported. The webdav client api needs to be revisted for updates and a more robust mechanism that would allow the authentication info to be obtained in a more opaque fashion would be good.

          • 2. Re: Netboot from a server that requires Basic Authentication
            John Schult Newbie

            Were you able to get 4.0.x to boot any configuration other than 'minimal'? Any configuration I try, all or default, fails miserably.

            The first error I see in the log is:

            =========================================================================
            
             JBoss Bootstrap Environment
            
             JBOSS_HOME: /ms/svc/appserver/jboss4-netboot
            
             JAVA: /ms/local/jdk1.5.0/bin/java
            
             JAVA_OPTS: -server -Dprogram.name=run.sh
            
             CLASSPATH: /ms/svc/appserver/jboss4-netboot/bin/run.jar:/ms/local/jdk1.5.0/lib/tools.jar
            
            =========================================================================
            
            21:03:08,182 INFO [Server] Starting JBoss (MX MicroKernel)...
            21:03:08,183 INFO [Server] Release ID: JBoss [Zion] 4.0.2RC1 (build: CVSTag=JBoss_4_0_2_RC1 date=200503140913)
            21:03:08,184 INFO [Server] Home Dir: /ms/svc/appserver/jboss4-netboot
            21:03:08,184 INFO [Server] Home URL: http://scam/netboot/
            21:03:08,184 INFO [Server] Library URL: http://scam/netboot/lib/
            21:03:08,185 INFO [Server] Patch URL: null
            21:03:08,185 INFO [Server] Server Name: default
            21:03:08,186 INFO [Server] Server Home Dir: /ms/svc/appserver/jboss4-netboot/server/default
            21:03:08,186 INFO [Server] Server Home URL: http://scam/netboot/server/default/
            21:03:08,186 INFO [Server] Server Data Dir: /ms/svc/appserver/jboss4-netboot/server/default/data
            21:03:08,186 INFO [Server] Server Temp Dir: /ms/svc/appserver/jboss4-netboot/server/default/tmp
            21:03:08,187 INFO [Server] Server Config URL: http://scam/netboot/server/default/conf/
            21:03:08,187 INFO [Server] Server Library URL: http://scam/netboot/server/default/lib/
            21:03:08,187 INFO [Server] Root Deployment Filename: jboss-service.xml
            21:03:08,191 INFO [Server] Starting General Purpose Architecture (GPA)...
            21:03:08,693 INFO [ServerInfo] Java version: 1.5.0_01,Sun Microsystems Inc.
            21:03:08,693 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_01-b08,Sun Microsystems Inc.
            21:03:08,693 INFO [ServerInfo] OS-System: Linux 2.4.21-15.ELsmp,i386
            21:03:09,275 INFO [Server] Core system initialized
            21:03:15,227 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
            21:03:15,307 INFO [WebService] Using RMI server codebase: http://dupe.eng.atl.earthlink.net:8083/
            21:03:15,555 INFO [NamingService] Started jndi bootstrap jnpPort=1099, rmiPort=1098, backlog=50, bindAddress=/0.0.0.0, Client SocketFactory=null, Server SocketFactory=org.jboss.net.sockets.DefaultSocketFactory@ad093076
            21:03:15,673 WARN [XMLLoginConfigImpl] End loadConfig, failed to load config: http://scam/netboot/server/default/conf/login-config.xml
            org.jboss.security.auth.login.ParseException: Encountered "<?xml" at line 1, column 1.
            Was expecting one of:
             <EOF>
             <IDENTIFIER> ...
            
             at org.jboss.security.auth.login.SunConfigParser.generateParseException(SunConfigParser.java:389)
            


            The next is:
            21:03:16,757 ERROR [MainDeployer] Could not initialise deployment: http://scam/netboot/server/default/deploy/jboss-aop.deployer/
            org.jboss.deployment.DeploymentException: Failed to find META-INF/jboss-service.xml
            


            The list goes on and on with similar errors. I really hope there is a working example of a configuration other than 'minimal' as we want to be able to use clustering, etc...