Re: [Architecture] [Dev] [VOTE] Release WSO2 IoT Server 3.2.0 RC1

[Kamidu Punchihewa]

I have tested and verified the following on a MacBookPro without any load
balancers using a self singed SSL certificate :

Created a user and role
Enrolled an Android device
Create and publish an Android policy
Applied the following operations to the enrolled device,

   - Send Notification
   - Location
   - Ring
   - Clear Passcode
   - Enterprise Wipe
   - Device Lock
   - Wipe Data

Check the Geo Dashboard and the UI for information and verify the received
information.
Test the re-enrollment process of the same device with another user.
Test and verify the Group Management.
Test and verify the Role and Permission Management.
Test and verify the Certificate Management.

No issues found.
[x] Stable - go ahead and release

Regards,
Inosh


On Mon, Feb 5, 2018 at 12:49 PM, Inosh Perera  wrote:

> Tested and verified the following:
>
> Created a user and role
> Enrolled an iOS device
>
> Applied the following operations and policies,
> Send Notification
> Location
> Ring
> Clear Passcode
> Enterprise Wipe
> Device Lock
> Wipe Data
> Verify Location information in UI againt the device location
> Verify device information in UI againt the device
> Verify app list
> Passcode Policy
> Restrictions
> WiFi Settings
> Email Settings
> AirPlay Settings
> LDAP Setting
> Calendar
> Calendar Subscritption
> Cellular Network Settings
> VPN
> Manage Domains
>
> No issues found.
> [x] Stable - go ahead and release
>
> Regards,
> Inosh
>
>
>
> On Tue, Jan 30, 2018 at 11:52 AM, Rasika Perera  wrote:
>
>> Hi Devs,
>>
>> We are pleased to announce the release candidate of WSO2 IoT Server 3.2.0
>> .
>>
>> This is the first release candidate (RC) of the WSO2 IoT Server 3.2.0
>> release.
>>
>> This release carries 275 issue fixes [1-12] over the last GA (3.1.0)
>> release.
>>
>> Reported Issues:
>>
>>- https://github.com/wso2/product-iots/issues
>>
>> Source and distribution packages:
>>
>>- https://github.com/wso2/product-iots/releases/tag/v3.2.0-RC1
>>
>> Tag to be voted upon:
>>
>>- https://github.com/wso2/product-iots/releases/tag/v3.2.0-RC1
>>
>> Please download, test, and vote. The README file under the distribution
>> contains guide and instructions on how to try it out locally.
>>
>> [+] Stable - Go ahead and release
>> [-] Broken - Do not release (explain why)
>>
>> This vote will be open for 72 hours or as needed.
>>
>> [1] https://github.com/wso2/product-iots/milestone/3?closed=1
>> [2] https://github.com/wso2/product-iots/milestone/4?closed=1
>> [3] https://github.com/wso2/product-iots/milestone/5?closed=1
>> [4] https://github.com/wso2/product-iots/milestone/6?closed=1
>> [5] https://github.com/wso2/product-iots/milestone/7?closed=1
>> [6] https://github.com/wso2/product-iots/milestone/11?closed=1
>> [7] https://github.com/wso2/product-iots/milestone/12?closed=1
>> [8] https://github.com/wso2/product-iots/milestone/13?closed=1
>> [9] https://github.com/wso2/product-iots/milestone/14?closed=1
>> [10] https://github.com/wso2/product-iots/milestone/18?closed=1
>> [11] https://github.com/wso2/product-iots/milestone/19?closed=1
>> [12] https://github.com/wso2/product-iots/milestone/20?closed=1
>>
>> Regards,
>> The WSO2 IoT Team.
>>
>> --
>> With Regards,
>>
>> *Rasika Perera*
>> Senior Software Engineer
>> LinkedIn: http://lk.linkedin.com/in/rasika90
>>
>> 
>>
>> WSO2 Inc. www.wso2.com
>> lean.enterprise.middleware
>>
>
>
>
> --
> Inosh Perera
> Senior Software Engineer, WSO2 Inc.
> Tel: 077813 7285, 0785293686
>
> ___
> Dev mailing list
> d...@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Kamidu Sachith Punchihewa
*Senior 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.
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Can we ship Identity Management / Identity Governance features with APIM by default.

