Re: [Architecture] WSO2 Enterprise Mobility Manager 2.0.1 is released

[Kamidu Punchihewa]

Hi All,

Adding architecture group.

Thanks and Regards,

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


Disclaimer: This communication may contain privileged or other confidential
information and is intended exclusively for the addressee/s. If you are not
the intended recipient/s, or believe that you may have received this
communication in error, please reply to the sender indicating that fact and
delete the copy you received and in addition, you should not print, copy,
retransmit, disseminate, or otherwise use the information contained in this
communication. Internet communications cannot be guaranteed to be timely,
secure, error or virus-free. The sender does not accept liability for any
errors or omissions.

On Wed, Mar 16, 2016 at 11:18 AM, Kamidu Punchihewa 
wrote:

> WSO2 Enterprise Mobility Manager 2.0.1 is released!
>
> WSO2 Enterprise Mobility Manager (WSO2 EMM) is a 100% open source,
> comprehensive platform that addresses mobile computing challenges which
> enterprises face today. WSO2 EMM supports iOS, Android & Windows devices
> and helps organizations deal with both "corporate-owned,
> personally-enabled" (COPE) devices and employee owned devices with the
> "bring-your-own-device" (BYOD) ownership schemes.
>
> Built on a generic device management framework (i.e. WSO2 Connected Device
> Management Framework) that can be extended to support many other device
> platforms, WSO2 EMM offers better scalability with its rich architecture,
> supporting horizontal as well as vertical scaling of associated components.
> Whether it is device configuration management, policy enforcement,
> app-management, device data security or compliance monitoring, WSO2 EMM
> offers a single enterprise grade platform for all your mobile computing
> needs.
>
>
> What features are on offer?
>
> Mobile Device Management (MDM)
>
>
>-
>
>Self-service device enrollment and management with WSO2 EMM end-user
>console for iOS, Android and Windows devices
>-
>
>Integrates to enterprise identity systems for device ownership: LDAP,
>Microsoft AD
>-
>
>Policy-driven device and profile management for security, data, and
>device features (Camera, Password Policy)
>-
>
>Deploy policies over-the-air
>-
>
>Compliance monitoring for applied policies on devices.
>-
>
>Role-based access control (RBAC) for device management
>-
>
>Securely wipe enterprise configurations using Enterprise wipe
>-
>
>Track locations of enrolled devices
>-
>
>Retrieve device information
>-
>
>Configure network settings
>-
>
>Facilitate device-owner operations such as registering and
>unregistering devices, installing, rating, sorting mobile apps, etc
>
>
> Mobile App Management
>
>
>-
>
>App approval process through a lifecycle
>-
>
>Provision and de-provisioning apps to enrolled devices
>-
>
>Provision apps to enrolled devices based on roles
>-
>
>Provision apps to multiple enrolled devices per user
>-
>
>Retrieve list of apps
>-
>
>Install new apps and update existing apps on iOS devices via REST
>APIs, enabling automation of application installation/updates for third
>party systems / vendors
>-
>
>Install Web clips on devices. Shortcuts to a web app can be installed
>on a device via this feature
>-
>
>Enterprise App Store
>-
>
>Discover mobile apps through an Enterprise App Store
>-
>
>Self-provisioning of mobile apps to devices
>-
>
>Rating and Sorting Applications
>
>
> Device and Data Security
>
>
>-
>
>Enforce built-in security features of passcode protection
>-
>
>Encryption of data storage
>-
>
>Device lock and reset
>-
>
>Managed APIs to perform administrative functions
>
>
> iOS Features
>
>
>-
>
>Self-service device enrollment and management with WSO2 EMM end-user
>console via iOS agent or Web interface for versions up to iOS 9 SDK
>-
>
>Facilitate remote notifications via Apple Push Notification Service
>(APNS)
>-
>
>New iOS Version Support
>-
>
>Tracking iOS Device
>-
>
>Configuring cellular network settings
>-
>
>Device profile management
>-
>
>Retrieving device info
>-
>
>Device lock
>-
>
>Automatic WiFi configuration
>-
>
>AirPlay
>-
>
>Restrictions (60+ operations are supported)
>-
>
>Enterprise WIPE
>-
>
>Setup APN
>-
>
>Setup LDAP
>-
>
>Setup email accounts
>-
>
>Setup CalDav
>-
>
>Calendar subscription
>-
>
>Passcode policy
>-
>
>Clear passcode
>-
>
>App installation and update
>-
>
>Retrieve app list
>-
>
>Web clip installation
>-
>
>Supports App management
>-
>
>Setup email accounts
>-
>
>Subscribe for

Re: [Architecture] [Pet Project] Velocity Template Mediator for ESB

[Chanaka Fernando]

Hi Asanka,

I had a look into the feature set and it looks really useful. Please send
us a PR and we will include this in a future ESB release.

On Wed, Mar 16, 2016 at 9:05 AM, Asanka Dissanayake 
wrote:

