You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@esme.apache.org by Richard Hirsch <hi...@gmail.com> on 2011/09/18 13:25:21 UTC

Apache Shiro integration in ESME

Ethan found an interesting blog about Apache Shiro integration in Lift
(http://goo.gl/fb/3kLxZ)

Apache Shiro is a Java security framework (formally known as
JSecurity) and it comes with a fairly abstract set of classes for
building systems that have the familiar users, roles and permissions
setup. There is an interesting write up here with further details:
http://shiro.apache.org/authentication-features.html

Thanks to Vladimir we already have some implemented some features such
as LDAP and container-based authentication.  Should we look at Shiro?

Thoughts?

D.

Re: Playing with 1.3

Posted by Jack Park <ja...@topicquests.org>.
I suppose I exist in lala-land; today, Compass is working fine. It 
created its own file-based /compass-index and seems to be indexing.  The 
present installation uses Derby.

Many thanks
Jack

On 9/27/2011 11:24 PM, Richard Hirsch wrote:
> What database are you using? Derby or something else?
>
> There should be log entries when ESME starts saying that the the
> compass indexes have been created.
>
> INFO - Configuring from resource [/props/compass.cfg.xml]
> INFO - Mapping class [class org.apache.esme.model.Message]
> INFO - Building analyzer [default]
> INFO - Building analyzer [pool]
> INFO - Building analyzer [stemming]
> INFO - Not using highlighter - no highlighter jar included.
> INFO - Starting scheduled optimizer [class org.compass.core.lucene.engine.optimi
> zer.AdaptiveOptimizer] with period [10000ms]
> INFO - Starting scheduled index manager with period [60000ms]
> INFO - Starting scheduled refresh cache with period [5000ms]
>
> I just tried the search on the cloudbees instance (where 1.3 is
> installed) and it works.
>
> D.
>
> On Wed, Sep 28, 2011 at 7:53 AM, Jack Park<ja...@topicquests.org>  wrote:
>> I have a version of ESME online for experiments. There are several messages.
>> When I type one of the words from one of the messages into the search bar,
>> nothing is found. Is Compass actually wired in?
>>
>> Thanks
>> Jack
>>

Re: Playing with 1.3

Posted by Richard Hirsch <hi...@gmail.com>.
What database are you using? Derby or something else?

There should be log entries when ESME starts saying that the the
compass indexes have been created.

INFO - Configuring from resource [/props/compass.cfg.xml]
INFO - Mapping class [class org.apache.esme.model.Message]
INFO - Building analyzer [default]
INFO - Building analyzer [pool]
INFO - Building analyzer [stemming]
INFO - Not using highlighter - no highlighter jar included.
INFO - Starting scheduled optimizer [class org.compass.core.lucene.engine.optimi
zer.AdaptiveOptimizer] with period [10000ms]
INFO - Starting scheduled index manager with period [60000ms]
INFO - Starting scheduled refresh cache with period [5000ms]

I just tried the search on the cloudbees instance (where 1.3 is
installed) and it works.

D.

On Wed, Sep 28, 2011 at 7:53 AM, Jack Park <ja...@topicquests.org> wrote:
> I have a version of ESME online for experiments. There are several messages.
> When I type one of the words from one of the messages into the search bar,
> nothing is found. Is Compass actually wired in?
>
> Thanks
> Jack
>

Re: Playing with 1.3

Posted by Ethan Jewett <es...@gmail.com>.
Hi Jack,

It should be working, but it depends on your setup. I think by default
Compass uses the filesystem as its database, but if your app doesn't
have access to the file system then that will fail. For most shared
hosting deployments you'll probably want to use your database as the
Compass database, which involves creating a database and supplying the
username and password in a configuration file.

I think Dick has configuration for MySQL to run on CloudBees, and
there are lots of examples in the resources/props directory. You can
find them on SVN here:
http://svn.apache.org/viewvc/esme/trunk/server/src/main/resources/props/

Does that help? If you continue having issues, can you post your
compass.cfg.xml file?

Cheers,
Ethan

On Wed, Sep 28, 2011 at 7:53 AM, Jack Park <ja...@topicquests.org> wrote:
> I have a version of ESME online for experiments. There are several messages.
> When I type one of the words from one of the messages into the search bar,
> nothing is found. Is Compass actually wired in?
>
> Thanks
> Jack
>

Playing with 1.3

Posted by Jack Park <ja...@topicquests.org>.
I have a version of ESME online for experiments. There are several 
messages. When I type one of the words from one of the messages into the 
search bar, nothing is found. Is Compass actually wired in?

Thanks
Jack

Re: Apache Shiro integration in ESME

Posted by Ethan Jewett <es...@gmail.com>.
Hi all,

My interest in this is based on the observation that I can think of
the following places where we do authorization in ESME:

1. General access (you must be logged in - stored in database, LDAP,
or container, thanks to Vladimir)
2. Pools (pool membership stored in database (or LDAP?))
3. API super-user (allowed to create user accounts - configured
through property files)

Each of these is handled in a different way with different types of
checks. Our current system is not very complex, so I'm not sure if we
would benefit from a framework like Shiro, but my thought was that it
might push us towards a more consistent approach. That said, I don't
see a pressing need for it at the moment, since things seem to be
working OK.

Just my 2 cents :-)

Ethan

On Sun, Sep 18, 2011 at 1:25 PM, Richard Hirsch <hi...@gmail.com> wrote:
> Ethan found an interesting blog about Apache Shiro integration in Lift
> (http://goo.gl/fb/3kLxZ)
>
> Apache Shiro is a Java security framework (formally known as
> JSecurity) and it comes with a fairly abstract set of classes for
> building systems that have the familiar users, roles and permissions
> setup. There is an interesting write up here with further details:
> http://shiro.apache.org/authentication-features.html
>
> Thanks to Vladimir we already have some implemented some features such
> as LDAP and container-based authentication.  Should we look at Shiro?
>
> Thoughts?
>
> D.
>