[Nuwan Dias]

On Mon, Feb 5, 2018 at 12:36 PM, Asela Pathberiya  wrote:

>
>
> On Mon, Feb 5, 2018 at 12:10 PM, Nuwan Dias  wrote:
>
>> As mentioned on the subject itself, these are Identity Management and
>> Identity Governance features. They don't closely tie in with API
>> Management. Therefore I think its fine to recommend IS for those kind of
>> use cases.
>>
>> Installing these features to APIM at this point in time is also a problem
>> due to its roadmap with 3.0. If we install these features into APIM users
>> will see these as first class features of our APIM offering, they won't see
>> this as something coming from IS.
>>
>
> APIM store is public facing for end users.  It already supports for user
> registration which is also identity management feature.  It is a question,
> why can't it support  features such as  password recovery/policies/email
> activation by default.
>

Its not that it can't. Its a question of where do we draw the line between
IS and APIM. My opinion is that the current user registration (with
workflow support) and password reset options are just enough for the OOTB
product. You can have many more scenarios than listed above. Such as Login
with Facebook, Multifactor Authentication, etc and the list could go on. I
think its fine to ask users to integrate with IS for advanced scenarios.

>
> If product supports for public user registration, it must support for all
> other identity management features as well.
>
> Are we removing the user registration from APIM 3.0 ?
>

No, that would be there. But we don't have plans to support anything else.
Since there's no C5 based IS yet, we are writing all the user management
capabilities from scratch to even get the basic functionality. The need to
support more and more scenarios would create a lot more work than already
planned. Risking its deadlines.

>
> Thanks,
> Asela.
>
>
>> Which means that users would expect the same set of features on 3.0 as
>> well. Therefore I would be -1 to installing these features on APIM.
>>
>> On Mon, Feb 5, 2018 at 9:49 AM, Asela Pathberiya  wrote:
>>
>>> Hi All,
>>>
>>> There are several customers/users who are looking for $subject with
>>> APIM.  Specially following features
>>>
>>> 1. Account lock/disable
>>> 2. Password/Account recovery
>>> 3. Password policies
>>>
>>> We are usually not recommending the feature installation.  Therefore,
>>> shall we ship these features by default with APIM.
>>>
>>> However, we can suggests to use WSO2IS as KM,  but we need to consider on
>>>
>>> 1.  Cost on running WSO2IS (infra cost)
>>> 2.  All in one deployment
>>> 3.  First impression on the IAM feature list of APIM.
>>>
>>> WDYT ?
>>>
>>> Thanks,
>>> Asela.
>>>
>>> --
>>> Thanks & Regards,
>>> Asela
>>>
>>> ATL
>>> Mobile : +94 777 625 933 <+94%2077%20762%205933>
>>>  +358 449 228 979
>>>
>>> http://soasecurity.org/
>>> http://xacmlinfo.org/
>>>
>>
>>
>>
>> --
>> Nuwan Dias
>>
>> Software Architect - WSO2, Inc. http://wso2.com
>> email : nuw...@wso2.com
>> Phone : +94 777 775 729 <+94%2077%20777%205729>
>>
>
>
>
> --
> Thanks & Regards,
> Asela
>
> ATL
> Mobile : +94 777 625 933 <+94%2077%20762%205933>
>  +358 449 228 979
>
> http://soasecurity.org/
> http://xacmlinfo.org/
>



-- 
Nuwan Dias

Software Architect - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [Dev] [VOTE] Release WSO2 IoT Server 3.2.0 RC1

[Inosh Perera]

Tested and verified the following:

Created a user and role
Enrolled an iOS device

Applied the following operations and policies,
Send Notification
Location
Ring
Clear Passcode
Enterprise Wipe
Device Lock
Wipe Data
Verify Location information in UI againt the device location
Verify device information in UI againt the device
Verify app list
Passcode Policy
Restrictions
WiFi Settings
Email Settings
AirPlay Settings
LDAP Setting
Calendar
Calendar Subscritption
Cellular Network Settings
VPN
Manage Domains

No issues found.
[x] Stable - go ahead and release

Regards,
Inosh



On Tue, Jan 30, 2018 at 11:52 AM, Rasika Perera  wrote:

> Hi Devs,
>
> We are pleased to announce the release candidate of WSO2 IoT Server 3.2.0.
>
> This is the first release candidate (RC) of the WSO2 IoT Server 3.2.0
> release.
>
> This release carries 275 issue fixes [1-12] over the last GA (3.1.0)
> release.
>
> Reported Issues:
>
>- https://github.com/wso2/product-iots/issues
>
> Source and distribution packages:
>
>- https://github.com/wso2/product-iots/releases/tag/v3.2.0-RC1
>
> Tag to be voted upon:
>
>- https://github.com/wso2/product-iots/releases/tag/v3.2.0-RC1
>
> Please download, test, and vote. The README file under the distribution
> contains guide and instructions on how to try it out locally.
>
> [+] Stable - Go ahead and release
> [-] Broken - Do not release (explain why)
>
> This vote will be open for 72 hours or as needed.
>
> [1] https://github.com/wso2/product-iots/milestone/3?closed=1
> [2] https://github.com/wso2/product-iots/milestone/4?closed=1
> [3] https://github.com/wso2/product-iots/milestone/5?closed=1
> [4] https://github.com/wso2/product-iots/milestone/6?closed=1
> [5] https://github.com/wso2/product-iots/milestone/7?closed=1
> [6] https://github.com/wso2/product-iots/milestone/11?closed=1
> [7] https://github.com/wso2/product-iots/milestone/12?closed=1
> [8] https://github.com/wso2/product-iots/milestone/13?closed=1
> [9] https://github.com/wso2/product-iots/milestone/14?closed=1
> [10] https://github.com/wso2/product-iots/milestone/18?closed=1
> [11] https://github.com/wso2/product-iots/milestone/19?closed=1
> [12] https://github.com/wso2/product-iots/milestone/20?closed=1
>
> Regards,
> The WSO2 IoT Team.
>
> --
> With Regards,
>
> *Rasika Perera*
> Senior Software Engineer
> LinkedIn: http://lk.linkedin.com/in/rasika90
>
> 
>
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
>



-- 
Inosh Perera
Senior Software Engineer, WSO2 Inc.
Tel: 077813 7285, 0785293686
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Can we ship Identity Management / Identity Governance features with APIM by default.

[Asela Pathberiya]

On Mon, Feb 5, 2018 at 12:10 PM, Nuwan Dias  wrote:

> As mentioned on the subject itself, these are Identity Management and
> Identity Governance features. They don't closely tie in with API
> Management. Therefore I think its fine to recommend IS for those kind of
> use cases.
>
> Installing these features to APIM at this point in time is also a problem
> due to its roadmap with 3.0. If we install these features into APIM users
> will see these as first class features of our APIM offering, they won't see
> this as something coming from IS.
>

APIM store is public facing for end users.  It already supports for user
registration which is also identity management feature.  It is a question,
why can't it support  features such as  password recovery/policies/email
activation by default.

If product supports for public user registration, it must support for all
other identity management features as well.

Are we removing the user registration from APIM 3.0 ?

Thanks,
Asela.