> Hi All,
> I am developing a new Mediator for ESB as a pet project. After noticing
> some draw backs in Payload Factory I thought of writing this one.
>
> Code can be found at :
> https://github.com/asanka88/VelocityTemplateMediator
>
> @ESB Team:
> If this make any sense, I am more than happy to contribute this with more
> improvements. This is still under development. I will upload samples soon.
> Your feedback is highly appreciated.
> Why Velocity Template Mediator ?
>
> Currently synapse comes with built in payloadFactory mediator. But there
> are several drawbacks in it.
>
> 1 Doesn’t support arrays : You cannot iterate though an array/collection
> and add those elements to the payload.
>
> 2 Doesn’t support conditional expressions: In case you want to add
> elements based on conditions payloadFactory doesn’t support it.
>
> 3 Readability is less since numbered placeholders like $1,$2 are used
>
> How
> Velocity Template Mediator solve them?
>
> Velocity template mediator uses well known Apache Velocity as the template
> engine. You can do whatever you can do with Velocity in side this. Iterate
> through collections, check conditions etc. In addition to that since we are
> using place holders like $name,$age for the variables ,so it improves the
> readability as well.
>
> On the other hand, there was no such a thing in Synapse to create a
> property out of a template.
>
> For Example: When you call a soap back end, suppose you have to send a
> user name token in SOAP Header. Suppose there are several back end calls
> you need to make and in every call you need to pass the user name token.
>
> With the payload factory , you will have to create that part every time.
> Instead if you can create a property one time using a template and save it
> in the message context , you can reuse it without generating again and
> again.
>
> With the Velocity Template Mediator , it supports body,property,soap
> header,envelope as the targets. You can put the generated output to anyof
> these. And it supports both xml and json formats
>
> Sample Syntax
>
> 
>
>   
>  $name
>  $age
>   
>
>
>   
>   
>
> property-type="string|om" scope="synapse|axis2|operation" />
> 
>
>
> Thanks,
> Asanka D
>
> --
>
>
> *Asanka DissanayakeSoftware Engineer*
> *WSO2 Inc. - lean . enterprise . middleware |  wso2.com *
>
> *email: asan...@wso2.com ,   blog:
> cyberwaadiya.blogspot.com
> , asankastechtalks.wordpress.com
>   mobile: +94 71 8373821*
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Thank you and Best Regards,
Chanaka Fernando
Senior Technical Lead
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 773337238
Blog : http://soatutorials.blogspot.com
LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
Twitter:https://twitter.com/chanakaudaya
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [Dev] [BPS] Rendering information of the current task of a BPMN process instance

[Dilini Mihindra]

Hi all,

Thank you for the suggestion. Current implementation does not use REST API.
I completed the above task and now I am working on rendering information
through REST API.

Thank you.

Dilini Mihindra Mampitiya Arachchi
Intern - Software Engineer
Mobile: +94 710 420 550
Email: dili...@wso2.com

On Tue, Mar 15, 2016 at 5:46 PM, Waruna Jayaweera  wrote:

> Hi,
> Yes. It is better if we can expose rendering information through rest api.
> These data will be helpful when integrating bps runtime with process center
> too.
>
> Thanks,
> Waruna
>
> On Tue, Mar 15, 2016 at 5:30 PM, Vinod Kavinda  wrote:
>
>> Hi,
>> Are we exposing these information via REST api? It's better to expose
>> everything in REST first. Then we can build the UI as relevant, later.
>>
>> Regards,
>> Vinod
>> On Mar 15, 2016 1:14 PM, "Nandika Jayawardana"  wrote:
>>
>>> Lets implement this for bpmn explorer as well.  However, both would
>>> change when we move to C5.
>>>
>>> Regards
>>> Nandika
>>>
>>> On Tue, Mar 15, 2016 at 12:31 PM, Vinod Kavinda  wrote:
>>>
 [Adding Architecture@]
 Hi DiliniM,
 As we are planning on dropping the admin UIs with C5, is there a use of
 integrating this with admin console UI? Shall we do this in our BPMN
 explorer UI?

 Regards,
 Vinod

 On Tue, Mar 15, 2016 at 12:24 PM, Dilini Mihindra 
 wrote:

> Hi all,
>
> I am working on rendering the information of the current task of an
> active BPMN process instance. As supported by Activiti, the process 
> diagram
> of an active process instance is given as following:
>
>
>*Figrue 1 - The process instance diagram
> of *
> * an active BPMN process instance*
>
> The current task of the process instance is highlighted by a red
> boarder in the given process diagram. I am working on rendering the
> information of this current task in the instance_list_view.jsp page so 
> that
> the users can get a clear idea on the current task.
>
> The following properties are displayed regarding each task:​
>
>
>- Task Key
>- Task Name
>- Assignee
>- Description
>- Category
>- Due Date
>- Form Key
>- Owner
>- Priority
>- Skip
>- Candidate Group Ids
>- Candidate User Ids
>
> Thank you.
>
>
> Dilini Mihindra Mampitiya Arachchi
> Intern - Software Engineer
> Mobile: +94 710 420 550
> Email: dili...@wso2.com
>
> ___
> Dev mailing list
> d...@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Vinod Kavinda
 Software Engineer
 *WSO2 Inc. - lean . enterprise . middleware .*
 Mobile : +94 (0) 712 415544
 Blog : http://soatechflicks.blogspot.com/


 ___
 Architecture mailing list
 Architecture@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture


>>>
>>>
>>> --
>>> Nandika Jayawardana
>>> WSO2 Inc ; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> ___
>>> Dev mailing list
>>> d...@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>> ___
>> Dev mailing list
>> d...@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Regards,
>
> Waruna Lakshitha Jayaweera
> Software Engineer
> WSO2 Inc; http://wso2.com
> phone: +94713255198
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

[Architecture] [Pet Project] Velocity Template Mediator for ESB

[Asanka Dissanayake]

Hi All,
I am developing a new Mediator for ESB as a pet project. After noticing
some draw backs in Payload Factory I thought of writing this one.

Code can be found at : https://github.com/asanka88/VelocityTemplateMediator

