Would it be possible to protect the database via Apache Shiro after AURORA-351 <https://issues.apache.org/jira/browse/AURORA-351> is complete?
On Tue, Sep 16, 2014 at 9:58 AM, Bill Farner <wfar...@apache.org> wrote: > Since beginning migration of the internal database to H2, i've wanted to > include the H2 web console [1] as a means for debugging the internal > scheduler state. If we do that, we need to password-protect the database > to prevent unauthorized tinkering. > > Does anybody have a preference for where the scheduler gets that password? > The obvious choices are directly on the command line, or from a file > referenced on the command line. However, i'm open to ideas i haven't > thought of. > > [1] http://www.h2database.com/html/quickstart.html#h2_console > (ignore the windows/launching instructions - we will embed it as a servlet) > > > -=Bill > -- Zameer Manji