> Which means that users would expect the same set of features on 3.0 as
> well. Therefore I would be -1 to installing these features on APIM.
>
> On Mon, Feb 5, 2018 at 9:49 AM, Asela Pathberiya  wrote:
>
>> Hi All,
>>
>> There are several customers/users who are looking for $subject with
>> APIM.  Specially following features
>>
>> 1. Account lock/disable
>> 2. Password/Account recovery
>> 3. Password policies
>>
>> We are usually not recommending the feature installation.  Therefore,
>> shall we ship these features by default with APIM.
>>
>> However, we can suggests to use WSO2IS as KM,  but we need to consider on
>>
>> 1.  Cost on running WSO2IS (infra cost)
>> 2.  All in one deployment
>> 3.  First impression on the IAM feature list of APIM.
>>
>> WDYT ?
>>
>> Thanks,
>> Asela.
>>
>> --
>> Thanks & Regards,
>> Asela
>>
>> ATL
>> Mobile : +94 777 625 933 <+94%2077%20762%205933>
>>  +358 449 228 979
>>
>> http://soasecurity.org/
>> http://xacmlinfo.org/
>>
>
>
>
> --
> Nuwan Dias
>
> Software Architect - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729 <+94%2077%20777%205729>
>



-- 
Thanks & Regards,
Asela

ATL
Mobile : +94 777 625 933 <+94%2077%20762%205933>
 +358 449 228 979

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

Re: [Architecture] Can we ship Identity Management / Identity Governance features with APIM by default.

[Sanjeewa Malalgoda]

Yes, i also think same. Using identity server as key manager would be a
better choice as we can get both API and IS fixes via WUM.
But we need to have some solution for all in one scenario. Other than that
any HA deployment have key manager and we can easily replace it with is as
KM and use those features.

Thanks,
sanjeewa.

On Mon, Feb 5, 2018 at 12:10 PM, Nuwan Dias  wrote:

> As mentioned on the subject itself, these are Identity Management and
> Identity Governance features. They don't closely tie in with API
> Management. Therefore I think its fine to recommend IS for those kind of
> use cases.
>
> Installing these features to APIM at this point in time is also a problem
> due to its roadmap with 3.0. If we install these features into APIM users
> will see these as first class features of our APIM offering, they won't see
> this as something coming from IS. Which means that users would expect the
> same set of features on 3.0 as well. Therefore I would be -1 to installing
> these features on APIM.
>
> On Mon, Feb 5, 2018 at 9:49 AM, Asela Pathberiya  wrote:
>
>> Hi All,
>>
>> There are several customers/users who are looking for $subject with
>> APIM.  Specially following features
>>
>> 1. Account lock/disable
>> 2. Password/Account recovery
>> 3. Password policies
>>
>> We are usually not recommending the feature installation.  Therefore,
>> shall we ship these features by default with APIM.
>>
>> However, we can suggests to use WSO2IS as KM,  but we need to consider on
>>
>> 1.  Cost on running WSO2IS (infra cost)
>> 2.  All in one deployment
>> 3.  First impression on the IAM feature list of APIM.
>>
>> WDYT ?
>>
>> Thanks,
>> Asela.
>>
>> --
>> Thanks & Regards,
>> Asela
>>
>> ATL
>> Mobile : +94 777 625 933 <+94%2077%20762%205933>
>>  +358 449 228 979
>>
>> http://soasecurity.org/
>> http://xacmlinfo.org/
>>
>
>
>
> --
> Nuwan Dias
>
> Software Architect - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729 <077%20777%205729>
>



-- 

*Sanjeewa Malalgoda*
WSO2 Inc.
Mobile : +94713068779

blog
:http://sanjeewamalalgoda.blogspot.com/

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

Re: [Architecture] Can we ship Identity Management / Identity Governance features with APIM by default.

[Nuwan Dias]

As mentioned on the subject itself, these are Identity Management and
Identity Governance features. They don't closely tie in with API
Management. Therefore I think its fine to recommend IS for those kind of
use cases.

Installing these features to APIM at this point in time is also a problem
due to its roadmap with 3.0. If we install these features into APIM users
will see these as first class features of our APIM offering, they won't see
this as something coming from IS. Which means that users would expect the
same set of features on 3.0 as well. Therefore I would be -1 to installing
these features on APIM.

On Mon, Feb 5, 2018 at 9:49 AM, Asela Pathberiya  wrote:

> Hi All,
>
> There are several customers/users who are looking for $subject with APIM.
> Specially following features
>
> 1. Account lock/disable
> 2. Password/Account recovery
> 3. Password policies
>
> We are usually not recommending the feature installation.  Therefore,
> shall we ship these features by default with APIM.
>
> However, we can suggests to use WSO2IS as KM,  but we need to consider on
>
> 1.  Cost on running WSO2IS (infra cost)
> 2.  All in one deployment
> 3.  First impression on the IAM feature list of APIM.
>
> WDYT ?
>
> Thanks,
> Asela.
>
> --
> Thanks & Regards,
> Asela
>
> ATL
> Mobile : +94 777 625 933 <+94%2077%20762%205933>
>  +358 449 228 979
>
> http://soasecurity.org/
> http://xacmlinfo.org/
>



-- 
Nuwan Dias

Software Architect - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [IAM] SCIM 2.0 Outbound Connector

[Isuranga Perera]

Hi,

*@Gayan*
yes, *identity-outbound-**provisioning-scim2* has the nearly same code as
* identity-outbound-provisioning-scim. **identity-client-scim2 *simply
encode and decode SCIM objects and validate some actions. As Malithi
suggested we can use version as a connector configuration and instantiate
the appropriate provisioning client. As an alternative, we can instantiate
ScimClient [1] instead of ProvisioningClient since it provides almost all
SCIM version specific functions related to object encoding and decoding.
Anyway, if I'm not mistaken all of these changes are required only if we're
going to use *identity-outbound-provisioning-scim* with SCIM client [2].

*@Malithi*
Will work on the SCIM response error code issue asap.


[1]
https://github.com/IsurangaPerera/identity-client-scim2/blob/ab5bdd6382ce4b055f99b65568c77289472c9c14/src/main/java/org/wso2/scim2/util/SCIMClient.java
[2] https://github.com/wso2-extensions/identity-client-scim2/pull/1


Best Regards
Isuranga Perera

On Sun, Feb 4, 2018 at 2:22 PM, Malithi Edirisinghe 
wrote:

> Hi Gayan,
>
> +1 for the thought. Basically, it's always the CRUD operations being
> triggered for User and Group resources in the outbound provisioning flow
> and based on the version the respective client can initiate calls upon the
> protocol.
> So that's a matter of initializing the appropriate client based on the
> version that will be configured with respect to the protocol version used
> by the outbound party. That means version will be a connector configuration
> and the connector will instantiate the appropriate client upon the version
> with the application of factory pattern.
>
> *@Isuranga*,
> Thanks a lot for the contribution.
> Can we improve debug logs in the client to log respective requests calls
> and responses for outbound party.
> Also, looks like SCIM response errors are being swallowed in the client
> without passing them back to the connector [1]. In that case, the
> provisioning connector might not know if the request has been success or
> not and act accordingly.
>
> [1] https://github.com/wso2-extensions/identity-client-
> scim2/pull/1/files#diff-5d09971e2f15b2c4858e2d49950f571cR75
>
> Thanks,
> Malithi.
>
> On Sat, Feb 3, 2018 at 6:01 PM, Gayan Gunawardana  wrote:
>
>> Hi Isuranga,
>>
>> Thanks you very much for the contribution and definitely this will be a
>> very valuable feature.
>>
>> I went through some of your PRs [1][2]. As I understood*
>> identity-outbound-**provisioning-scim2* has nearly same code as*
>> identity-outbound-provisioning-scim.* There is a good possibility for
>> code duplication. Ideally protocol difference SCIM 1.1 and SCIM 2.0 should
>> be very minimum to the provisioning connector level and protocol difference
>> should be handled from *ProvisioningClient*. I do not think existing
>> SCIM 1.1 provisioning connector do much about SCIM specific logic rather 
>> *org.wso2.carbon.identity.scim.common.impl.ProvisioningClient
>> *handle all HTTP communication according to protocol. Is it possible to
>> switch *ProvisioningClient* based on protocol (SCIM 1.1 and SCIM 2.0) ?
>> @Darshana wdyt?
>>
>> I suppose in [2] swagger documentation doesn't have all error codes. For
>> example user creation has only one error code (404) but there should be
>> many more like 409.
>>
>> Also could you be able to consider about unit test coverage ?
>>
>> Thanks again for your valuable contribution.
>>
>> [1] https://github.com/wso2-extensions/identity-outbound-provisi
>> oning-scim2/pull/1
>> [2] https://github.com/wso2-extensions/identity-client-scim2/pull/1
>> [3] https://github.com/wso2-extensions/identity-outbound-provisi
>> oning-scim/
>>
>> Thanks,
>> Gayan
>>
>> On Mon, Nov 27, 2017 at 1:12 PM, Isuranga Perera <
>> isurangamper...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> I've submitted PRs for identity-client-scim2 [1] and
>>> identity-outbound-provisioning-scim2 [2]. There were some missing
>>> functions in charon3 such as some decoding methods, setter methods etc.
>>> Therefore I used some workarounds and also I have submitted some PRs for
>>> some of those missing functions.
>>>
>>> *PRs for Charon*
>>> IDENTITY-6962: Client-side validator for Charon 3 [3] fixed with PR [4]
>>> IDENTITY-6960: Missing Charon setter method of user password [5] fixed
>>> with PR [6]
>>>
>>>
>>>
>>> [1] https://github.com/wso2-extensions/identity-client-scim2/pull/1
>>> [2] https://github.com/wso2-extensions/identity-outbound-pro
>>> visioning-scim2/pull/1
>>> [3] https://wso2.org/jira/browse/IDENTITY-6962
>>> [4] https://github.com/wso2/charon/pull/80
>>> [5] https://github.com/wso2/charon/pull/79
>>>
>>> Best Regards
>>> Isuranga Perera
>>>
>>> On Thu, Nov 23, 2017 at 9:54 AM, Johann Nallathamby 
>>> wrote:
>>>
 Thanks a lot Maheshika.

 Regards,
 Johann.

 On Thu, Nov 23, 2017 at 8:56 AM, Maheshika Goonetilleke <
 mahesh...@wso2.com> wrote:

> Hi Johann
>

[Architecture] Can we ship Identity Management / Identity Governance features with APIM by default.

[Asela Pathberiya]

Hi All,

There are several customers/users who are looking for $subject with APIM.
Specially following features

1. Account lock/disable
2. Password/Account recovery
3. Password policies

We are usually not recommending the feature installation.  Therefore,
shall we ship these features by default with APIM.

However, we can suggests to use WSO2IS as KM,  but we need to consider on

1.  Cost on running WSO2IS (infra cost)
2.  All in one deployment
3.  First impression on the IAM feature list of APIM.

WDYT ?

Thanks,
Asela.

-- 
Thanks & Regards,
Asela

ATL
Mobile : +94 777 625 933
 +358 449 228 979

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

Re: [Architecture] [IAM] UX design for Retryable Outbound Provisioning Feature.

[Malithi Edirisinghe]

Hi Menaka,

I have few suggestions.

1. This is with related to outbound provisioning. So I think the name
should indicate that aspect. Moreover, this feature is more related with
monitoring aspect and triggering some actions based on that. Maybe
something like 'Outbound Provisioning Monitor' would be more suitable.
Also, I think this should move under some menu item like 'Monitor' or
'Manage'.

2. I think it's better to have an option to select all entries and perform
some action (retry/delete). Yet, below should be considered.

   - Should we allows retry for success operations. I think when success
   operations only 'delete' operations should be allowed
   - Is there a filter option as 'All' which will list both failed and
   success operations. If someone select all entries from that and perform a
   retry what would be the expected behavior. IMO, in such a case, the message
   to the end user should indicate only failed operations are retried.
   - There's a difference between deleting a success entry and a failed
   entry. If a failed entry is deleted it cannot be retried again and there's
   no need of a retry operation for a success entry. So, IMO, when deleting a
   failed entry the impact should be highlighted to the end user and upon
   confirmation entry should be deleted.

Thanks,
Malithi.

On Fri, Feb 2, 2018 at 9:47 AM, Menaka Jayawardena  wrote:

> Hi Imesh,
>
> Thank you very much for the suggestions. Please find my comments inline.
>
> Hi Menaka,

 Please find the bellow suggestions.

 IMHO, the filtration controls should resemble a visual connection to
 the listing.

>>>  I have followed the default UX design in Management Console for this
> otherwise it would break the consistancy.
>
>>
 Retry and delete actions should get a more prominence since they are
 the primary actions of this page

>>> +1 for this.
>
> If we could filter the data on the selection of each filtration criteria,
 IMO it's better to remove the "filter" button. For and example if we could
 update the listing according to the selected criteria, the action is not
 needed.

>>>  Yes. This could be done.
>
> When Deleting / Retrying without selecting a record, IMO it's better to
 disable the buttons until the user select at-least one record. WDYT?

>>>  +1.
>
>> --
 *Thanks and Best Regards,*
 Imesh Ashandimal Chandrasiri
 *Software Engineer*
 WSO2, Inc.
 lean . enterprise . middleware
 *E:* ime...@wso2.com | *P:* 0716519187 <071%20651%209187>

 --
>> *Menaka Jayawardena*
>> *Software Engineer - WSO2 Inc*
>> *Tel : 071 350 5470*
>> *LinkedIn: https://lk.linkedin.com/in/menakajayawardena
>> *
>> *Blog: https://menakamadushanka.wordpress.com/
>> *
>>
>>
>
>
> --
> *Menaka Jayawardena*
> *Software Engineer - WSO2 Inc*
> *Tel : 071 350 5470*
> *LinkedIn: https://lk.linkedin.com/in/menakajayawardena
> *
> *Blog: https://menakamadushanka.wordpress.com/
> *
>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 

*Malithi Edirisinghe*
Associate Technical Lead
WSO2 Inc.

Mobile : +94 (0) 718176807
malit...@wso2.com
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [MB] MQTT : support around 100K mqtt connections using WSO2 MB

[Youcef HILEM]

Hi Hasitha,