@ESB Team:
If this make any sense, I am more than happy to contribute this with more
improvements. This is still under development. I will upload samples soon.
Your feedback is highly appreciated.
Why Velocity Template Mediator ?

Currently synapse comes with built in payloadFactory mediator. But there
are several drawbacks in it.

1 Doesn’t support arrays : You cannot iterate though an array/collection
and add those elements to the payload.

2 Doesn’t support conditional expressions: In case you want to add elements
based on conditions payloadFactory doesn’t support it.

3 Readability is less since numbered placeholders like $1,$2 are used
How
Velocity Template Mediator solve them?

Velocity template mediator uses well known Apache Velocity as the template
engine. You can do whatever you can do with Velocity in side this. Iterate
through collections, check conditions etc. In addition to that since we are
using place holders like $name,$age for the variables ,so it improves the
readability as well.

On the other hand, there was no such a thing in Synapse to create a
property out of a template.

For Example: When you call a soap back end, suppose you have to send a user
name token in SOAP Header. Suppose there are several back end calls you
need to make and in every call you need to pass the user name token.

With the payload factory , you will have to create that part every time.
Instead if you can create a property one time using a template and save it
in the message context , you can reuse it without generating again and
again.

With the Velocity Template Mediator , it supports body,property,soap
header,envelope as the targets. You can put the generated output to anyof
these. And it supports both xml and json formats

Sample Syntax


   
  
 $name
 $age
  
   
   
  
  
   
   



Thanks,
Asanka D

-- 


*Asanka DissanayakeSoftware Engineer*
*WSO2 Inc. - lean . enterprise . middleware |  wso2.com *

*email: asan...@wso2.com ,   blog:
cyberwaadiya.blogspot.com
, asankastechtalks.wordpress.com
  mobile: +94 71 8373821*
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Fwd: OATH Authenticators for IS

[Malaka Silva]

Hi Rajjaz
​,

We need to create a common module to improve re usability of the code.​

But this common repo should not be just for
​​
TOTP and HOTP
​, but rather for the entire IS extensions.​ In this common repo
​
TOTP and HOTP
​ should be a component.

On Tue, Mar 15, 2016 at 10:34 PM, Rajjaz Mohammed  wrote:

> Hi All,
> Kind reminder on this topic.
>
> @Prabath/Johan
> shall we create a common module for TOTP and HOTP?
> Algorithm based common module will reduce the codes and we can use for
> multiple vendors, currently SMSOTP developed based on Nexmo API[1] but
> there are multiple options available for send SMS. so if we create common
> module then we can easily add  for other vendor also and we can add option
> to select the algorithm.
>
>
> [1] https://dashboard.nexmo.com 
>
>
> On Fri, Mar 11, 2016 at 11:46 AM, Kathees Rajendram 
> wrote:
>
>> Hi,
>>
>> We can have the authenticators either algorithm based or medium based as
>> we discussed in the meeting. Google authenticator also supports TOTP and
>> HOTP [1].
>>
>> Algorithm based authenticators (TOTP and HOTP)
>>
>> TOTP
>> - Email
>> - SMS
>> - Google
>> HOTP
>> - Email
>> - SMS
>> - Google
>>
>> Based on the algorithm, we will have the authenticator TOTP and HOTP
>> authenticators. Both authenticators will have the mediums Email, SMS and
>> google app to send the token.
>>
>> Medium based Authenticators (Email OTP, SMS OTP and Google)
>>
>> Email
>> - TOTP
>> - HOTP
>> SMS
>> - TOTP
>> - HOTP
>> Google
>> - TOTP
>> - HOTP
>>
>> Based on the medium, we will have the authenticators Email OTP, SMS OTP
>> and Google. Three authenticators will have the options TOTP and HOTP
>> algorithm to generate the token.
>>
>> [1] - https://github.com/google/google-authenticator
>>
>> @Prabath
>> WDYT?
>>
>> Thanks,
>> Kathee
>>
>> On Fri, Mar 11, 2016 at 9:32 AM, Keerthika Mahendralingam <
>> keerth...@wso2.com> wrote:
>>
>>> Yes, IMO we can't rename TOTP as Google authenticator. Because TOTP will
>>> provide the facility to use the Google authenticator to get the token and
>>> validate the user. But it can be also used to authenticate the user like
>>> SMSOTP and emailOTP.
>>>
>>>
>>> Thanks,
>>>
>>> On Thu, Mar 10, 2016 at 7:34 PM, Prabath Siriwardana 
>>> wrote:
>>>


 On Tue, Mar 8, 2016 at 10:24 PM, Kathees Rajendram 
 wrote:

> +1 for common module for TOTP and HOTP algorithms.
>
> IMO can we rename TOTP authenticator to Google Authenticator.
>

 Isn't that misleading...?


> SMS OTP, Email OTP and Google Authenticator can have the options TOTP
> and  HOTP.
>
> Thanks,
> Kahees
>
> On Tue, Mar 8, 2016 at 7:51 PM, Malaka Silva  wrote:
>
>> +1 for separating common modules.
>>
>> However IMO these needs to go as two different authenticators since
>> it provides two distinct methods to authenticate.
>>
>> +architecture
>>
>> -- Forwarded message --
>> From: Rajj
>> ​common mod​
>> az Mohammed 
>> Date: Tue, Mar 8, 2016 at 6:56 PM
>> Subject: OATH Authenticators for IS
>> To: Malaka Silva , Rohan Perera 
>> Cc: Kathees Rajendram , Elilmatha Sivanesan <
>> elilma...@wso2.com>, Keerthika Mahendralingam ,
>> Shakila Sivagnanarajah 
>>
>>
>> Hi All,
>> We already have SMS OTP , Email OTP and TOTP all are using hash-based
>> message authentication code
>> 
>> (HMAC) algorithm. OATH provides 2 types of authentication methods[1]
>> TOTP[2] and HOTP[3].
>>
>> OTP relies on two basic things, a shared secret and a moving factor.
>> for TOTP moving factor will be a timestamp[2] and for HOTP that moving
>> factor will be a counter[3].
>> But according to the list[4] given by IS Team we are developing
>> separate authenticators. can't we create common modules for these
>> OATH[1] authenticators?
>>
>> WDYT?
>>
>>
>> [1]
>> https://openauthentication.org/specifications-technical-resources/
>> [2]
>> https://en.wikipedia.org/wiki/Time-based_One-time_Password_Algorithm
>> [3]
>> https://en.wikipedia.org/wiki/HMAC-based_One-time_Password_Algorithm
>> [4]
>> https://docs.google.com/spreadsheets/d/1WhAc2yXg9SJ_fAFQYKwetbmP09m5TWEvRGLp04a0dO8/edit#gid=2089406928
>>
>>
>>
>> --
>> Thank you
>> Best Regards
>>
>> *Rajjaz HM*
>> Associate Software Engineer
>> Platform Extension Team
>> WSO2 Inc. 
>> lean | enterprise | middleware
>> Mobile | +94752833834|+94777226874
>> Email   | raj...@wso2.com
>> LinkedIn | Blogger | WSO2 Profile
>> 
>>
>>
>>
>> --
>>
>> Best Regards,
>>
>> Malaka Silva
>> Senior Tech Lead
>> M: +94 777 219 791
>> T

Re: [Architecture] [APIM Analytics][Docs] Documentation space for APIM Analytics

[Jackie Wheeler]

If I understand the scope correctly, tooling should just be described as
part of the instructions for performing a particular task. I don't think it
will need its own section. Analytics, on the other hand, should be
described in topics like "Tracking usage" or other use cases that use
analytics.

On Mon, Mar 14, 2016 at 3:03 AM, Nirdesha Munasinghe 
wrote:

> I think it is better to have this as part of a single product doc. The
> navigation experience will be easier for the users and analytics and
> tooling are anyway parts of the product.
>
> On Mon, Mar 14, 2016 at 2:19 PM, Rukshani Weerasinha 
> wrote:
>
>> Hi Nirmal,
>>
>> The Tooling information is not released yet, and these documents are
>> currently hidden.
>>
>> As agreed offline, I will pass the information with regard to the nature
>> of these Analytics implementation in APIM and other products to the Tech
>> Content team and discuss a general approach to include Analytics related
>> information in each product space.
>>
>> Best Regards,
>> Rukshani.
>>
>> On Mon, Mar 14, 2016 at 12:28 PM, Nirmal Fernando 
>> wrote:
>>
>>> Hi Rukshani,
>>>
>>> Where is it in the hierarchy?
>>>
>>> On Mon, Mar 14, 2016 at 12:25 PM, Rukshani Weerasinha >> > wrote:
>>>
 Hi Nirmal,

 At the moment, Tooling is already documented for some products as a
 separate section within the product documentation space (e.g. [1]). Can we
 follow the same approach for Analytics?

 [1]
 https://docs.wso2.com/display/ESB490/Installing+the+ESB+Tooling+Plug-In

 Best Regards,
 Rukshani.

 On Mon, Mar 14, 2016 at 12:12 PM, Nirmal Fernando 
 wrote:

> Hi All,
>
> Shall we decide where we gonna host APIM analytics related docs? Would
> it make sense to create a new doc space hierarchy with the introduction of
> product, tooling and analytics?
>
> APIM-X.X
> |_ Product
> |_About X
> |_Getting Started
> 
> |_Tooling
> |_ ..
> |_Analytics
> |_ ..
>
>
> --
>
> Thanks & regards,
> Nirmal
>
> Team Lead - WSO2 Machine Learner
> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>
>
>


 --
 Rukshani Weerasinha

 WSO2 Inc.
 Web:http://wso2.com
 Mobile: 0777 683 738


>>>
>>>
>>> --
>>>
>>> Thanks & regards,
>>> Nirmal
>>>
>>> Team Lead - WSO2 Machine Learner
>>> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
>>> Mobile: +94715779733
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>>
>>>
>>
>>
>> --
>> Rukshani Weerasinha
>>
>> WSO2 Inc.
>> Web:http://wso2.com
>> Mobile: 0777 683 738
>>
>>
>
>
> --
>
> Thanks,
>
> Nirdesha Munasinghe,
> WSO2 Inc.
> Web:http://wso2.com
>
> Mobile: +94 776321920
>



-- 
*Jackie Wheeler*
VP, Technical Content
WSO2, Inc.
Mobile: +1 510 725-2876
http://wso2.com/
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Fwd: OATH Authenticators for IS

[Rajjaz Mohammed]

Hi All,
Kind reminder on this topic.

@Prabath/Johan
shall we create a common module for TOTP and HOTP?
Algorithm based common module will reduce the codes and we can use for
multiple vendors, currently SMSOTP developed based on Nexmo API[1] but
there are multiple options available for send SMS. so if we create common
module then we can easily add  for other vendor also and we can add option
to select the algorithm.


[1] https://dashboard.nexmo.com 


On Fri, Mar 11, 2016 at 11:46 AM, Kathees Rajendram 
wrote:

> Hi,
>
> We can have the authenticators either algorithm based or medium based as
> we discussed in the meeting. Google authenticator also supports TOTP and
> HOTP [1].
>
> Algorithm based authenticators (TOTP and HOTP)
>
> TOTP
> - Email
> - SMS
> - Google
> HOTP
> - Email
> - SMS
> - Google
>
> Based on the algorithm, we will have the authenticator TOTP and HOTP
> authenticators. Both authenticators will have the mediums Email, SMS and
> google app to send the token.
>
> Medium based Authenticators (Email OTP, SMS OTP and Google)
>
> Email
> - TOTP
> - HOTP
> SMS
> - TOTP
> - HOTP
> Google
> - TOTP
> - HOTP
>
> Based on the medium, we will have the authenticators Email OTP, SMS OTP
> and Google. Three authenticators will have the options TOTP and HOTP
> algorithm to generate the token.
>
> [1] - https://github.com/google/google-authenticator
>
> @Prabath
> WDYT?
>
> Thanks,
> Kathee
>
> On Fri, Mar 11, 2016 at 9:32 AM, Keerthika Mahendralingam <
> keerth...@wso2.com> wrote:
>
>> Yes, IMO we can't rename TOTP as Google authenticator. Because TOTP will
>> provide the facility to use the Google authenticator to get the token and
>> validate the user. But it can be also used to authenticate the user like
>> SMSOTP and emailOTP.
>>
>>
>> Thanks,
>>
>> On Thu, Mar 10, 2016 at 7:34 PM, Prabath Siriwardana 
>> wrote:
>>
>>>
>>>
>>> On Tue, Mar 8, 2016 at 10:24 PM, Kathees Rajendram 
>>> wrote:
>>>
 +1 for common module for TOTP and HOTP algorithms.

 IMO can we rename TOTP authenticator to Google Authenticator.

>>>
>>> Isn't that misleading...?
>>>
>>>
 SMS OTP, Email OTP and Google Authenticator can have the options TOTP
 and  HOTP.

 Thanks,
 Kahees

 On Tue, Mar 8, 2016 at 7:51 PM, Malaka Silva  wrote:

> +1 for separating common modules.
>
> However IMO these needs to go as two different authenticators since
> it provides two distinct methods to authenticate.
>
> +architecture
>
> -- Forwarded message --
> From: Rajj
> ​common mod​
> az Mohammed 
> Date: Tue, Mar 8, 2016 at 6:56 PM
> Subject: OATH Authenticators for IS
> To: Malaka Silva , Rohan Perera 
> Cc: Kathees Rajendram , Elilmatha Sivanesan <
> elilma...@wso2.com>, Keerthika Mahendralingam ,
> Shakila Sivagnanarajah 
>
>
> Hi All,
> We already have SMS OTP , Email OTP and TOTP all are using hash-based
> message authentication code
> 
> (HMAC) algorithm. OATH provides 2 types of authentication methods[1]
> TOTP[2] and HOTP[3].
>
> OTP relies on two basic things, a shared secret and a moving factor.
> for TOTP moving factor will be a timestamp[2] and for HOTP that moving
> factor will be a counter[3].
> But according to the list[4] given by IS Team we are developing
> separate authenticators. can't we create common modules for these
> OATH[1] authenticators?
>
> WDYT?
>
>
> [1] https://openauthentication.org/specifications-technical-resources/
> [2]
> https://en.wikipedia.org/wiki/Time-based_One-time_Password_Algorithm
> [3]
> https://en.wikipedia.org/wiki/HMAC-based_One-time_Password_Algorithm
> [4]
> https://docs.google.com/spreadsheets/d/1WhAc2yXg9SJ_fAFQYKwetbmP09m5TWEvRGLp04a0dO8/edit#gid=2089406928
>
>
>
> --
> Thank you
> Best Regards
>
> *Rajjaz HM*
> Associate Software Engineer
> Platform Extension Team
> WSO2 Inc. 
> lean | enterprise | middleware
> Mobile | +94752833834|+94777226874
> Email   | raj...@wso2.com
> LinkedIn | Blogger | WSO2 Profile
> 
>
>
>
> --
>
> Best Regards,
>
> Malaka Silva
> Senior Tech Lead
> M: +94 777 219 791
> Tel : 94 11 214 5345
> Fax :94 11 2145300
> Skype : malaka.sampath.silva
> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
> Blog : http://mrmalakasilva.blogspot.com/
>
> WSO2, Inc.
> lean . enterprise . middleware
> http://www.wso2.com/
> http://www.wso2.com/about/team/malaka-silva/
> 
> https://store.wso2.com/store/
>
> Save a tree -Conserve nature & Save the world for your future. Print
>>>

Re: [Architecture] [Dev] [BPS] Rendering information of the current task of a BPMN process instance

[Waruna Jayaweera]

Hi,
Yes. It is better if we can expose rendering information through rest api.
These data will be helpful when integrating bps runtime with process center
too.

Thanks,
Waruna

On Tue, Mar 15, 2016 at 5:30 PM, Vinod Kavinda  wrote:

> Hi,
> Are we exposing these information via REST api? It's better to expose
> everything in REST first. Then we can build the UI as relevant, later.
>
> Regards,
> Vinod
> On Mar 15, 2016 1:14 PM, "Nandika Jayawardana"  wrote:
>
>> Lets implement this for bpmn explorer as well.  However, both would
>> change when we move to C5.
>>
>> Regards
>> Nandika
>>
>> On Tue, Mar 15, 2016 at 12:31 PM, Vinod Kavinda  wrote:
>>
>>> [Adding Architecture@]
>>> Hi DiliniM,
>>> As we are planning on dropping the admin UIs with C5, is there a use of
>>> integrating this with admin console UI? Shall we do this in our BPMN
>>> explorer UI?
>>>
>>> Regards,
>>> Vinod
>>>
>>> On Tue, Mar 15, 2016 at 12:24 PM, Dilini Mihindra 
>>> wrote:
>>>
 Hi all,

 I am working on rendering the information of the current task of an
 active BPMN process instance. As supported by Activiti, the process diagram
 of an active process instance is given as following:


*Figrue 1 - The process instance diagram
 of *
 * an active BPMN process instance*

 The current task of the process instance is highlighted by a red
 boarder in the given process diagram. I am working on rendering the
 information of this current task in the instance_list_view.jsp page so that
 the users can get a clear idea on the current task.

 The following properties are displayed regarding each task:​


- Task Key
- Task Name
- Assignee
- Description
- Category
- Due Date
- Form Key
- Owner
- Priority
- Skip
- Candidate Group Ids
- Candidate User Ids

 Thank you.


 Dilini Mihindra Mampitiya Arachchi
 Intern - Software Engineer
 Mobile: +94 710 420 550
 Email: dili...@wso2.com

 ___
 Dev mailing list
 d...@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> Vinod Kavinda
>>> Software Engineer
>>> *WSO2 Inc. - lean . enterprise . middleware .*
>>> Mobile : +94 (0) 712 415544
>>> Blog : http://soatechflicks.blogspot.com/
>>>
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Nandika Jayawardana
>> WSO2 Inc ; http://wso2.com
>> lean.enterprise.middleware
>>
>> ___
>> Dev mailing list
>> d...@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
> ___
> Dev mailing list
> d...@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Regards,

Waruna Lakshitha Jayaweera
Software Engineer
WSO2 Inc; http://wso2.com
phone: +94713255198
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [Dev] [BPS] Rendering information of the current task of a BPMN process instance

[Vinod Kavinda]

Hi,
Are we exposing these information via REST api? It's better to expose
everything in REST first. Then we can build the UI as relevant, later.

Regards,
Vinod
On Mar 15, 2016 1:14 PM, "Nandika Jayawardana"  wrote:

> Lets implement this for bpmn explorer as well.  However, both would change
> when we move to C5.
>
> Regards
> Nandika
>
> On Tue, Mar 15, 2016 at 12:31 PM, Vinod Kavinda  wrote:
>
>> [Adding Architecture@]
>> Hi DiliniM,
>> As we are planning on dropping the admin UIs with C5, is there a use of
>> integrating this with admin console UI? Shall we do this in our BPMN
>> explorer UI?
>>
>> Regards,
>> Vinod
>>
>> On Tue, Mar 15, 2016 at 12:24 PM, Dilini Mihindra 
>> wrote:
>>
>>> Hi all,
>>>
>>> I am working on rendering the information of the current task of an
>>> active BPMN process instance. As supported by Activiti, the process diagram
>>> of an active process instance is given as following:
>>>
>>>
>>>*Figrue 1 - The process instance diagram of *
>>> * an active BPMN process instance*
>>>
>>> The current task of the process instance is highlighted by a red
>>> boarder in the given process diagram. I am working on rendering the
>>> information of this current task in the instance_list_view.jsp page so that
>>> the users can get a clear idea on the current task.
>>>
>>> The following properties are displayed regarding each task:​
>>>
>>>
>>>- Task Key
>>>- Task Name
>>>- Assignee
>>>- Description
>>>- Category
>>>- Due Date
>>>- Form Key
>>>- Owner
>>>- Priority
>>>- Skip
>>>- Candidate Group Ids
>>>- Candidate User Ids
>>>
>>> Thank you.
>>>
>>>
>>> Dilini Mihindra Mampitiya Arachchi
>>> Intern - Software Engineer
>>> Mobile: +94 710 420 550
>>> Email: dili...@wso2.com
>>>
>>> ___
>>> Dev mailing list
>>> d...@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Vinod Kavinda
>> Software Engineer
>> *WSO2 Inc. - lean . enterprise . middleware .*
>> Mobile : +94 (0) 712 415544
>> Blog : http://soatechflicks.blogspot.com/
>>
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Nandika Jayawardana
> WSO2 Inc ; http://wso2.com
> lean.enterprise.middleware
>
> ___
> Dev mailing list
> d...@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] The new disruptor based Netty transport is not working well for MSF4J

[Afkham Azeez]

Our initial assumptions were wrong and we were able to narrow down this
issue to a wrong configuration parameter name. Due to that, we were always
running with a single disruptor event handler thread instead of a thread
pool. Now we are seeing better perf values with disruptor as opposed to the
Netty executor thread pool, with some tuning of disruptor configuration
parameters.

Azeez

On Mon, Mar 14, 2016 at 1:55 PM, Sagara Gunathunga  wrote:

>
>
> On Mon, Mar 14, 2016 at 1:53 PM, Srinath Perera  wrote:
>
>> I talked to Ranawaka and Isuru in detail.
>>
>> Disrupter helps a lot when tasks are CPU bound. In such cases, in can
>> works with very few threads and reduce the overhead of communication
>> between threads.
>>
>> However, when threads  block for I/O this advantage is reduced a lot. In
>> those cases, we need to have multiple disrupter workers ( batch
>> processors). We are doing that.
>>
>> However, doing  test with 500ms sleep is not fair IMO. Sleep often waits
>> more than the given value. With 200 threads, it can only do 400TPS with
>> 500ms sleep. I think we should compare against a DB backend.
>>
>> Shell we test disrupter and java work pool model against a DB backend?
>>
>
> +1 I also think we should use more realistic backend such as DB.
>
> Thanks !
>
>>
>> --Srinath
>>
>>
>>
>> On Mon, Mar 14, 2016 at 10:26 AM, Kasun Indrasiri  wrote:
>>
>>> Hi,
>>>
>>> Let me try to clarify few things here.
>>>
>>> - Initially we implemented Netty HTTP transport with conventional thread
>>> model (workers) and at the same time we also tested the Disruptor based
>>> model for the same Gateway/Header based routing use case. Disruptor based
>>> approach gave us around  ~20k of perf gain on perf testing environments.
>>> - MSF4J 1.0 GA didn't use GW's HTTP transport code as it is. It reused
>>> basic transport runtime but with a custom Netty handler that is used to
>>> dispatch the requests. So, MSFJ 1.0 GA, didn't have disruptor and
>>> performance/latency of MSF4J 1.0 GA has nothing to do with Disruprtor.
>>>
>>> - Now we are trying to migrate MSF4J into the exact same transport code
>>> as it with the GW core (carbon-transport's HTTP transport). And that's
>>> where we came across the above perf issue.
>>> - So, unlike GW scenario, for MSF4J and even for any other content-aware
>>> ESB scenario, the above approach is not the optimum it seems. Hence we are
>>> now looking into how such scenarios are handled with Disruptor.
>>>
>>> In that context, if we look at the original LMAX use case[1] is also
>>> quite similar to what we are trying with content aware scenarios. In their
>>> use case they had heavy CPU intensive components(such as Business Logic
>>> component) as well as IO bound components (such as Un-marshaller,
>>> Replicator). And they get better performance for the same use case with
>>> Disruptor over a conventional worker-thread model.
>>>
>>>
>>> [image: Inline image 1]
>>>
>>> So, we need to have a close look into that how we can implement a
>>> dependent consumer scenario[2] (one consumer is IO bound and the other is
>>> CPU bound) and check whether we can get more perf gain compared to the
>>> conventional worker thread model.
>>>
>>> Ranawaka is current looking into this.
>>>
>>> [1] http://martinfowler.com/articles/lmax.html
>>> [2]
>>> http://mechanitis.blogspot.com/2011/07/dissecting-disruptor-wiring-up.html
>>>
>>> On Sun, Mar 13, 2016 at 8:11 AM, Isuru Ranawaka  wrote:
>>>
 Hi Azeez,

 In GW Disruptor threads are not used for make calls for backends.
 Backends are called by Netty worker pool and those calls are non blocking
 calls. So if backend responds after a delay it won't be a problem.


 In MSF4J  if it includes IO operations or delayed operations then it
 causes problems because processing happens through Disruptor threads and
 by occupying all the limited disruptor threads. But this should be solved
 by operating Disruptor Event Handlers through workerpool and now we are
 looking in to that why it does not provide expected results.

 thanks
 IsuruR

 On Sat, Mar 12, 2016 at 6:46 PM, Afkham Azeez  wrote:

> Kasun et al,
> In MSF4J, the threads from the disruptor pool itself are used for
> processing in the MSF4J operation. In the case of the GW passthrough & HBR
> scenarios, are those disruptor threads used to make the calls to the 
> actual
> backends? Is that a blocking call? What if the backend service is changed
> so that it responds after a delay rather than instantaneously?
>
> On Sat, Mar 12, 2016 at 6:21 PM, Afkham Azeez  wrote:
>
>>
>>
>> On Sat, Mar 12, 2016 at 1:40 PM, Sanjiva Weerawarana <
>> sanj...@wso2.com> wrote:
>>
>>> On Thu, Mar 10, 2016 at 6:20 PM, Sagara Gunathunga 
>>> wrote:
>>>
 On Thu, Mar 10, 2016 at 10:26 AM, Afkham Azeez 
 wrote:

> No from day 1, we have decided that GW & MSF4J

Re: [Architecture] [BPS] User management integration of BPMN

[Himasha Guruge]

Thanks for the update Jayanga.

On Tue, Mar 15, 2016 at 12:21 PM, Jayanga Kaushalya 
wrote:

> Hi Himasha,
>
> We will be able to finish a JDBC based implementation for Platform with
> Authentication, Authorization, basic CRUD operations and claim management
> in around 3 weeks. We'll update you when we are done.
>
> Thanks!
>
> *Jayanga Kaushalya*
> Software Engineer
> Mobile: +94777860160
> WSO2 Inc. | http://wso2.com
> lean.enterprise.middleware
>
> On Mon, Mar 14, 2016 at 3:49 PM, Himasha Guruge  wrote:
>
>> Hi Sameera/ IS team,
>>
>> In order to integrate user management to C5 based BPMN component, we have
>> a dependency on JDBCIdentityStoreConnector [1]. Is it possible to know
>> when the completed user core will be available in Kernel?
>>
>> [1]
>> https://github.com/wso2/carbon-security/blob/hamming-release/component/src/main/java/org/wso2/carbon/security/usercore/connector/jdbc/JDBCIdentityStoreConnector.java
>>
>> Thanks,
>> Himasha
>>
>> On Fri, Mar 11, 2016 at 11:22 AM, Himasha Guruge 
>> wrote:
>>
>>>
>>> Hi All,
>>>
>>> As a part of C5 based bpmn development, i'm in the process of
>>> integrating user management with Camunda based bpmnEngineBuilder. With
>>> regards to the custom UserIdentityManager and GroupIdentityManager,
>>> DbIdentityServiceProvider [1] [2] will be extended which is the default
>>> identity service that provides CRUD functionalities related to users and
>>> groups.
>>>
>>>  In order to override necessary methods of DbIdentityServiceProvider,
>>> IdentityStoreConnector interface [3]  will be implemented which is
>>> available under  carbon-security component of the Kernel. This interface
>>> includes  necessary User  and group related methods.
>>>
>>> [1]
>>> https://docs.camunda.org/manual/7.4/user-guide/process-engine/identity-service/
>>> [2]
>>> https://docs.camunda.org/javadoc/camunda-bpm-platform/7.4/org/camunda/bpm/engine/impl/identity/db/DbIdentityServiceProvider.html
>>> [3]
>>> https://github.com/wso2/carbon-security/blob/hamming-release/component/src/main/java/org/wso2/carbon/security/usercore/connector/IdentityStoreConnector.java
>>>
>>>
>>> Regards,
>>>
>>> Himasha Guruge
>>> *Software Engineer*
>>> WS*O2* *Inc.*
>>> Mobile: +94 777459299
>>> himas...@wso2.com
>>>
>>
>>
>>
>> --
>> Himasha Guruge
>> *Software Engineer*
>> WS*O2* *Inc.*
>> Mobile: +94 777459299
>> himas...@wso2.com
>>
>
>


-- 
Himasha Guruge
*Software Engineer*
WS*O2* *Inc.*
Mobile: +94 777459299
himas...@wso2.com
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [Dev] [BPS] Rendering information of the current task of a BPMN process instance

[Nandika Jayawardana]

Lets implement this for bpmn explorer as well.  However, both would change
when we move to C5.

Regards
Nandika

On Tue, Mar 15, 2016 at 12:31 PM, Vinod Kavinda  wrote:

> [Adding Architecture@]
> Hi DiliniM,
> As we are planning on dropping the admin UIs with C5, is there a use of
> integrating this with admin console UI? Shall we do this in our BPMN
> explorer UI?
>
> Regards,
> Vinod
>
> On Tue, Mar 15, 2016 at 12:24 PM, Dilini Mihindra 
> wrote:
>
>> Hi all,
>>
>> I am working on rendering the information of the current task of an
>> active BPMN process instance. As supported by Activiti, the process diagram
>> of an active process instance is given as following:
>>
>>
>>*Figrue 1 - The process instance diagram of *
>> * an active BPMN process instance*
>>
>> The current task of the process instance is highlighted by a red boarder
>> in the given process diagram. I am working on rendering the information of
>> this current task in the instance_list_view.jsp page so that the users can
>> get a clear idea on the current task.
>>
>> The following properties are displayed regarding each task:​
>>
>>
>>- Task Key
>>- Task Name
>>- Assignee
>>- Description
>>- Category
>>- Due Date
>>- Form Key
>>- Owner
>>- Priority
>>- Skip
>>- Candidate Group Ids
>>- Candidate User Ids
>>
>> Thank you.
>>
>>
>> Dilini Mihindra Mampitiya Arachchi
>> Intern - Software Engineer
>> Mobile: +94 710 420 550
>> Email: dili...@wso2.com
>>
>> ___
>> Dev mailing list
>> d...@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Vinod Kavinda
> Software Engineer
> *WSO2 Inc. - lean . enterprise . middleware .*
> Mobile : +94 (0) 712 415544
> Blog : http://soatechflicks.blogspot.com/
>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Nandika Jayawardana
WSO2 Inc ; http://wso2.com
lean.enterprise.middleware
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [Dev] [BPS] Rendering information of the current task of a BPMN process instance

[Vinod Kavinda]

[Adding Architecture@]
Hi DiliniM,
As we are planning on dropping the admin UIs with C5, is there a use of
integrating this with admin console UI? Shall we do this in our BPMN
explorer UI?

Regards,
Vinod

On Tue, Mar 15, 2016 at 12:24 PM, Dilini Mihindra  wrote:

> Hi all,
>
> I am working on rendering the information of the current task of an active
> BPMN process instance. As supported by Activiti, the process diagram of an
> active process instance is given as following:
>
>
>*Figrue 1 - The process instance diagram of *
> * an active BPMN process instance*
>
> The current task of the process instance is highlighted by a red boarder
> in the given process diagram. I am working on rendering the information of
> this current task in the instance_list_view.jsp page so that the users can
> get a clear idea on the current task.
>
> The following properties are displayed regarding each task:​
>
>
>- Task Key
>- Task Name
>- Assignee
>- Description
>- Category
>- Due Date
>- Form Key
>- Owner
>- Priority
>- Skip
>- Candidate Group Ids
>- Candidate User Ids
>
> Thank you.
>
>
> Dilini Mihindra Mampitiya Arachchi
> Intern - Software Engineer
> Mobile: +94 710 420 550
> Email: dili...@wso2.com
>
> ___
> Dev mailing list
> d...@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Vinod Kavinda
Software Engineer
*WSO2 Inc. - lean . enterprise . middleware .*
Mobile : +94 (0) 712 415544
Blog : http://soatechflicks.blogspot.com/
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture