Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #223 (closed)

Opened 16 years ago

Closed 15 years ago

Installation should respect omero.rootpass option of etc/local.properties

Reported by: jamoore Owned by: jamoore
Priority: critical Milestone: 3.0-M3
Component: Security Version: 3.0-M3
Keywords: iteration6 Cc:
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.


Currently the root password is always set to "ome" and the omero.rootpass property is only used for client-side root login. The installatino process should also respect this value.

Change History (5)

comment:1 Changed 16 years ago by jmoore

  • Keywords iteration6 added

comment:2 Changed 16 years ago by jmoore

r1011 refactors the build to take care of this.

It was necessary to take the <reload-db/> task out of /common and put it into /server to have access to AdminImpl?. To accomplish this, there's now a new ant property sql.dir where the generated sql lives. The server task copies that locally and replaces the @ROOTPASS@ token with the value of etc/local.properties:omero.rootpass.

The other thing that was "necessary" was to update /server's classpath to include jbossall-client.jar since org.jboss.security.Util references org.jboss.logger.Logger (ack). (This was also the exception being thrown in AdminTest.) Having jbossall-client.jar in the server is not all so horrible, since it allows server code to make EJB calls (in the long term, a good thing)

comment:3 Changed 16 years ago by jmoore

  • Resolution set to fixed
  • Status changed from new to closed

comment:4 Changed 15 years ago by jmoore

  • Keywords iteration3 added; iteration6 removed
  • Milestone changed from 3.0-M3 to 3.0-Beta2
  • Priority changed from major to critical
  • Resolution fixed deleted
  • Status changed from closed to reopened

I take that back. Having jbossall-client.jar in the server may be doing crazy things to ant. Keyword:

java.lang.LinkageError: loader constraints violated when linking org/xml/sax/Locator class

Looking into it.

comment:5 Changed 15 years ago by jmoore

  • Keywords iteration6 added; iteration3 removed
  • Milestone changed from 3.0-Beta2 to 3.0-M3
  • Resolution set to fixed
  • Status changed from reopened to closed

Nope. Groovy is the culprit (see the complaints in #104). New ticket created as #641. Re-closing this.

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.67804 sec.)

We're Hiring!