WSO2 MB is AMQP compliant.
Why not use Apache Qpid Dispatch Router
(https://qpid.apache.org/components/dispatch-router/index.html) to handle
all connection management like Enmasse (http://enmasse.io/) ?

Thanks 
Youcef HILEM



--
Sent from: 
http://wso2-oxygen-tank.10903.n7.nabble.com/WSO2-Architecture-f62919.html
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [MB] MQTT : support around 100K mqtt connections using WSO2 MB

[Youcef HILEM]

Hi,

For information our solution:
- will rely on the standard MQTT over Websocket
(http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/csprd02/mqtt-v3.1.1-csprd02.html#_Toc385349863)
- will use WSO2 APIM Websocket APIs
(https://wso2.com/library/articles/2017/05/introducing-websocket-apis-with-wso2-api-manager/).
Sample with kafka
(https://medium.com/@lahirugmg/managed-websocket-api-for-kafka-with-wso2-api-manager-3e17f6e9a121)

I keep an eye on the support of MQTT over WebSocket in WSO2 MB 4
(https://wso2.org/jira/browse/MB-1688).

Tanks
Youcef HILEM



--
Sent from: 
http://wso2-oxygen-tank.10903.n7.nabble.com/WSO2-Architecture-f62919.html
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] WSO2 API Manager 2.1.0-update9 Released !

[Bhathiya Jayasekara]

On Fri, Feb 2, 2018 at 5:59 PM, Chamila Adhikarinayake 
wrote:

> The WSO2 API Manager team is pleased to announce the release of version
> 2.1.0-update9 of API Manager.
>
> WSO2 API Manager is a platform for creating, managing, consuming and
> monitoring APIs. It employs proven SOA best practices to solve a wide range
> of API management challenges such as API provisioning, API governance, API
> security and API monitoring. It combines some of the most powerful and
> mature components of the WSO2's state-of-the-art Carbon platform to deliver
> a smooth and end-to-end API management experience while catering to both
> API publisher and API consumer requirements.
>
> WSO2 API Manager is comprised of several modules.
>
>-
>
>API Provider: Define new APIs and manage them
>-
>
>API Store: Browse published APIs and subscribe to them
>-
>
>API Gateway: The underlying API runtime based on WSO2 ESB
>-
>
>API Key Manager: Performs Key Generation and Key Validation
>functionalities
>-
>
>API Traffic Manager: Performs Rate Limiting of API Requests
>
> For more information on WSO2 API Manager please visit
> http://wso2.com/products/api-manager. Also, take a look at the online
> product documentation
> .
>
> Distributions
>
> WSO2 APIM 2.1.0-update9.zip
> 
>
> WSO2 APIM Analytics 2.1.0-update5.zip
> 
> How to Run
>
>1.
>
>Extract the downloaded zip
>2.
>
>Go to the bin directory in the extracted folder
>3.
>
>Run the wso2server.sh or wso2server.bat as appropriate
>4.
>
>Launch a web browser and navigate to https://localhost:9443/publisher
>to access the API publisher web app
>5.
>
>Navigate to https://localhost:9443/store to access the API store
>6.
>
>Navigate to https://localhost:9443/admin to access Admin Portal
>7.
>
>Use "admin", "admin" as the username and password to log in as an admin
>
> Bug Fixes And Improvements in 2.1.0-update9
>
> Please refer following locations for WSO2 API Manager 2.1.0-update9 Bug
> fixes and Improvements
>
>
>1.
>
>JIRA 
>2.
>
>GitHub (carbon-apimgt)
>
> 
>3.
>
>GitHub (product-apim)
>
> 
>
> Known Issues
>
> All the open issues pertaining to WSO2 API Manager are reported at the
> following location:
>
>1.
>
>JIRA 
>2.
>
>GitHub (carbon-apimgt)
>
>3.
>
>GitHub (product-apim)
>
>
> How You Can ContributeMailing Lists
>
> Join our mailing list and correspond with the developers directly.
>
>-
>
>Developer List: d...@wso2.org | Subscribe | Mail Archive
>
>-
>
>User List: u...@wso2.org | Subscribe | Mail Archive
>
>-
>
>User Forum: Stack Overflow
>
>
> Reporting Issues
>
> We encourage you to report issues, documentation faults and feature
> requests regarding WSO2 API Manager through the WSO2 API Manager Git
> issues 
>
> -- WSO2 API Manager Team --
>
> --
> Regards,
> Chamila Adhikarinayake
> Senior Software Engineer
> WSO2, Inc.
> Mobile - +94712346437 <+94%2071%20234%206437>
> Email  - chami...@wso2.com
> Blog  -  http://helpfromadhi.blogspot.com/
>



-- 
*Bhathiya Jayasekara*
*Associate Technical Lead,*
*WSO2 inc., http://wso2.com *

*Phone: +94715478185*
*LinkedIn: http://www.linkedin.com/in/bhathiyaj
*
*Twitter: https://twitter.com/bhathiyax *
*Blog: http://movingaheadblog.blogspot.com
*
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture