IMHO this is not right... Ideally we should find a way to do this without
replacing existing configuration..

Thanks & regards,
-Prabath

On Thu, Jan 29, 2015 at 8:48 AM, Amalka Subasinghe <[email protected]> wrote:

> [1] says
>
> *Warning*: Installing this feature will result in changes to some of the
> configuration files in Identity Server. The
> <IS_HOME>/repository/conf/identity.xml file and the
> <IS_HOME>/repository/conf/datasources/master-datasouces.xml file will
> lose their current configurations.
>
> [1]
> https://docs.wso2.com/display/CLUSTER420/Configuring+WSO2+Identity+Server+as+the+Key+Manager
>
>
>
> On Thu, Jan 29, 2015 at 3:34 PM, Chamila De Alwis <[email protected]>
> wrote:
>
>> Hi,
>>
>> I have a cluster of two IS nodes (5.0.0), with registry mounting
>> configured. In the worked node, I installed the Key Manager features
>> (1.8.0) and restarted the server. This resulted in the
>> repository/conf/datasources/master-datasources.xml being replaced with a
>> fresh configuration, removing the data source configurations for mounted
>> registry.
>>
>> Is this an expected behavior?
>>
>> Regards,
>> Chamila de Alwis
>> Software Engineer | WSO2 | +94772207163
>> Blog: code.chamiladealwis.com
>>
>>
>>
>> _______________________________________________
>> Dev mailing list
>> [email protected]
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> Amalka Subasinghe
>
> WSO2 Inc.
> Mobile: +94 77 9401267
>
> _______________________________________________
> Dev mailing list
> [email protected]
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,
Prabath

Twitter : @prabath
LinkedIn : http://www.linkedin.com/in/prabathsiriwardena

Mobile : +1 650 625 7950

http://blog.facilelogin.com
http://blog.api-security.org
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to