Hi all,
These are the design decisions taken in architectural discussion.
*In IS point of view*
- SP can be created with or without authorization policy.
- When list down the Federated authenticators of each SP, user can be
define the authorization policy for each authenticator.
- Au
+1
Thanks & regards,
-Prabath
On Mon, Sep 21, 2015 at 8:46 PM, Ishara Karunarathna
wrote:
> Hi Prabath,
>
> On Mon, Sep 21, 2015 at 8:25 PM, Prabath Siriwardena
> wrote:
>
>>
>>
>> On Mon, Sep 21, 2015 at 12:49 AM, Ishara Karunarathna
>> wrote:
>>
>>> Hi Prabath,
>>>
>>> On Mon, Sep 21, 2015
On Tue, Sep 22, 2015 at 10:45 AM, Sachith Withana wrote:
> Yes. Hector is deprecated now and DataStax recommends using CQL.
> But I went ahead and used Hector for the implementation since it is for a
> Cassandra 1.x
> and BAM also uses Hector driver in its impementation.
>
+1 'Hector' would ne
Yes. Hector is deprecated now and DataStax recommends using CQL.
But I went ahead and used Hector for the implementation since it is for a
Cassandra 1.x
and BAM also uses Hector driver in its impementation.
On Mon, Sep 21, 2015 at 11:02 AM, Ramith Jayasinghe wrote:
> From what I know, for any n
On Mon, Sep 21, 2015 at 8:44 PM, Rajith Vitharana wrote:
> Hi Prabath,
>
> Sorry I missed the mail, yes it would be great if we can talk about this
> further.
>
>
>
> On Tue, Sep 22, 2015 at 1:54 AM, Prabath Siriwardena
> wrote:
>
>> Having a direct connection with IS is not mandatory...
>>
>> T
Hi Prabath,
On Mon, Sep 21, 2015 at 8:25 PM, Prabath Siriwardena
wrote:
>
>
> On Mon, Sep 21, 2015 at 12:49 AM, Ishara Karunarathna
> wrote:
>
>> Hi Prabath,
>>
>> On Mon, Sep 21, 2015 at 12:09 PM, Prabath Siriwardena
>> wrote:
>>
>>> It looks like from the architecture, whether its a dumb or
Hi Prabath,
Sorry I missed the mail, yes it would be great if we can talk about this
further.
On Tue, Sep 22, 2015 at 1:54 AM, Prabath Siriwardena
wrote:
> Having a direct connection with IS is not mandatory...
>
> The Trusted IdP is a proxy - a representation of the external Identity
> Provi
Having a direct connection with IS is not mandatory...
The Trusted IdP is a proxy - a representation of the external Identity
Provider, in DSS itself...
Thanks & regards,
-Prabath
On Mon, Sep 21, 2015 at 1:19 PM, Nuwan Bandara wrote:
>
>
> On Mon, Sep 21, 2015 at 2:31 PM, Prabath Siriwardena
On Mon, Sep 21, 2015 at 2:31 PM, Prabath Siriwardena
wrote:
> If I understand your requirement correctly, this is about a federation
> scenario, where users are not under the domain of DSS.
>
> I guess we need to fix couple of things here..
>
> When I last looked into DSS - the way the DSS picks
At the moment you can write custom authenticators and plug that into the
system - and it would be specific endpoint to the service provider.
But, the challenge adding SP specific configurations - at the moment the IS
Service Provider does not pick custom inbound authenticator configurations.
I gu
If I understand your requirement correctly, this is about a federation
scenario, where users are not under the domain of DSS.
I guess we need to fix couple of things here..
When I last looked into DSS - the way the DSS picks the username is from
the UT header - and the DS must be secured with UT
On Mon, Sep 21, 2015 at 12:49 AM, Ishara Karunarathna
wrote:
> Hi Prabath,
>
> On Mon, Sep 21, 2015 at 12:09 PM, Prabath Siriwardena
> wrote:
>
>> It looks like from the architecture, whether its a dumb or smart is a
>> decision made at the SCIM level, not at the provisioning framework level..
>
Hi,
This email is with reference to the mail with heading “[MSS] [Carbon 5]
[netty-http] JAX-RS Engine implementation”
When deploying a JAX-RS artifact in netty-http service, first we need to
discover all the JAX-RS resource classes inside the artifact and initialise
them. For that, following opt
Hi,
In MSS based on Carbon 5, netty-http is used on top of netty for the JAX-RS
engine. Here, netty-http provides JAX-RS annotation processing
functionality using reflection. But the way that netty-http supports JX-RS
resource classes is bit too much coupled with netty-http implementation.
IE in
Yes. The Protocol is SyncML.
http://technical.openmobilealliance.org/Technical/release_program/docs/Common/V1_2_2-20090724-A/OMA-TS-SyncML-RepPro-V1_2_2-20090724-A.pdf
On Mon, Sep 21, 2015 at 4:16 PM, Dulitha Wijewantha
wrote:
>
>
> On Monday, September 21, 2015, Dileesha Rajapakse
> wrote:
>
On Monday, September 21, 2015, Dileesha Rajapakse wrote:
> *Android OMA-DM Standardization*
>
> *OVERVIEW*
>
> As per the current architecture of the Android Component of the WSO2 MDM
> framework, Android mobile devices are managed using a custom built client
> application installed on the device
*Android OMA-DM Standardization*
*OVERVIEW*
As per the current architecture of the Android Component of the WSO2 MDM
framework, Android mobile devices are managed using a custom built client
application installed on the device. Server to Client communication is done
over HTTP and the devices are
Hi Prabath,
On Mon, Sep 21, 2015 at 12:09 PM, Prabath Siriwardena
wrote:
> It looks like from the architecture, whether its a dumb or smart is a
> decision made at the SCIM level, not at the provisioning framework level..
> Is that right..?
>
Yes.
With the current implementation provisioning fra
Hi Lahiru,
As Danushka mentioned, lets focus only on 2nd option where we configure
workflows for all tenants not per tenant. Few reasons to choose option 2,
1. If we allow per tenant workflows, we need to enable mechanism to upload,
configure AF runtime servers and it should not cause any issues t
I thought we are going for a common workflow for all tenants which is
similar to what we have currently.
Thanks & Regards
Danushka Fernando
Senior Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729
On Mon, Sep 21, 2015 at 11:34 AM, Lahiru Manohara wrote:
> Hi All,
>
> The AppFac
These are the Improvements identified during the Design Review;
- UI for specifying throttling limits will be moved to Manage Page.
- Rather than providing two text fields to specify Unit Time and
MaxRequest count, there'd be single filed to specify Transactions Per
Second. (This is do
21 matches
Mail list logo
