airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Suresh Marru <sma...@apache.org>
Subject Re: Configuration is bit confusing in airavata
Date Thu, 03 Jan 2013 17:43:23 GMT
+ 1 for consolidating all configurations and having a single place of change for all needed
configurations.

Suresh

On Jan 3, 2013, at 12:38 PM, Lahiru Gunathilake <glahiru@gmail.com> wrote:

> Hi Amila,
> 
> Thanks Amila for clarification. So then we don't need authenticators.xml in
> axis2 webapp, I think I am clear with rest service configuration.
> 
> In airavata I can see still two places with registry database
> configuration, which are registry.properties file and
> airavata-server.properties file. Why do we need two places to configure
> registry database.
> 
> Laihru
> On Thu, Jan 3, 2013 at 12:31 PM, Amila Jayasekara
> <thejaka.amila@gmail.com>wrote:
> 
>> Hi Lahiru,
>> 
>> On Thu, Jan 3, 2013 at 12:22 PM, Lahiru Gunathilake <glahiru@gmail.com>
>> wrote:
>>> Hi Devs,
>>> 
>>> I have been trying to configure airavata to point to mysql with a trunk
>>> build and I have seen 5 places with some database configuration for
>>> registry database.
>>> 
>>> In axis2 web apps I can see, authentication.xml, registry.properties,
>>> airavata-server.properties to configure with database configuration.
>> 
>> I am not quite sure why we are having an authenticators.xml file in
>> axis2. Need to see distribution configurations where it is coming
>> from. This we dont need at all. We can remove it and we dont need to
>> configure it as well.
>> 
>>> 
>>> In rest service I can see authentication.xml, registry.properties with
>>> database configuration. I think its alright to have two places to
>> configure
>>> this since we have two separate webapps, but all the other places looks
>>> like redundant.
>> 
>> We only need authenticators.xml in rest service. In a practical
>> scenario the authenticator will point to a user store which is
>> different from airavata database. Therefore we need to specify user
>> store information separately.
>> 
>> Thanks
>> Amila
>> 
>>> 
>>> Regards
>>> Lahiru
>>> 
>>> --
>>> System Analyst Programmer
>>> PTI Lab
>>> Indiana University
>> 
> 
> 
> 
> -- 
> System Analyst Programmer
> PTI Lab
> Indiana University


Mime
View raw message