On Tue, Feb 17, 2015 at 10:55 AM, KasunG Gajasinghe wrote:
>
> There's a parameter called allowRoles that can be used to enforce roles.
> It could contain a comma separated roles list. But, I believe it would be
> much cleaner if the roles can also be included in the RampartConfig of the
> policy
There's a parameter called allowRoles that can be used to enforce roles. It
could contain a comma separated roles list. But, I believe it would be much
cleaner if the roles can also be included in the RampartConfig of the
policy.
ESB can go ahead with this approach. Security wizard already resides
OK, lets go ahead with this. The initial plan is to write this for STS only
so that IS can own this. But If ESB also need this, where are we going to
maintain this?
On Mon, Feb 16, 2015 at 11:53 AM, Johann Nallathamby
wrote:
> [Adding Godwin to the thread]
>
> IS team has already started working
[Adding Godwin to the thread]
IS team has already started working on this targeting the IS 5.1.0 release
on Git based on carbon-kernel 4.3.0.
Following are items we will be doing.
1. We will continue using the security wizard to apply STS policies and
persist it to registry.
2. Previously the s
On Sun, Jul 6, 2014 at 3:12 PM, Johann Nallathamby wrote:
> Hi Kishanthan,
>
>
> On Tue, Jul 1, 2014 at 8:03 PM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>> Hi All,
>>
>> We recently had a meeting on $subject. Our current story for CApp (Carbon
>> Application) development approach
On Sun, Jul 6, 2014 at 3:12 PM, Johann Nallathamby wrote:
> Hi Kishanthan,
>
>
> On Tue, Jul 1, 2014 at 8:03 PM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>> Hi All,
>>
>> We recently had a meeting on $subject. Our current story for CApp (Carbon
>> Application) development approach
Hi Kishanthan,
On Tue, Jul 1, 2014 at 8:03 PM, Kishanthan Thangarajah
wrote:
> Hi All,
>
> We recently had a meeting on $subject. Our current story for CApp (Carbon
> Application) development approach is broken when including application of
> QoS for services. This was mainly due to the issues
On Tue, Jul 1, 2014 at 8:03 PM, Kishanthan Thangarajah
wrote:
> Hi All,
>
> We recently had a meeting on $subject. Our current story for CApp (Carbon
> Application) development approach is broken when including application of
> QoS for services. This was mainly due to the issues we faced with,
>
Hi All,
We recently had a meeting on $subject. Our current story for CApp (Carbon
Application) development approach is broken when including application of
QoS for services. This was mainly due to the issues we faced with,
- the file-based metadata persistence layer for services.
- the possibilit
