Re: [Dev] [VOTE] Release WSO2 Identity Server 5.11.0 RC1
Hi All, Tested the following and no blocking issues found, - Role management REST API - User, Group, and Role management functionalities with the console app - User and Role management with the management console [+] Stable - go ahead and release Thanks, Ashen -- Ashen Weerathunga | Senior Software Engineer | WSO2 Inc. (m) +94716042995 | (w) +94112145345 | Email: as...@wso2.com <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.6.1 RC2
Hi All, Tested the new role and group separation changes with the Kernel 4.6.1 RC2 and no blocking issues found. [+] Stable - go ahead and release Thanks, Ashen On Wed, Nov 11, 2020 at 11:05 AM Sominda Gamage wrote: > Hi all, > > I have tested the following SCIM endpoints with MsSQL2019 and MySQL8 and > they were performing as expected. > >- Users Endpoint >- Me Endpoint >- Groups Endpoint >- Roles Endpoint >- Bulk Endpoint >- ResourceType Endpoint > > Here is my +1. > > Regards, > Sominda. > > On Tue, Nov 10, 2020 at 9:34 PM Gayashan Bombuwala > wrote: > >> Hi all, >> >> Tested below scenarios. >> >>- StartTLS with Read Only LDAP & Read Write LDAP User Stores. >>- SCIM2 GET Groups and PATCH Group (Add Member, Remove Member, Rename >>Group) operations on UniqueID Read Write LDAP User Store. >> >> No blocking issues found. >> >> [+] Stable - Go ahead and release >> >> Best Regards, >> >> On Tue, Nov 10, 2020 at 6:32 PM Mushthaq Rumy wrote: >> >>> Hi All, >>> >>> +1 from the API Manager Team. >>> >>> Thanks & Regards, >>> Mushthaq >>> >>> On Tue, Nov 10, 2020 at 6:11 PM Nadeeshani Pathirennehelage < >>> nadeesha...@wso2.com> wrote: >>> >>>> Hi All, >>>> >>>> +1 from the Security Team as all the security scans got completed. >>>> >>>> Best Regards, >>>> Nadeeshani. >>>> >>>> On Sat, Nov 7, 2020 at 3:06 PM Kanapriya Kuleswararajan < >>>> kanapr...@wso2.com> wrote: >>>> >>>>> Hi Devs, >>>>> >>>>> *WSO2 Carbon Kernel 4.6.1 RC2 Release Vote*. >>>>> >>>>> Please download and test your products with kernel 4.6.1 RC2 and vote. >>>>> The vote will be open for 72 hours or longer as needed. >>>>> >>>>> *Maven staging repository:* >>>>> https://maven.wso2.org/nexus/content/repositories/orgwso2carbon-4915 >>>>> >>>>> *The tag to be voted upon:* >>>>> https://github.com/wso2/carbon-kernel/releases/tag/v4.6.1-RC2 >>>>> >>>>> [- ] Broken - do not release (explain why) >>>>> [+] Stable - go ahead and release >>>>> >>>>> Thanks >>>>> Kanapriya Kuleswararajan >>>>> Senior Software Engineer >>>>> Mobile : - 0774894438 >>>>> Mail : - kanapr...@wso2.com >>>>> LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/ >>>>> WSO2, Inc. >>>>> lean . enterprise . middleware >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>> >>>> >>>> -- >>>> Pathirennehelage Nadeeshani >>>> Senior Software Engineer >>>> Security & Compliance Team >>>> WSO2 Inc. >>>> mobile : +94 716545223 >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>> >>> >>> -- >>> Mushthaq Rumy >>> *Associate Technical Lead* >>> Mobile : +94 (0) 779 492140 >>> Email : musht...@wso2.com >>> WSO2, Inc.; http://wso2.com/ >>> lean . enterprise . middleware. >>> >>> <http://wso2.com/signature> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >> >> >> -- >> *Gayashan Bombuwala* >> Software Engineer | WSO2 >> >> Email: gayash...@wso2.com >> Phone: +94770548334 >> >> [image: https://wso2.com/signature] <https://wso2.com/signature> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> > > > -- > *Sominda Gamage* | Software Engineer| WSO2 Inc. <http://wso2.com/> > (M)+94 719873902 | (E) somi...@wso2.com > <http://wso2.com/signature> > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- Ashen Weerathunga | Senior Software Engineer | WSO2 Inc. (m) +94716042995 | (w) +94112145345 | Email: as...@wso2.com <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How to disable SCIM in IS 5.10.0
Hi Gayan, >From IS 5.10.0 onwards we have enabled SCIM2 by default in the product with the new unique ID based userstore managers. We have removed the disabling option as we will be using the user ID concept moving forward in the product and new portals also using the SCIM API for user management. Thanks, Ashen On Thu, May 28, 2020 at 9:06 PM gayan gunawardana wrote: > Hi Team, > > I was trying to disable SCIM for primary user store in IS 5.10.0. However > I couldn't find necessary property from documentation [1]. Is there a way > to disable SCIM in IS 5.10.0 ? > > [1] > https://is.docs.wso2.com/en/latest/setup/configuring-a-read-write-ldap-user-store/#configuring-a-read-write-ldap-user-store > > > Thanks, > Gayan > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- Ashen Weerathunga | Senior Software Engineer | WSO2 Inc. (m) +94716042995 | (w) +94112145345 | Email: as...@wso2.com <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Deprecating WebContextRoot configuration from WSO2 Identity Server
Hi All, We had the *WebContextRoot* configuration in carbon.xml file and we have been using this to build the URLs within the IS product. But as for our observation, it has not been consistent all the places across the product and therefore the usage of this has been very minimal. Currently, we are carrying out a restructuring effort for the building URLs within the IAM system and we have decided to deprecate the WebContextRoot configuration due to the above reason and as for an alternative you can use the *ProxyContextPath* configuration and you can configure it in the *deployment.yaml* as below, > *[server]**proxy_context_path="abc"* Please note that this change will be effective from the WSO2 Identity Server 5.11.0 release. Thanks, Ashen -- Ashen Weerathunga | Senior Software Engineer | WSO2 Inc. (m) +94716042995 | (w) +94112145345 | Email: as...@wso2.com <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] IS 5.10.0 Unique user identifier across the system
Hi Gayan, >From 5.10.0 onwards we have introduced a new unique user identifier in the user core level with a new set of APIs. Therefore the username is not immutable at the user core level now. But we have not implemented username renaming capability yet as we still consuming old user core APIs and use the username as the user identifier in the other components such as OAuth/identity framework etc. Therefore we need to migrate other components and use the uniqueID as the user identifier everywhere in the system. Then only we can provide the username renaming capability. So we will provide these capabilities in future releases. Thanks, Ashen On Tue, Apr 7, 2020 at 9:46 PM gayan gunawardana wrote: > Hi Team, > > As per [1] it looks like username attribute is not immutable any more with > new unique user identifier implementation. > Are there any SCIM or RemoteUserStoreManagerServce Apis available to alter > username ? > > [1] https://github.com/wso2/product-is/releases/tag/v5.10.0-rc2 > > -- > Gayan > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- Ashen Weerathunga | Senior Software Engineer | WSO2 Inc. (m) +94716042995 | (w) +94112145345 | Email: as...@wso2.com <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Identity Server 5.11.0 M12 Released!
WSO2 Identity and Access Management team is pleased to announce the release of Identity Server 5.11.0 M12! <https://github.com/wso2/product-is/blob/master/release-guidelines.md#download> Download You can download WSO2 Identity Server 5.11.0 M12 from here <https://github.com/wso2/product-is/releases/download/v5.11.0-m12/wso2is-5.11.0-m12.zip> . <https://github.com/wso2/product-is/blob/master/release-guidelines.md#how-to-run>How to run 1. Extract the downloaded zip file. 2. Go to the *bin* directory in the extracted folder. 3. Run the *wso2server.sh* file if you are on a Linux/Mac OS or run the *wso2server.bat* file if you are on a Windows OS. 4. Optionally, if you need to start the OSGi console with the server, use the *-DosgiConsole* property when starting the server. <https://github.com/wso2/product-is/blob/master/release-guidelines.md#whats-new-in-wso2-identity-server-released_version>What's new - Provide the capability to encrypt internal sensitive data with symmetric encryption. - Enable configuration store support for all the common databases. *Other fixes & features* A list of all the new features and bug fixes shipped with this release can be found in the following locations: - IS Runtime <https://github.com/wso2/product-is/milestone/114?closed=1> - IAM Portals <https://github.com/wso2/identity-apps/milestone/11?closed=1> <https://github.com/wso2/product-is/blob/master/release-guidelines.md#known-issues>Known Issues All the open issues pertaining to WSO2 Identity Server are reported at the following locations: - IS Runtime <https://github.com/wso2/product-is/issues> - IAM Portals <https://github.com/wso2/identity-apps/issues?q=is%3Aopen+is%3Aissue> <https://github.com/wso2/product-is/blob/master/release-guidelines.md#contribute-to-wso2-identity-server>Contribute to WSO2 Identity Server <https://github.com/wso2/product-is/blob/master/release-guidelines.md#mailing-lists>Mailing Lists Join our mailing lists and correspond with the developers directly. We also encourage you to take part in discussions related to the product in the architecture mailing list. If you have any questions regarding the product you can use our StackOverflow forum to raise them as well. - Developer List: dev@wso2.org - Architecture List: architect...@wso2.org - User Forum: StackOverflow <http://stackoverflow.com/questions/tagged/wso2is> <https://github.com/wso2/product-is/blob/master/release-guidelines.md#slack-channels>Slack Channels Join us via our wso2is.slack.com <https://join.slack.com/t/wso2is/shared_invite/enQtNzk0MTI1OTg5NjM1LTllODZiMTYzMmY0YzljYjdhZGExZWVkZDUxOWVjZDJkZGIzNTE1NDllYWFhM2MyOGFjMDlkYzJjODJhOWQ4YjE> for even better communication. You can talk to our developers directly regarding any issues, concerns about the product. We encourage you to start discussions or join any ongoing discussions with the team, via our slack channels. - Discussions about developments: Dev Channel <https://wso2is.slack.com/messages/dev> - New releases: Release Announcement Channel <https://wso2is.slack.com/messages/releases> <https://github.com/wso2/product-is/blob/master/release-guidelines.md#reporting-issues>Reporting Issues We encourage you to report issues, improvements, and feature requests regarding WSO2 Identity Server through our public WSO2 Identity Server GIT Issues <https://github.com/wso2/product-is/issues>. *Important: Please be advised that security issues must be reported to secur...@wso2.com , not as GitHub issues, in order to reach the proper audience. We strongly advise following the WSO2 Security Vulnerability Reporting Guidelines <https://docs.wso2.com/display/Security/WSO2+Security+Vulnerability+Reporting+Guidelines> when reporting the security issues.* For more information about WSO2 Identity Server, please see https://wso2.com/identity-and-access-management <https://wso2.com/identity-and-access-management> or visit the WSO2 Oxygen Tank <http://wso2.com/library/> developer portal for additional resources. ~ The WSO2 Identity and Access Management Team ~ -- Ashen Weerathunga | Senior Software Engineer | WSO2 Inc. (m) +94716042995 | (w) +94112145345 | Email: as...@wso2.com <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] [Iam-dev] [VOTE] Release WSO2 Identity Server 5.10.0 RC2
>>>>>> >>>>>>- 5.10.0-M1 >>>>>><https://github.com/wso2/product-is/milestone/95?closed=1> >>>>>>- 5.10.0-M2 >>>>>><https://github.com/wso2/product-is/milestone/96?closed=1> >>>>>>- 5.10.0-M3 >>>>>><https://github.com/wso2/product-is/milestone/97?closed=1> >>>>>>- 5.10.0-M4 >>>>>><https://github.com/wso2/product-is/milestone/98?closed=1> >>>>>>- 5.10.0-M5 >>>>>><https://github.com/wso2/product-is/milestone/99?closed=1> >>>>>>- 5.10.0-M6 >>>>>><https://github.com/wso2/product-is/milestone/100?closed=1> >>>>>>- 5.10.0-M7 >>>>>><https://github.com/wso2/product-is/milestone/101?closed=1> >>>>>>- 5.10.0-M8 >>>>>><https://github.com/wso2/product-is/milestone/102?closed=1> >>>>>>- 5.10.0-M9 >>>>>><https://github.com/wso2/product-is/milestone/103?closed=1> >>>>>>- 5.10.0-Alpha >>>>>><https://github.com/wso2/product-is/milestone/104?closed=1> >>>>>>- 5.10.0-Alpha2 >>>>>><https://github.com/wso2/product-is/milestone/105?closed=1> >>>>>>- 5.10.0-Alpha3 >>>>>><https://github.com/wso2/product-is/milestone/106?closed=1> >>>>>>- 5.10.0-Beta >>>>>><https://github.com/wso2/product-is/milestone/107?closed=1> >>>>>>- 5.10.0-Beta2 >>>>>><https://github.com/wso2/product-is/milestone/108?closed=1> >>>>>>- 5.10.0-Beta3 >>>>>><https://github.com/wso2/product-is/milestone/109?closed=1> >>>>>>- 5.10.0-GA >>>>>><https://github.com/wso2/product-is/milestone/92?closed=1> >>>>>> >>>>>> >>>>>> *Source and Distribution* >>>>>> The source and distribution >>>>>> <https://github.com/wso2/product-is/releases/download/v5.10.0-rc2/wso2is-5.10.0-rc2.zip> >>>>>> are >>>>>> available at >>>>>> https://github.com/wso2/product-is/releases/tag/v5.10.0-rc2 >>>>>> >>>>>> >>>>>> Please download the product, test it, and vote using the following >>>>>> convention. >>>>>> [+] Stable - go ahead and release >>>>>> [-] Broken - do not release (explain why) >>>>>> >>>>>> >>>>>> Thank you, >>>>>> WSO2 Identity and Access Management Team >>>>>> >>>>>> -- >>>>>> *Janak Amarasena* | Senior Software Engineer | WSO2 Inc. >>>>>> (m) +9464144 | (w) +94112145345 | (e) ja...@wso2.com >>>>>> >>>>>> >>>>>> <https://wso2.com/signature> >>>>>> ___ >>>>>> Iam-dev mailing list >>>>>> iam-...@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/iam-dev >>>>>> >>>>> >>>>> >>>>> -- >>>>> *Theviyanthan Krishnamohan (Thivi)* >>>>> Software Engineer | WSO2 Inc. >>>>> Mobile: 94 76 967 >>>>> Email: theviyant...@wso2.com >>>>> >>>>> ___ >>>>> Iam-dev mailing list >>>>> iam-...@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/iam-dev >>>>> >>>> >>>> >>>> -- >>>> *Brion Silva* | Software Engineer | WSO2 Inc. >>>> (m) +94777933830 | (e) br...@wso2.com >>>> >>>> <https://wso2.com/signature> >>>> ___ >>>> Iam-dev mailing list >>>> iam-...@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/iam-dev >>>> >>> ___ >>> Iam-dev mailing list >>> iam-...@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/iam-dev >>> >> >> >> -- >> Sathya Bandara >> Senior Software Engineer >> Blog: https://medium.com/@technospace >> WSO2 Inc. http://wso2.com >> Mobile: (+94) 715 360 421 >> >> <+94%2071%20411%205032> >> ___ >> Architecture mailing list >> architect...@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> > > > -- > *Tharindu Bandara* > Senior Software Engineer | WSO2 > > Email : tharin...@wso2.com > Mobile : +94 714221776 > web : http://wso2.com > <https://www.google.com/url?q=http://wso2.com=D=151765338399=AFQjCNFggB4bSJTKmdqKcBV0VY9xx1ABKg> > > https://wso2.com/signature > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- Ashen Weerathunga | Senior Software Engineer | WSO2 Inc. (m) +94716042995 | (w) +94112145345 | Email: as...@wso2.com <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 IS SAML and External IdPs
Hi Angelo, On Wed, Nov 13, 2019 at 4:44 PM Angelo Immediata wrote: > Hello Ashen > > I just verified again and I can confirm that by passing from APP1 to APP2, > WSO2 IS passes to APP2 only the requested claims. > > Sorry for bothering you :) > Glad to hear that you got it working! Thanks, Ashen > > Cheers, > Angelo > > Il giorno mer 13 nov 2019 alle ore 05:35 Ashen Weerathunga > ha scritto: > >> Hi Angelo, >> >> On Mon, Nov 11, 2019 at 11:18 PM Angelo Immediata >> wrote: >> >>> Hi There >>> I'm using WSO2 IS version 5.8.0 and 5.9.0 >>> >>> Let's suppose the following scenario: I have an external SAML IdP. This >>> external IdP can give me the following fields: >>> >>>- name >>>- familyName >>>- userIdentity >>>- address >>> >>> Lets' suppose that I have 2 service provider. One configured in order to >>> get WSO2 claims name and familyName and the other in order to get >>> userIdentity and address. >>> >>> Now I go on my App1 (configured by using Service Provider 1) and I login >>> by using the external IdP and I can get the name and familyName attribute. >>> Then i switch to App2 without making logout. Obviously WSO2 doesn't ask to >>> me to login but it sends to the APP2 also the App1 params (e.g. claims) and >>> not only the claims required by App2 >>> >>> Is there any way to avoid this situation? I simply want the following: >>> I login by using external IdP >>> >>>- Eternal IdP gives to me all the required attributes >>>- WSO2 by using the full list attribute returned by the external IdP >>>passes to the APP1 attribute name and familyName. When I switch to App2, >>>WSO2 will give to me only userIdentity and address and not also the other >>>ones... >>> >>> Is it possible? >>> >> >> Ideally, it should only send the requested claims of the APP2 when you >> log in to the APP2. >> >> If you have set the subject attribute of APP2 as familyName, you will >> receive the familyName as well. Also, try changing the requested attribute >> of APP1 to another attribute and check whether you can observe the same >> pattern. >> >> Thanks, >> Ashen >> >> >>> >>> Thank you >>> Angelo >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >> >> >> -- >> Ashen Weerathunga | Senior Software Engineer | WSO2 Inc. >> (m) +94716042995 | (w) +94112145345 | Email: as...@wso2.com >> <http://wso2.com/signature> >> >> >> -- Ashen Weerathunga | Senior Software Engineer | WSO2 Inc. (m) +94716042995 | (w) +94112145345 | Email: as...@wso2.com <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 IS SAML and External IdPs
Hi Angelo, On Mon, Nov 11, 2019 at 11:18 PM Angelo Immediata wrote: > Hi There > I'm using WSO2 IS version 5.8.0 and 5.9.0 > > Let's suppose the following scenario: I have an external SAML IdP. This > external IdP can give me the following fields: > >- name >- familyName >- userIdentity >- address > > Lets' suppose that I have 2 service provider. One configured in order to > get WSO2 claims name and familyName and the other in order to get > userIdentity and address. > > Now I go on my App1 (configured by using Service Provider 1) and I login > by using the external IdP and I can get the name and familyName attribute. > Then i switch to App2 without making logout. Obviously WSO2 doesn't ask to > me to login but it sends to the APP2 also the App1 params (e.g. claims) and > not only the claims required by App2 > > Is there any way to avoid this situation? I simply want the following: > I login by using external IdP > >- Eternal IdP gives to me all the required attributes >- WSO2 by using the full list attribute returned by the external IdP >passes to the APP1 attribute name and familyName. When I switch to App2, >WSO2 will give to me only userIdentity and address and not also the other >ones... > > Is it possible? > Ideally, it should only send the requested claims of the APP2 when you log in to the APP2. If you have set the subject attribute of APP2 as familyName, you will receive the familyName as well. Also, try changing the requested attribute of APP1 to another attribute and check whether you can observe the same pattern. Thanks, Ashen > > Thank you > Angelo > _______ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- Ashen Weerathunga | Senior Software Engineer | WSO2 Inc. (m) +94716042995 | (w) +94112145345 | Email: as...@wso2.com <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [IAM] User association during Adaptive authentication
Hi Sameera, On Thu, Oct 17, 2019 at 8:04 PM Sameera Wickramasekara wrote: > Hi Devs, > > I am looking for a way to get the roles of a user in an adaptive > authentication script in *IS 5.8.0* in the following special scenario. > > >- The user authenticates through GitHub federated IDP. >- The user can be already present in the user store registered from >another means. >- The email attribute will be used as the unique identifier (common >attribute) to associate the user > > > The requirement is to check if the user currently authenticating > through GitHub already exists in the userstore with the same email address > and if present, retrieve the list of roles for that user. > currently we can retrieve the roles of the logging in user but it does not > address the above scenario because IFAIU user association happens after the > adaptive authentication process. > Yes, the user association happens during the post-authentication process. When you have enabled JIT provisioning for the GitHub federated IDP, during the 1st login it will create a new user in the local user store with the same username (email) and then it will associate the authenticated federated user with the local user. When you try to do a role comparison during the authentication process via an adaptive authentication function (eg: hasAnyOfTheRoles()), it will retrieve the roles of the local user. Therefore in your case, if the user is already created in the local userstore you should be able to check the roles of the existing local user during the adaptive authentication process. That way you should be able to achieve your requirement AFAIU. Thanks, Ashen > > I have gone through resources [1] and skimmed through [2]. Appreciate if > you could provide any insight into a solution. > > > [1] - > https://docs.wso2.com/display/IS580/Adaptive+Authentication+JS+API+Reference#AdaptiveAuthenticationJSAPIReference-contextObject > [2] - > https://github.com/wso2-extensions/identity-conditional-auth-functions/tree/master/components/org.wso2.carbon.identity.conditional.auth.functions.user/src/main/java/org/wso2/carbon/identity/conditional/auth/functions/user > > > Thanks, > Sameera > > > > -- > *Sameera Wickramasekara* > Senior Software Engineer > WSO2 > lean . enterprise . middleware > Mobile : +94(0) 714652035 > <https://wso2.com/signature> > > _______ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- Ashen Weerathunga | Senior Software Engineer | WSO2 Inc. (m) +94716042995 | (w) +94112145345 | Email: as...@wso2.com <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [VOTE] Release WSO2 Identity Server 5.9.0 RC2
>>>> Hi all, >>>> >>>> >>>> Verified and validated below listed features are working as expected. >>>> >>>> >>>> Test Environment OS- MAC O/S, Windows-Server-2016-standard-64bit >>>> >>>>Java version- 1.8.0_171, 11.0.4 >>>> >>>> Database - H2, Oracle 12c >>>> >>>> User type, Primary, Secondary, Super user and Tenant user >>>> >>>> >>>> >>>>- User management with multilayer approval >>>>- Manage user stores(Create,update,delete,disable) >>>>- Configuring Claims for a Service Provider >>>>- Consent Management for Self Sign Up >>>>- Single Sign-On / Federated authentication for a web application >>>>with SAML - SP-Init, IDP-Init >>>>- SAML2 IdP Initiated Single Logout >>>> >>>> Front channel post binding >>>> Front channel redirect binding >>>> Backchannel >>>> >>>>- SAML SSO with end-user consent and claim mapping >>>>- Add a custom claim to OIDC >>>>- Adding Multiple Federated authenticators >>>>- By-parsing the IS authenticator selection page >>>>- Identity Analytics-SSO analyzed via WSO2 IS Analytics. >>>>- QSG- Self signup, workflow management >>>>- JIT provision >>>>- Ask Password >>>>- Add Email template >>>>- Connectors- GITHUB, LinkedIn, Google >>>>- Installing as a Windows Service (Java version- 1.8.0_171) >>>>- REST APIs for the user portal >>>> >>>>Account Recovery - Update challenge questions answers >>>> >>>>Authorized OAuth Apps - List and revoke >>>> >>>>User session management >>>> >>>>Pending Approvals >>>> >>>> >>>> +1 to proceed. >>>> >>>> On Wed, Oct 2, 2019 at 4:26 PM Buddhima Udaranga >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> We have tested the Configuration Management REST API with the WSO2 IS >>>>> 5.9.0-RC2 with the MySQL database. No blocker issues found. +1 to proceed. >>>>> >>>>> Thanks, >>>>> *Buddhima Udaranga*|Software Engineer| WSO2 Inc. <http://wso2.com/> >>>>> (M)+94 714742094 | (E) buddhi...@wso2.com >>>>> <https://wso2.com/signature> >>>>> >>>>> >>>>> On Wed, Oct 2, 2019 at 10:59 AM Piraveena Paralogarajah < >>>>> pirave...@wso2.com> wrote: >>>>> >>>>>> Hi all, >>>>>> >>>>>> >>>>>> We are pleased to announce the second release candidate of WSO2 >>>>>> Identity Server 5.9.0. >>>>>> >>>>>> >>>>>> >>>>>> New Features >>>>>> >>>>>>- >>>>>> >>>>>>An improved, simpler configuration model >>>>>>- >>>>>> >>>>>>RESTful APIs for user self-services >>>>>>- >>>>>> >>>>>>Passwordless authentication with WebAuthn >>>>>>- >>>>>> >>>>>>Reusable script library for adaptive authentication >>>>>>- >>>>>> >>>>>>Cross-protocol single logout capability >>>>>>- >>>>>> >>>>>>Inbuilt support to view and revoke user sessions >>>>>>- >>>>>> >>>>>>Azure AD/Office365 multi-domain federation support >>>>>> >>>>>> >>>>>> >>>>>> Fixes >>>>>> >>>>>> This release includes the following issue fixes and improvements: >>>>>> >>>>>>- >>>>>> >>>>>>5.9.0-m1 >>>>>><https://github.com/wso2/product-is/milestone/85?closed=1> >>>>>>- >>>>>> >>>>>>5.9.0-m2 >>>>>><https://github.com/wso2/product-is/milestone/86?closed=1
[Dev] [IAM] Implementing a unique user identifier in WSO2 Identity Server
Hi All, Currently, we consider username of the user as an immutable attribute across the Identity Server and we do not maintain any other unique user identifier for all the users apart from the SCIM ID which is only applicable for SCIM enabled user stores. So we are in the process of introducing an immutable user identifier that is unique across the system and maintains a mapping with all the other user attributes which will enable the following capabilities in the product. - *Provide a unique user identifier across the system* - This id will be used for new Admin REST APIs, Identify the user internally and the same ID will be used as the SCIM ID as well. - *Username renaming capability* - The users will be able to change them without having any impact on the existing system. - *Multi-attribute login capability* - The users will be able to have multiple login identifiers such as username, email address, mobile number or any other identifier that’s unique across the system as for their preference. For this, we will be introducing a new UserStoreManager interface with the new APIs and the relevant implementations to work with the unique user ID as below, [image: Unique user identifier for IS .jpg] During discussions we had so far, usercore API implementation and the impact for other dependant components were discussed in detail under the following categories, *New product deployments:* - They can directly start using the new functionalities as they are enabled by default in the product. *Existing **product deployments** which does not require new functionalities:* - These types of users should be able to disable new functionalities and use the old implementation. A configuration can be used to switch off the new functionalities. *Existing **product deployments** which **require* *new functionalities**:* - These users will require a data migration and we need to finalize the process. - In this scenario, we discussed on supporting existing usercore APIs as well in a migrated environment to make sure existing dependent components are not breaking. So all the dependent components can be migrated eventually to the new usercore APIs which work with the new user ID. - New usercore APIs should consider supporting existing event listeners for the relevant user operations to maintain backward compatibility. - Apart from the above concerns we need to address the performance aspect as well. So in this process, the following dependent components should be migrated to work with new APIs eventually, - Identity framework - SCIM implementation - Basic authenticator - Management console - OAuth2 components (Password grant, etc) - Any other dependant products/components We will be having continues discussions on this while doing the implementation and highly appreciate your feedback as well. Thanks, Ashen -- Ashen Weerathunga | Senior Software Engineer | WSO2 Inc. (m) +94716042995 | (w) +94112145345 | Email: as...@wso2.com <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DEV] [IAM] Updating the password of an authenticated user in SCIM2
Hi Brion, There can be multiple use cases where the users need to change the password such as forgot password recovery and changing the password manually as they required. So in this case we provide the option to change the users password manually without any recovery options. Therefore as Ruwan mentioned we need to request the existing password as a security measure. So it's better to go with that option and it should be validated as well other than just doing it for improve the user experience. So you may use the provided existing password to authenticate the /Me API and if It's successful only, the new password will be updated. Thanks, Ashen On Tue, Aug 6, 2019 at 3:12 PM Ruwan Abeykoon wrote: > Hi Brion, > > The reason we ask to provide the current password is a security measure. > Someone have the users session should not be able to update the password or > any primary security related data without proving he has access to that > information. > > For password, the user has to prove that he knows the(existing) password > for phone number, user has to prove that he owns the phone (OTP) > for email, he has to prove that he has access to that email account. > (email confirmation link) > > Hence this needs to be done in a generic way, something like verifiable > claim. > > I do not see a problem attaching the existing password as basic auth, > provided the API is authorized with different mechanism (Token) > Ideally these kind of data update would need to obtain one time short > lived token for the patch operation and the token should be revoked after > first use. > > > Cheers, > Ruwan A > > > On Tue, Aug 6, 2019 at 2:54 PM Brion Silva wrote: > >> >> >> On Tue, Aug 6, 2019 at 2:51 PM Brion Silva wrote: >> >>> Hi All, >>> >>> I'm in the process of implementing the password reset gadget in the new >>> IS user portal. >>> >>> In the new user-portal, we consume the SCIM2 Me endpoint and we have the >>> option to update the user's password using the PATCH operation[1]. This >>> operation does not expect the current password and only rely on the >>> authentication mechanism enforced for the API. So we need to clarify >>> following, >>> >>>1. Current user-dashboard have the UI to capture the existing >>>password. So there will be a difference in user experience. >>>2. Will it be aligned with the general practice of the IAM solutions? >>> >>> As a workaround we can capture the existing password from the new UI and >>> call this PATCH operation using a basic auth header. But it will only >>> provide the existing user-experience. >>> >>> Appreciate your inputs on this. >>> >>> [1] >>> https://docs.wso2.com/display/IS570/apidocs/SCIM2-endpoints/#!/operations#MeEndpoint#patchUserMe >>> >>> Thanks and Best Regards. >>> -- >>> *Brion Silva* | Software Engineer | WSO2 Inc. >>> (m) +94777933830 | (e) br...@wso2.com >>> >>> <https://wso2.com/signature> >>> >> >> >> -- >> *Brion Silva* | Software Engineer | WSO2 Inc. >> (m) +94777933830 | (e) br...@wso2.com >> >> <https://wso2.com/signature> >> > > > -- > Ruwan Abeykoon | Director/Architect | WSO2 Inc. > (w) +947435800 | Email: ruw...@wso2.com > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- Ashen Weerathunga | Senior Software Engineer | WSO2 Inc. (m) +94716042995 | (w) +94112145345 | Email: as...@wso2.com <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [IS] Local dialect in Claim Management REST API
Hi Janak,
Claim dialect list should include the local dialect as well and doing an
internal redirection to a different endpoint is not a proper approach IMO.
Therefore +1 for the 2nd option as it will be a much cleaner approach.
Thanks,
Ashen
On Mon, Aug 5, 2019 at 11:23 PM Malithi Edirisinghe
wrote:
> Hi Janak,
>
> I would opt for option 2.
> So that, from the claim management REST API perspective, the api
> definition would be same and local dialect will only have a reserved id
> which is 'local' and an extended schema from other dialects.
>
> Thanks,
> Malithi
>
>
> On Mon, Aug 5, 2019 at 5:22 PM Janak Amarasena wrote:
>
>> Hi all,
>>
>> When listing all the claim dialects using the Claim Management REST API
>> the local claim dialect is also listed.
>>
>> [
>> {
>> "id": "aHR0cDovL3dzbzIub3JnL2NsYWltcw",
>> "dialectURI": "http://wso2.org/claims;,
>> "link": {
>> "href": "
>> https://localhost:9443/t/carbon.super/api/server/v1/claim-dialects/aHR0cDovL3dzbzIub3JnL2NsYWltcw/claims
>> ",
>> "rel": "claims"
>> }
>> },
>> {
>> "id":
>> "aHR0cDovL3NjaGVtYXMueG1sc29hcC5vcmcvd3MvMjAwNS8wNS9pZGVudGl0eQ",
>> "dialectURI": "http://schemas.xmlsoap.org/ws/2005/05/identity;,
>> "link": {
>> "href": "
>> https://localhost:9443/t/carbon.super/api/server/v1/claim-dialects/aHR0cDovL3NjaGVtYXMueG1sc29hcC5vcmcvd3MvMjAwNS8wNS9pZGVudGl0eQ/claims
>> ",
>> "rel": "claims"
>> }
>> },
>> ...
>>
>> Using the provided link in *href *it is possible to retrieve the set of
>> claims for each dialect except for the *href *for the local claim
>> dialect. A separate endpoint is defined in the swagger[1] for getting
>> claims from the local dialect as the schema returned is significantly
>> different than when calling using another claim dialect.
>>
>> Response when using the local claim dialect when getting claims;
>> [
>> {
>> "id": "aHR0cDovL3dzbzIub3JnL2NsYWltcy9sb2NhbA",
>> "claimURI": "http://wso2.org/claims/local;,
>> "dialectURI": "http://wso2.org/claims;,
>> "description": "Local",
>> "displayOrder": 0,
>> "displayName": "Local",
>> "readOnly": false,
>> "regEx": null,
>> "required": false,
>> "supportedByDefault": false,
>> "attributeMapping": [
>> {
>> "mappedAttribute": "local",
>> "userstore": "PRIMARY"
>> }
>> ],
>> "properties": []
>> },
>> ...
>>
>> Response when using any other dialect when getting claims;
>> [
>> {
>> "id":
>> "dXJuOnNjaW06c2NoZW1hczpjb3JlOjEuMDphZGRyZXNzZXMuZm9ybWF0dGVk",
>> "claimURI": "urn:scim:schemas:core:1.0:addresses.formatted",
>> "claimDialectURI": "urn:scim:schemas:core:1.0",
>> "mappedLocalClaimURI": "
>> http://wso2.org/claims/addresses.formatted;
>> },
>> ...
>>
>> Currently, if the *href* shown for the local claim dialect is used to
>> retrieve the local claims a bad request response is thrown as retrieving
>> local claims has a separate endpoint defined.
>>
>>
>> There are three possible approaches;
>>
>>1. Remove the local claim dialect from listing - There can be
>>drawbacks when implementing UIs as the local claim dialect will have to be
>>separately listed.
>>2. Change the *id* and the *href *to match the endpoint defined in
>>the swagger - The schema returned for the local cliam dialect will still
>> be
>>significantly different from other dialects but a developer will see a
>>difference in the *href* and the *id. *The *id* = "local" *href *= "
>>
>> https://localhost:9443/t/carbon.super/api/server/v1/claim-dialects/local/claims
>>".
>>3. Internally wire the endpoint to be directed to the endpoint
>>defined in the swagger to get local claims - At development time the
>>developer will not see a difference and might use the endpoint
>> incorrectly.
>>
>>
>> [1] -
>> https://app.swaggerhub.com/apis/janakamarasena/IS-ADMIN-CLAIMS/1.0.0
>>
>> Your thoughts are much appreciated in this regards,
>>
>> Thank you,
>> Janak
>>
>> --
>> *Janak Amarasena* | Software Engineer | WSO2 Inc.
>> (m) +9464144 | (w) +94112145345 | (e) ja...@wso2.com
>>
>>
>> <https://wso2.com/signature>
>>
>
>
> --
> *Malithi Edirisinghe* | Technical Lead | WSO2 Inc.
> (m) +94 718176807 | (w) +94 11 214 5345 | (e) malit...@wso2.com
> GET INTEGRATION AGILE
> Integration Agility for Digitally Driven Business
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
--
Ashen Weerathunga | Senior Software Engineer | WSO2 Inc.
(m) +94716042995 | (w) +94112145345 | Email: as...@wso2.com
<http://wso2.com/signature>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Identity Server 5.9.0 M5 Released!
WSO2 Identity and Access Management team is pleased to announce the release of Identity Server 5.9.0 M5! Download You can download WSO2 Identity Server 5.9.0 M5 from here <https://github.com/wso2/product-is/releases/download/v5.9.0-m5/wso2is-5.9.0-m5.zip> . You can download WSO2 Identity Server Analytics 5.9.0 M5 from here <https://github.com/wso2/analytics-is/releases/download/v5.9.0-m5/wso2is-analytics-5.9.0-m5.zip> . How to run 1. Extract the downloaded zip file. 2. Go to the bin directory in the extracted folder. 3. Run the wso2server.sh file if you are on a Linux/Mac OS or run the wso2server.bat file if you are on a Windows OS. 4. Optionally, if you need to start the OSGi console with the server, use the -DosgiConsole property when starting the server. What's new in WSO2 Identity Server 5.9.0 M5 A list of all the new features and bug fixes shipped with this release can be found here <https://github.com/wso2/product-is/milestone/90?closed=1> Known Issues All the open issues pertaining to WSO2 Identity Server are reported at the following location: - IS Runtime <https://github.com/wso2/product-is/issues> - IS Analytics <https://github.com/wso2/analytics-is/issues> Contribute to WSO2 Identity ServerMailing Lists Join our mailing lists and correspond with the developers directly. We also encourage you to take part in discussions related to the product in the architecture mailing list. If you have any questions regarding the product you can use our StackOverflow forum to raise them as well. - Developer List: dev@wso2.org - Architecture List: architect...@wso2.org - User Forum: StackOverflow <http://stackoverflow.com/questions/tagged/wso2is> Reporting Issues We encourage you to report issues, improvements, and feature requests regarding WSO2 Identity Server through our public WSO2 Identity Server GIT Issues <https://github.com/wso2/product-is/issues>. For more information about WSO2 Identity Server, please see https://wso2 .com/identity-and-access-management or visit the WSO2 Oxygen Tank <http://wso2.com/library/> developer portal for additional resources. ~ The WSO2 Identity and Access Management Team ~ -- Ashen Weerathunga | Senior Software Engineer | WSO2 Inc. (m) +94716042995 | (w) +94112145345 | Email: as...@wso2.com <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] [VOTE] Release WSO2 Identity Server 5.8.0 RC3
uct-is/milestone/62?closed=1> >>>>>- 5.8.0-M3 fixes >>>>><https://github.com/wso2/product-is/milestone/61?closed=1> >>>>>- 5.8.0-M2 fixes >>>>><https://github.com/wso2/product-is/milestone/60?closed=1> >>>>>- 5.8.0-M1 fixes >>>>><https://github.com/wso2/product-is/milestone/59?closed=1> >>>>> >>>>> >>>>> Source and distribution >>>>> >>>>> Runtime - https://github.com/wso2/product-is/releases/tag/v >>>>> <https://github.com/wso2/product-is/releases/download/v5.8.0-rc3/wso2is-5.8.0-rc3.zip> >>>>> 5.8.0-rc3 >>>>> <https://github.com/wso2/product-is/releases/download/v5.8.0-rc3/wso2is-5.8.0-rc3.zip> >>>>> Analytics - >>>>> https://github.com/wso2/analytics-is/releases/tag/v5.8.0-rc3 >>>>> <https://github.com/wso2/analytics-is/releases/download/v5.8.0-rc3/wso2is-analytics-5.8.0-rc3.zip> >>>>> >>>>> >>>>> Please download, test the product and vote. >>>>> >>>>> [+] Stable - go ahead and release >>>>> [-] Broken - do not release (explain why) >>>>> >>>>> >>>>> Thanks, >>>>> - WSO2 Identity and Access Management Team - >>>>> >>>>> -- >>>>> >>>>> Hasanthi Dissanayake >>>>> >>>>> Senior Software Engineer | WSO2 >>>>> >>>>> E: hasan...@wso2.com >>>>> M :0718407133| http://wso2.com <http://wso2.com/> >>>>> >>>> >>>> >>>> -- >>>> >>>> Hasanthi Dissanayake >>>> >>>> Senior Software Engineer | WSO2 >>>> >>>> E: hasan...@wso2.com >>>> M :0718407133| http://wso2.com <http://wso2.com/> >>>> >>> >>> >>> -- >>> *Shanika Wickramasinghe* >>> Software Engineer - QA Team >>> >>> Email: shani...@wso2.com >>> Mobile : +94713503563 >>> Web : http://wso2.com >>> >>> <http://wso2.com/signature> >>> >> >> >> -- >> *Isuranga Perera* | Software Engineer | WSO2 Inc. >> +94 71 735 7034 | isura...@wso2.com >> >> ___ >> Architecture mailing list >> architect...@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> > > > -- > > Hasanthi Dissanayake | Senior Software Engineer | WSO2 Inc. > (m) +94718407133 | (w) +94112145345 | Email: hasan...@wso2.com > > ___ > Architecture mailing list > architect...@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > -- Ashen Weerathunga | Senior Software Engineer | WSO2 Inc. (m) +94716042995 | (w) +94112145345 | Email: as...@wso2.com <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Anomaly detection with an Open source ML/Analytic server - GSOC idea
Hi Gayan,
Thank you for your interest in this project. Main objective of this project
would be to integrate anomaly detection with WSO2 Identity Server [1] data.
We will update the project details accordingly. So we are mainly focusing
on authentication data and OAuth access token related data which are
generated from WSO2 IS.
As an example when you consider a login activity there can be following
data,
- Browser and OS related data
- Geo location of the user based on the IP address
- Application related data
- Login time
- Data generated from WSO2 IS (username, userstore, tenant domain, user
roles etc)
So the idea is to derive an anomaly detection model based on the mentioned
data to provide real time results back to WSO2 IS for decision making [2].
We have already integrated the WSO2 Stream Processor with WSO2 IS for
monitoring purpose. Please refer [3] for more details to get an idea about
the data that we already collect.
[1] https://wso2.com/identity-and-access-management
[2] https://docs.wso2.com/display/IS570/Adaptive+Authentication
[3] https://docs.wso2.com/display/IS570/Analytics
Thanks,
Ashen
On Thu, Feb 7, 2019 at 12:10 AM Gayan Kavirathne <
gayankavirathne...@cse.mrt.ac.lk> wrote:
> Hi all,
>
> Thank you very much for the detailed description of the aforementioned
> project idea. Yet. it's not clear when querying the engine with *{User,
> Activity, Time, and activity data} *what is activity data. And it would
> be great if i can access a masked data set before submitting a proposal.
>
> A brief about myself,
> I recently graduated from the Department of CSE at the University of
> Moratuwa. Now I'm following a fulltime masters specialized in Data
> science. My final year R project was on estimating rainfall leveraging
> Commercial Microwave Links (Watch this video we made
> <https://www.youtube.com/watch?v=T9FxUWXMPAM>to get a quick understanding
> ). As a research student, I'm working on a project for Spatio-Temporal
> Analysis of Dengue Epidemics in Sri Lanka using mobility models for
> infectious disease.
>
>
> Best Regards!
> Gayan Sandaruwanthis video we made
> Undergraduate,
> Computer Science & Engineering,
> University Of Moratuwa - Sri Lanka
> Mobile +94779713087
> [image:
> https://lk.linkedin.com/in/gayan-sandaruwan-51b864113?trk=profile-badge]
> <https://lk.linkedin.com/in/gayan-sandaruwan-51b864113?trk=profile-badge>
>
--
*Ashen Weerathunga*
Senior Software Engineer
WSO2 Inc.: http://wso2.com
lean.enterprise.middleware
Email: as...@wso2.com
Mobile: +94716042995
LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga
<http://lk.linkedin.com/in/ashenweerathunga>*
<http://wso2.com/signature>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] [VOTE] Release of WSO2 Identity Server 5.6.0 RC3
>><https://github.com/wso2/product-is/milestone/36?closed=1> >>>>>>>>>>- 5.6.0-M5 Fixes >>>>>>>>>><https://github.com/wso2/product-is/milestone/35?closed=1> >>>>>>>>>>- 5.6.0-M4 Fixes >>>>>>>>>><https://github.com/wso2/product-is/milestone/34?closed=1> >>>>>>>>>>- 5.6.0-M3 Fixes >>>>>>>>>><https://github.com/wso2/product-is/milestone/33?closed=1> >>>>>>>>>>- 5.6.0-M2 Fixes >>>>>>>>>><https://github.com/wso2/product-is/milestone/31?closed=1> >>>>>>>>>>- 5.6.0-M1 Fixes >>>>>>>>>><https://github.com/wso2/product-is/milestone/30?closed=1> >>>>>>>>>> >>>>>>>>>> Source and distribution, >>>>>>>>>> Runtime - >>>>>>>>>> https://github.com/wso2/product-is/releases/tag/v5.6.0-rc3 >>>>>>>>>> Analytics - >>>>>>>>>> https://github.com/wso2/analytics-is/releases/v5.6.0-rc3 >>>>>>>>>> >>>>>>>>>> Please download, test the product and vote. >>>>>>>>>> >>>>>>>>>> [+] Stable - go ahead and release >>>>>>>>>> [-] Broken - do not release (explain why) >>>>>>>>>> >>>>>>>>>> Thanks, >>>>>>>>>> WSO2 Identity and Access Management Team >>>>>>>>>> -- >>>>>>>>>> >>>>>>>>>> Madawa Soysa / Senior Software Engineer >>>>>>>>>> mada...@wso2.com / +94714616050 >>>>>>>>>> >>>>>>>>>> *WSO2 Inc.* >>>>>>>>>> lean.enterprise.middleware >>>>>>>>>> >>>>>>>>>> <https://wso2.com/signature> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> >>>>>>>>> Vihanga Liyanage >>>>>>>>> >>>>>>>>> Software Engineer | WS*Oâ‚‚* Inc. >>>>>>>>> >>>>>>>>> M : +*94710124103* | http://wso2.com >>>>>>>>> >>>>>>>>> [image: http://wso2.com/signature] <http://wso2.com/signature> >>>>>>>>> >>>>>>>>> ___ >>>>>>>>> Dev mailing list >>>>>>>>> Dev@wso2.org >>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Sathya Bandara >>>>>>>> Software Engineer >>>>>>>> WSO2 Inc. http://wso2.com >>>>>>>> Mobile: (+94) 715 360 421 <+94%2071%20411%205032> >>>>>>>> >>>>>>>> <+94%2071%20411%205032> >>>>>>>> >>>>>>>> ___ >>>>>>>> Dev mailing list >>>>>>>> Dev@wso2.org >>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> *Dewni Weeraman* >>>>>>> Trainee Software Engineer | WSO2 >>>>>>> >>>>>>> Email: de...@wso2.com >>>>>>> Mobile: +94772979049 >>>>>>> Web: http://wso2.com/ >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> ___ >>>>>>> Architecture mailing list >>>>>>> architect...@wso2.org >>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> Hasanthi Dissanayake >>>>>> >>>>>> Senior Software Engineer | WSO2 >>>>>> >>>>>> E: hasan...@wso2.com >>>>>> M :0718407133| http://wso2.com <http://wso2.com/> >>>>>> ___ >>>>>> Architecture mailing list >>>>>> architect...@wso2.org >>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>> >>>>> >>>>> >>>>> -- >>>>> *Pulasthi Mahawithana* >>>>> Associate Technical Lead >>>>> WSO2 Inc., http://wso2.com/ >>>>> Mobile: +94-71-5179022 >>>>> Blog: https://medium.com/@pulasthi7/ >>>>> >>>>> <https://wso2.com/signature> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>> >>>> >>>> -- >>>> >>>> >>>> >>>> *Kind Regards,Nipuni Bhagya* >>>> >>>> *Software Engineering Intern* >>>> *WSO2* >>>> >>>> >>>> >>>> *Mobile : +94 0779028904* >>>> ___ >>>> Architecture mailing list >>>> architect...@wso2.org >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>> >>> >>> -- >>> Omindu Rathnaweera >>> Senior Software Engineer, WSO2 Inc. >>> Mobile: +94 771 197 211 >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Isuri Anuradha >> Trainee Software Engineer | WSO2 >> >> Emaii : is...@wso2.com >> Mobile : +94775941280 >> web :http://wso2.com >> >> <http:///wso2.com> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> > > > -- > Ishara Karunarathna > Technical Lead > WSO2 Inc. - lean . enterprise . middleware | wso2.com > > email: isha...@wso2.com, blog: isharaaruna.blogspot.com, mobile: > +94717996791 > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- *Ashen Weerathunga* Senior Software Engineer WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: +94716042995 LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga <http://lk.linkedin.com/in/ashenweerathunga>* <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Authenticating a user with specific user store in WSO2 IS 5.3.0
Hi Shiva, You can find the all the details related to user realm from these documentations [1][2][3][4]. [1] https://docs.wso2.com/display/IS530/Configuring+the+Realm [2] https://docs.wso2.com/display/IS530/Configuring+the+Authorization+Manager [3] https://docs.wso2.com/display/IS530/Configuring+the+System+Administrator [4] https://docs.wso2.com/display/IS530/Configuring+User+Stores Thanks, Ashen On Fri, May 18, 2018 at 5:13 PM Shiva Kumar <shiv...@securelyshare.com> wrote: > Hi Ashen, > > Thanks for your quick reply is it possible to create new realm in wso2, if > yes How? > > On Friday 18 May 2018 05:09 PM, Ashen Weerathunga wrote: > > Hi Shiva, > > Let's assume the user: *Shiva* is in the userstore: *ABC*. So you can use > following two usernames to authenticate, > >- *Shiva* - If you enter the username without userstore domain it will >iterate through the userstores available and do the authentication. >- *ABC/Shiva* - If you enter the username with the userstore domain >appended it will only check the ABC userstore and do the authentication. > > Thanks, > Ashen > > On Fri, May 18, 2018 at 2:53 PM Shiva Kumar <shiv...@securelyshare.com> > wrote: > >> Hi, >> >> I am successfully able to authenticate user with primary userstore. Is >> it possible to do the same with specific user store instead of primary. >> Is realm can help in this? Can I add new realm? in >> https://docs.wso2.com/display/IS530/Configuring+the+Realm there is no >> description on creating and using the realm. >> >> >> Thanks, >> >> Shiva >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> > > > -- > *Ashen Weerathunga* > Senior Software Engineer > WSO2 Inc.: http://wso2.com > lean.enterprise.middleware > > Email: as...@wso2.com > Mobile: +94716042995 > LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga > <http://lk.linkedin.com/in/ashenweerathunga>* > > <http://wso2.com/signature> > > > -- *Ashen Weerathunga* Senior Software Engineer WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: +94716042995 LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga <http://lk.linkedin.com/in/ashenweerathunga>* <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Authenticating a user with specific user store in WSO2 IS 5.3.0
Hi Shiva, Let's assume the user: *Shiva* is in the userstore: *ABC*. So you can use following two usernames to authenticate, - *Shiva* - If you enter the username without userstore domain it will iterate through the userstores available and do the authentication. - *ABC/Shiva* - If you enter the username with the userstore domain appended it will only check the ABC userstore and do the authentication. Thanks, Ashen On Fri, May 18, 2018 at 2:53 PM Shiva Kumar <shiv...@securelyshare.com> wrote: > Hi, > > I am successfully able to authenticate user with primary userstore. Is > it possible to do the same with specific user store instead of primary. > Is realm can help in this? Can I add new realm? in > https://docs.wso2.com/display/IS530/Configuring+the+Realm there is no > description on creating and using the realm. > > > Thanks, > > Shiva > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- *Ashen Weerathunga* Senior Software Engineer WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: +94716042995 LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga <http://lk.linkedin.com/in/ashenweerathunga>* <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB 5.0.0] Unable to login into admin console
Hi Keerthika, This is a known issue [1] with macOS High Sierra and we have fixed it with Carbon Kernel v4.4.22. So this issue does not exist in the latest WSO2 products based on kernel v4.4.22 or higher. [1] https://docs.wso2.com/display/compatibility/Known+Incompatibilities Thanks, Ashen On Sun, Apr 8, 2018 at 7:20 PM, Keerthika Mahendralingam <keerth...@wso2.com > wrote: > Thanks Nirothipan. But changing jdk version didn't help. > > @Prakhash, Thanks, I was able to login successfully after changing the > compression option as "off". But earlier, I was able to login > successfully from my old machine without changing the compression option. > What is the reason behind this? > > Thanks, > Keerthika. > > On Fri, Apr 6, 2018 at 6:59 PM, Prakhash Sivakumar <prakh...@wso2.com> > wrote: > >> Hi Keerthika, >> >> Change the compression option as "off" in the catalina-server.xml. Then >> it should work. >> >> Thanks. >> >> On Fri, Apr 6, 2018 at 6:18 PM, Nirothipan Mehalingam < >> nirothi...@wso2.com> wrote: >> >>> Hi Keerthika, >>> >>> There was a similar issue [1] with JDK 1.8.0_151 but not with JDK >>> 1.8.0_144. However, to confirm whether this is specific to JDK, could you >>> please try with some other version of JDK and see? >>> >>> [1] - https://github.com/wso2/product-ei/issues/1219 >>> >>> Thanks >>> Nirothipan >>> >>> On Fri, Apr 6, 2018 at 6:11 PM, Keerthika Mahendralingam < >>> keerth...@wso2.com> wrote: >>> >>>> Hi All, >>>> >>>> I am getting "403 Forbidden Error" when I tried to login into ESB >>>> admin console. >>>> >>>> Mac OS version : 10.13.2 >>>> Java version : 1.8.0_144 >>>> >>>> What could be the reason? >>>> >>>> Console error: >>>> >>>> [2018-04-06 18:01:13,178] INFO - CarbonUIServiceComponent Mgt Console >>>> URL : https://10.100.5.169:9443/carbon/ >>>> >>>> [2018-04-06 18:01:25,382] WARN - JavaLogger potential cross-site >>>> request forgery (CSRF) attack thwarted (user:, ip:10.100.5.169, >>>> method:POST, uri:/carbon/admin/login_action.jsp, error:required token >>>> is missing from the request) >>>> >>>> Thanks, >>>> Keerthika. >>>> -- >>>> <dev-requ...@wso2.org> >>>> Keerthika Mahendralingam >>>> Senior Software Engineer >>>> Mobile :+94 (0) 776 121144 >>>> keerth...@wso2.com >>>> WSO2, Inc. >>>> lean . enterprise . middleware >>>> >>> >>> >>> >>> -- >>> >>> >>> *M.Nirothipan* >>> *Software Engineer | WSO2* >>> *Mobile : +94 77 2172692* >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Prakhash Sivakumar >> Senior Software Engineer | WSO2 Inc >> Platform Security Team >> Mobile : +94771510080 >> Blog : https://medium.com/@PrakhashS >> > > > > -- > <dev-requ...@wso2.org> > Keerthika Mahendralingam > Senior Software Engineer > Mobile :+94 (0) 776 121144 > keerth...@wso2.com > WSO2, Inc. > lean . enterprise . middleware > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Ashen Weerathunga* Software Engineer WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: +94716042995 <94716042995> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga <http://lk.linkedin.com/in/ashenweerathunga>* <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Unable to find the org.wso2.carbon.user.core package in carbon-kernel 4.4.11 branch
Hi Jason, There was an unnecessary branch have been created with the same name (v4.4.11) which consist of C5 code. That's why the UI showed an incorrect code. So I have removed the incorrect branch and now you can see the correct tag [1] even from the UI. So as Rajith suggested please checkout the v4.4.11 tag by using the following command to get the correct code. git checkout tags/v4.4.11 [1] https://github.com/wso2/carbon-kernel/tree/v4.4.11/core Thanks, Ashen On Fri, Apr 6, 2018 at 12:48 PM, Jason De Silva <jas...@wso2.com> wrote: > Hi Devs, > > I tried to checkout "org.wso2.carbon.user.core > <https://github.com/wso2/carbon-kernel/tree/v4.4.10/core/org.wso2.carbon.user.core>" > v 4.4.11 ( which is used by IS 5.3.0 ). But when I check out to the v > 4.4.11 branch [1] I cannot seem to find the user core packages. However the > org.wso2.carbon.user.core package can be found in other branches e.g [2]. > Any idea what can be the cause for this? > > [1] https://github.com/wso2/carbon-kernel/tree/v4.4.11/core > [2] https://github.com/wso2/carbon-kernel/tree/v4.4.10/core > > Regards, > Jason > > Jason De Silva > *Software Engineer - QA* > Mobile: +94 (0) 772 097 678 > Email: jas...@wso2.com > WSO2 Inc. www.wso2.com > <http://wso2.com/signature> > -- *Ashen Weerathunga* Software Engineer WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: +94716042995 <94716042995> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga <http://lk.linkedin.com/in/ashenweerathunga>* <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] [VOTE] Release WSO2 Identity Server 5.5.0 RC2
Thu, Mar 15, 2018 at 5:19 AM, Darshana Gunawardana < >>>>>> darsh...@wso2.com> wrote: >>>>>> >>>>>>> Hi all, >>>>>>> >>>>>>> We are pleased to announce the second release candidate of WSO2 >>>>>>> Identity Server 5.5.0. >>>>>>> >>>>>>> This release fixes the following issues, >>>>>>> >>>>>>>- >>>>>>>- 5.5.0-RC2 fixes >>>>>>> >>>>>>> <https://github.com/wso2/product-is/issues?q=is%3Aclosed+milestone%3A5.5.0-RC2> >>>>>>>- 5.5.0-RC1 fixes >>>>>>> >>>>>>> <https://github.com/wso2/product-is/issues?q=is%3Aclosed+milestone%3A5.5.0-RC1> >>>>>>>- 5.5.0-Beta fixes >>>>>>> >>>>>>> <https://github.com/wso2/product-is/issues?q=is%3Aclosed+milestone%3A5.5.0-beta> >>>>>>>- 5.5.0-Alpha3 fixes >>>>>>> >>>>>>> <https://github.com/wso2/product-is/issues?q=is%3Aclosed+milestone%3A5.5.0-alpha3> >>>>>>>- 5.5.0-Alpha2 fixes >>>>>>> >>>>>>> <https://github.com/wso2/product-is/issues?q=is%3Aclosed+milestone%3A5.5.0-alpha2> >>>>>>>- 5.5.0-Alpha fixes >>>>>>> >>>>>>> <https://github.com/wso2/product-is/issues?q=is%3Aclosed+milestone%3A5.5.0-alpha> >>>>>>>- 5.5.0-M4 fixes >>>>>>> >>>>>>> <https://github.com/wso2/product-is/issues?q=is%3Aclosed+milestone%3A5.5.0-M4> >>>>>>>- 5.5.0-M3 fixes >>>>>>> >>>>>>> <https://github.com/wso2/product-is/issues?q=is%3Aclosed+milestone%3A5.5.0-M3> >>>>>>>- 5.5.0-M2 fixes >>>>>>> >>>>>>> <https://github.com/wso2/product-is/issues?q=is%3Aclosed+milestone%3A5.5.0-M2> >>>>>>>- 5.5.0-M1 fixes >>>>>>> >>>>>>> <https://github.com/wso2/product-is/issues?q=is%3Aclosed+milestone%3A5.5.0-M1> >>>>>>> >>>>>>> >>>>>>> Source and distribution >>>>>>> >>>>>>> Runtime - https://github.com/wso2/product-is/releases/v5.5.0-rc2 >>>>>>> Analytics - https://github.com/wso2/anal >>>>>>> ytics-is/releases/v5.5.0-rc2 >>>>>>> >>>>>>> >>>>>>> Please download, test the product and vote. >>>>>>> >>>>>>> [+] Stable - go ahead and release >>>>>>> [-] Broken - do not release (explain why) >>>>>>> >>>>>>> >>>>>>> Thanks, >>>>>>> - WSO2 Identity and Access Management Team - >>>>>>> >>>>>>> -- >>>>>>> Regards, >>>>>>> >>>>>>> >>>>>>> *Darshana Gunawardana*Technical Lead >>>>>>> WSO2 Inc.; http://wso2.com >>>>>>> >>>>>>> *E-mail: darsh...@wso2.com <darsh...@wso2.com>* >>>>>>> *Mobile: +94718566859 <+94%2071%20856%206859>*Lean . Enterprise . >>>>>>> Middleware >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> Best Regards, >>>>>> >>>>>> Nuwandi Wickramasinghe >>>>>> >>>>>> Senior Software Engineer >>>>>> >>>>>> WSO2 Inc. >>>>>> >>>>>> Web : http://wso2.com >>>>>> >>>>>> Mobile : 0719214873 <071%20921%204873> >>>>>> >>>>>> ___ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> >>>>> >>>>> *Kind Regards,Nipuni Bhagya* >>>>> >>>>> *Software Engineering Intern* >>>>> *WSO2* >>>>> >>>>> >>>>> >>>>> *Mobile : +94 0779028904 <+94%2077%20767%201807>* >>>>> >>>>> ___ >>>>> Architecture mailing list >>>>> architect...@wso2.org >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Dinali Rosemin Dabarera* >>>> Software Engineer >>>> WSO2 Lanka (pvt) Ltd. >>>> Web: http://wso2.com/ >>>> Email : gdrdabar...@gmail.com >>>> LinkedIn <https://lk.linkedin.com/in/dinalidabarera> >>>> Mobile: +94770198933 <077%20019%208933> >>>> >>>> >>>> >>>> >>>> <https://lk.linkedin.com/in/dinalidabarera> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> Thanks, >>> -- >>> Pushpalanka. >>> -- >>> Pushpalanka Jayawardhana, B.Sc.Eng.(Hons). >>> Senior Software Engineer, WSO2 Lanka (pvt) Ltd; wso2.com/ >>> Mobile: +94779716248 >>> Blog: pushpalankajaya.blogspot.com/ | LinkedIn: lk.linkedin.com/in/p >>> ushpalanka/ | Twitter: @pushpalanka >>> >>> >>> ___ >>> Architecture mailing list >>> architect...@wso2.org >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Denuwanthi De Silva >> Senior Software Engineer; >> WSO2 Inc.; http://wso2.com, >> Email: denuwan...@wso2.com >> Blog: https://denuwanthi.wordpress.com/ >> >> ___ >> Architecture mailing list >> architect...@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Sathya Bandara > Software Engineer > WSO2 Inc. http://wso2.com > Mobile: (+94) 715 360 421 <+94%2071%20411%205032> > > <+94%2071%20411%205032> > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Ashen Weerathunga* Software Engineer WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: +94716042995 <94716042995> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga <http://lk.linkedin.com/in/ashenweerathunga>* <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Identity Server 5.4.0 Update6 Released !!!
The WSO2 Identity and Access Management team is pleased to announce the release of WSO2 Identity Server 5.4.0 Update6. You can build the distribution from the source tag, Runtime: https://github.com/wso2/product-is/releases/tag/v5.4.0-update6 follow the steps given below. *Building from the source* 1. Install Java8 or above 2. Install Apache Maven 3.x.x(https://maven.apache.org/download.cgi#) 3. Get the source, - For the Runtime: Get a clone from https://github.com/wso2/p roduct-is.git and checkout to v5.4.0-update6 tag or you can directly download the source for the tag from https://github.com/wso2/ product-is/releases/tag/v5.4.0-update6 <https://github.com/wso2/product-is/releases/tag/v5.4.0-update6> 4. Run the one of the below maven commands from product-is directory, - *mvn** clean install* (To build the binary and source distributions with the tests) - *mvn** clean install -Dmaven.test.skip=true* (To build the binary and source distributions, without running any of the unit/integration tests) 5. You can find the, - wso2is-5.4.0-update6.zip binary distribution in product-is/modules/distribution/target directory. What's new in WSO2 Identity Server 5.4.0 Update6 New Features & Bug Fixes: A list of new features and bug fixes shipped with this release can be found here <https://github.com/wso2/product-is/milestone/16?closed=1>. Download You can download WSO2 Identity Server 5.4.0 Update6 here <https://github.com/wso2/product-is/releases/download/v5.4.0-update6/wso2is-5.4.0-update6.zip> . Contribute to WSO2 Identity ServerMailing Lists Join our mailing lists and correspond with the developers directly. We also encourage you to take part in discussions related to the product in the architecture mailing list. If you have any questions regarding the product you can use our StackOverflow forum to raise them as well. - Developer List: dev@wso2.org - Architecture List: architect...@wso2.org - User Forum: StackOverflow <http://stackoverflow.com/questions/tagged/wso2is> Reporting Issues We encourage you to report issues, improvements, and feature requests regarding WSO2 Identity Server through our public WSO2 Identity Server GIT Issues <https://github.com/wso2/product-is/issues>. ~ The WSO2 Identity and Access Management Team ~ -- *Ashen Weerathunga* Software Engineer WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: +94716042995 <94716042995> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga <http://lk.linkedin.com/in/ashenweerathunga>* <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Identity Server 5.4.0 Update4 Released !!!
The WSO2 Identity and Access Management team is pleased to announce the release of WSO2 Identity Server 5.4.0 Update4. You can build the distribution from the source tag, Runtime: https://github.com/wso2/product-is/releases/tag/v5.4.0-update4 Analytics: https://github.com/wso2/analytics-is/releases/tag/v5.4.0-update4 follow the steps given below. *Building from the source* 1. Install Java8 or above 2. Install Apache Maven 3.x.x(https://maven.apache.org/download.cgi#) 3. Get the source, - For the Runtime: Get a clone from https://github.com/wso2/p roduct-is.git and checkout to v5.4.0-update4 tag or you can directly download the source for the tag from https://github.com/wso2/ product-is/releases/tag/v5.4.0-update4 <https://github.com/wso2/product-is/releases/tag/v5.4.0-update4> - For the Analytics: Get a clone from https://github.com/wso2/a nalytics-is.git and checkout to v5.4.0-update4 tag or you can directly download the source for the tag from https://github.com/wso2/ analytics-is/releases/tag/v5.4.0-update4 <https://github.com/wso2/analytics-is/releases/tag/v5.4.0-update4> 4. Run the one of the below maven commands from product-is directory, - *mvn** clean install* (To build the binary and source distributions with the tests) - *mvn** clean install -Dmaven.test.skip=true* (To build the binary and source distributions, without running any of the unit/integration tests) 5. You can find the, - wso2is-5.4.0-update4.zip binary distribution in product-is/modules/distribution/target directory. - wso2is-analytics-5.4.0-update4.zip binary distribution in analytics-is/product/distribution/target directory. What's new in WSO2 Identity Server 5.4.0 Update4 New Features & Bug Fixes: A list of new features and bug fixes shipped with this release can be found here <https://github.com/wso2/product-is/milestone/12?closed=1> and here <https://wso2.org/jira/issues/?filter=14508>. Download You can download WSO2 Identity Server 5.4.0 Update4 here <https://github.com/wso2/product-is/releases/download/v5.4.0-update4/wso2is-5.4.0-update4.zip> . Contribute to WSO2 Identity ServerMailing Lists Join our mailing lists and correspond with the developers directly. We also encourage you to take part in discussions related to the product in the architecture mailing list. If you have any questions regarding the product you can use our StackOverflow forum to raise them as well. - Developer List: dev@wso2.org - Architecture List: architect...@wso2.org - User Forum: StackOverflow <http://stackoverflow.com/questions/tagged/wso2is> Reporting Issues We encourage you to report issues, improvements, and feature requests regarding WSO2 Identity Server through our public WSO2 Identity Server GIT Issues <https://github.com/wso2/product-is/issues>. ~ The WSO2 Identity and Access Management Team ~ -- *Ashen Weerathunga* Software Engineer WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: +94716042995 <94716042995> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga <http://lk.linkedin.com/in/ashenweerathunga>* <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How to configure the IS Dashboard for a IS cluster fronted by Nginx
Hi Sashika,
Have you added the proxy port 443 for https connector in
*catalina-server.xml*?
That config needs to be there for the dashboard.
Go to /repository/conf/tomcat/catalina-server.xml and add the
proxy port 443 as below.
wrote:
> Hi Ashen,
>
> The IS clustering guide you pointed out does not contain any information
> to configure the IS dashboard in a cluster setup.
>
> In my scenario, I can log in to the management console successfully but
> the issue occurs when login to the IS dashboard. Could this be due to any
> missing configuration?
>
> Thanks
> Sashika
>
> On Thu, Oct 26, 2017 at 12:35 AM, Ashen Weerathunga <as...@wso2.com>
> wrote:
>
>> Hi Sashika,
>>
>> Can you check with IS 5.4.0 Clustered guide [1].
>> I guess it has the information you need.
>>
>> [1] https://docs.wso2.com/display/IS540/Clustered+Deployment
>>
>> Thanks,
>> Ashen
>>
>> On Wed, Oct 25, 2017 at 5:34 PM, Asela Pathberiya <as...@wso2.com> wrote:
>>
>>>
>>>
>>> On Tue, Oct 24, 2017 at 5:41 PM, Sashika Wijesinghe <sash...@wso2.com>
>>> wrote:
>>>
>>>> Hi All,
>>>>
>>>> We have configured two IS nodes fronted by Nginx and the site.json with
>>>> server host details as below.
>>>>
>>>> {
>>>> "proxy" : {
>>>> "proxyHost" : "is.dev.wso2.org",
>>>> "proxyHTTPSPort" : "443",
>>>> "proxyContextPath" : "",
>>>> "servicePath" : "/services"
>>>> }
>>>> }
>>>>
>>>>
>>>> When I log in to the Management Console with the admin user,
>>>> authentication was successful but failed to login to the IS Dashboard with
>>>> admin user or any user who have permission to the IS Dashboard login.
>>>>
>>>> Following is the authentication exception logged in the terminal.
>>>>
>>>> Any suggestion to solve this issue is highly appreciated.
>>>>
>>>
>>> Don't we have a doc on configuring WSO2IS with Nginx ?
>>>
>>> Thanks,
>>> Asela.
>>>
>>>>
>>>>
>>>> TID: [-1234] [] [2017-10-24 05:28:50,683] ERROR
>>>> {org.wso2.carbon.identity.authenticator.saml2.sso.SAML2SSOAuthenticator}
>>>> - Authentication Request is rejected. SAMLResponse AudienceRestriction
>>>> validation failed.
>>>> TID: [-1] [] [2017-10-24 05:28:50,683] WARN
>>>> {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -
>>>> Failed Administrator login attempt 'admin@carbon.super[-1]' at
>>>> [2017-10-24 05:28:50,683+]
>>>> TID: [-1234] [] [2017-10-24 05:28:50,751] WARN
>>>> {org.wso2.carbon.server.admin.module.handler.AuthenticationHandler} -
>>>> Illegal access attempt at [2017-10-24 05:28:50,0751] from IP address
>>>> 192.168.57.251 while trying to authenticate access to service
>>>> WorkflowImplAdminService
>>>>
>>>> TID: [-1] [] [2017-10-24 05:28:49,939] INFO
>>>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusterMessageListener}
>>>> - Received ClusteringMessage: org.wso2.carbon.identity.entit
>>>> lement.PolicyStatusClusterMessage@d47e9b84
>>>> TID: [-1234] [] [2017-10-24 05:28:50,778] INFO {
>>>> org.apache.axis2.transport.http.HTTPSender} - Unable to sendViaPost
>>>> to url[https://is.dev.wso2.org/services/WorkflowImplAdminServic
>>>> e.WorkflowImplAdminServiceHttpsSoap11Endpoint/]
>>>> org.apache.axis2.AxisFault: Transport error: 401 Error: Unauthorized
>>>> at org.apache.axis2.transport.http.HTTPSender.handleResponse(HT
>>>> TPSender.java:326)
>>>> at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPS
>>>> ender.java:196)
>>>> at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77)
>>>> at org.apache.axis2.transport.http.CommonsHTTPTransportSender.w
>>>> riteMessageWithCommons(CommonsHTTPTransportSender.java:451)
>>>> at org.apache.axis2.transport.http.CommonsHTTPTransportSender.i
>>>> nvoke(CommonsHTTPTransportSender.java:278)
>>>> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
>>>> at org.apache.axis2.description.OutInAxisOperationClient.send(O
>>>> utInAxisOperation.java:430)
>>>> at org.apache.axis2.description.OutInAxisOp
Re: [Dev] How to configure the IS Dashboard for a IS cluster fronted by Nginx
t; at org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(Comp
>> ositeValve.java:62)
>> at org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetection
>> Valve.invoke(CarbonStuckThreadDetectionValve.java:159)
>> at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogVa
>> lve.java:962)
>> at org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.
>> invoke(CarbonContextCreatorValve.java:57)
>> at org.apache.catalina.core.StandardEngineValve.invoke(Standard
>> EngineValve.java:116)
>> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAd
>> apter.java:445)
>> at org.apache.coyote.http11.AbstractHttp11Processor.process(Abs
>> tractHttp11Processor.java:1115)
>> at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler
>> .process(AbstractProtocol.java:637)
>> at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun
>> (NioEndpoint.java:1775)
>> at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(
>> NioEndpoint.java:1734)
>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
>> Executor.java:1142)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
>> lExecutor.java:617)
>> at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.
>> run(TaskThread.java:61)
>> at java.lang.Thread.run(Thread.java:748)
>> TID: [-1234] [] [2017-10-24 05:28:50,782] INFO
>> {JAGGERY.controllers.login-logout.SAML2SSOAuthenticationClient:jag} -
>> JavaException: org.jaggeryjs.scriptengine.exceptions.ScriptException:
>> Transport error: 401 Error: Unauthorized
>>
>> Thank You
>>
>> --
>>
>> *Sashika WijesingheSoftware Engineer - QA Team*
>> Mobile : +94 (0) 774537487
>> sash...@wso2.com
>>
>
>
>
> --
> Thanks & Regards,
> Asela
>
> ATL
> Mobile : +94 777 625 933 <+94%2077%20762%205933>
> +358 449 228 979
>
> http://soasecurity.org/
> http://xacmlinfo.org/
>
--
*Ashen Weerathunga*
Software Engineer
WSO2 Inc.: http://wso2.com
lean.enterprise.middleware
Email: as...@wso2.com
Mobile: +94716042995 <94716042995>
LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga
<http://lk.linkedin.com/in/ashenweerathunga>*
<http://wso2.com/signature>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Identity Server 5.4.0 Alpha Released!
ce - [IDENTITY-6317 <https://wso2.org/jira/browse/IDENTITY-6317>] - Roles(Groups) created from management console doesn't show in SCIM endpoints - [IDENTITY-6322 <https://wso2.org/jira/browse/IDENTITY-6322>] - syntax error on executing identity/postgre.sql - [IDENTITY-6323 <https://wso2.org/jira/browse/IDENTITY-6323>] - [IS]identity oracle dbscripts have errors when executing - [IDENTITY-6330 <https://wso2.org/jira/browse/IDENTITY-6330>] - [IS]When configured secondary jdbc userstore canot login with the secondary userstore user - [IDENTITY-6334 <https://wso2.org/jira/browse/IDENTITY-6334>] - Identity oracle sql script fails due to too long column name Task - [IDENTITY-5182 <https://wso2.org/jira/browse/IDENTITY-5182>] - There are 2 configurations to turn on/off OAuthCache in identity.xml - [IDENTITY-6080 <https://wso2.org/jira/browse/IDENTITY-6080>] - Assertion Consumer URL is not getting set into IS from SP metadata - [IDENTITY-6266 <https://wso2.org/jira/browse/IDENTITY-6266>] - New kernal version upgrade Improvement - [IDENTITY-676 <https://wso2.org/jira/browse/IDENTITY-676>] - [User Management] User Name for Change Password is not shown on the Page - [IDENTITY-2486 <https://wso2.org/jira/browse/IDENTITY-2486>] - There is no way to define the UserInfo endpoint when configuring an OIDC IDP - [IDENTITY-2708 <https://wso2.org/jira/browse/IDENTITY-2708>] - Navigate back from Federated login to local login using browser 'Back' button does not work - [IDENTITY-4441 <https://wso2.org/jira/browse/IDENTITY-4441>] - Cannot change the Assertion Encryption Algorithm for a specific service provider - [IDENTITY-6036 <https://wso2.org/jira/browse/IDENTITY-6036>] - Add "SignJWTWithSPKey" property to identity.xml - [IDENTITY-6081 <https://wso2.org/jira/browse/IDENTITY-6081>] - Need to add separate configuration element in identity.xml for Oauth2 token persistence pool size - [IDENTITY-6127 <https://wso2.org/jira/browse/IDENTITY-6127>] - Add a UI to the expiry time per SP feature - [IDENTITY-6133 <https://wso2.org/jira/browse/IDENTITY-6133>] - Add the self-signed JWT access token issuer - [IDENTITY-6139 <https://wso2.org/jira/browse/IDENTITY-6139>] - Add the functionality to dynamically pick the user token value generator. - [IDENTITY-6151 <https://wso2.org/jira/browse/IDENTITY-6151>] - Improve OAuth/OIDC TokenResponseTypeHandler - [IDENTITY-6178 <https://wso2.org/jira/browse/IDENTITY-6178>] - Add the default values for identity xml - [IDENTITY-6197 <https://wso2.org/jira/browse/IDENTITY-6197>] - Proper error handling for parser errors in application-authentication.xml file - [IDENTITY-6264 <https://wso2.org/jira/browse/IDENTITY-6264>] - Add the facility to customize the introspection URL in Playground application. - [IDENTITY-6283 <https://wso2.org/jira/browse/IDENTITY-6283>] - SAML bearer grant type support for local users after introducing user store domain federated - [IDENTITY-6292 <https://wso2.org/jira/browse/IDENTITY-6292>] - Sign UserInfo JWT Response - [IDENTITY-6298 <https://wso2.org/jira/browse/IDENTITY-6298>] - Make OAuth backward compatible with Federated User store domain - [IDENTITY-6316 <https://wso2.org/jira/browse/IDENTITY-6316>] - Make SAML Encryption Algorithms configurable from SP configuration UI Sub-task - [IDENTITY-4054 <https://wso2.org/jira/browse/IDENTITY-4054>] - [SSO to Travelocity] Authentication Error when Navigated Back from Federated Login to Basic Login and try to authenticate *How To Contribute* Your feedback is most welcome! Mailing Lists Join our mailing list and correspond with the developers directly. - Developer List: dev@wso2.org | Subscribe <dev-requ...@wso2.org> | Mail Archive <http://wso2.org/mailarchive/dev/> - User Forum: StackOverflow <http://stackoverflow.com/questions/tagged/wso2is> Reporting Issues We encourage you to report issues, improvements and feature requests regarding WSO2 Identity Server through public WSO2 Identity Server Runtime JIRA <https://wso2.org/jira/browse/IDENTITY> and Analytics JIRA <https://wso2.org/jira/browse/ANLYIS> *~ The WSO2 Identity Server Team ~* -- *Ashen Weerathunga* Software Engineer WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: +94716042995 <94716042995> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga <http://lk.linkedin.com/in/ashenweerathunga>* <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Regarding the OIDC openid scope in WSO2 IS
On Fri, Aug 11, 2017 at 10:13 AM, Farasath Ahamed <farasa...@wso2.com> wrote: > > > On Friday, August 11, 2017, Omindu Rathnaweera <omi...@wso2.com> wrote: > >> >> >> On Thu, Aug 10, 2017 at 5:15 PM, Hasini Witharana <hasi...@wso2.com> >> wrote: >> >>> Hi, >>> >>> Currently I am working on making WSO2 IS OpenID Connect certified. I ran >>> a test on requesting essential claims from OP, when the scope is openid. It >>> gave an error saying unexpected claims returned. >>> >> >> This is not an error, but a warning correct ? >> >> >>> Then I inquired about this issue through the mailing list of OIDC >>> specifications [1]. I got some information from that as openid scope >>> should only return subject and issuer. >>> >>> IS 5.4.0 is supporting many claims for scope openid. They are : >>> sub,email,email_verified,name, >>> family_name,given_name,middle_name,nickname, >>> preferred_username,profile,pic >>> ture,website,gender,birthdate,zoneinfo,locale, >>> phone_number,phone_number_veri >>> fied,address,street,updated_at >>> >>> I couldn't find In the OIDC specification where it mention that, openid >>> scope should only return subject and issuer. >>> >> >> AFAIK, the spec has not specifically mentioned about what we should >> return for the openid scope and it only mentions about the what should be >> returned for the default 4 scopes. However it is understandable that the >> test client expects a minimum set of claims when having only the openid >> scope. If an RP needs additional claims, it should request them with >> specifying additional scopes and/or essential claims. So I think the >> correct behavior would be to return only a minimal set of claims for the >> openid scope. >> > > Since the spec hasn't specifed this minimal set of claims one can argue > that it is something specific to an RP. This is how our current > implementation works as well. Although we could define a set of claim bound > to the 'openid' scope, the service provider could control what it needs > from the claims bound to openid scope by using requested claims > configuration. > > Changing 'openid' scope to return issuer and sub claims only will be a > breaking change for many existing providers who rely on the additional > claims (some of them could be mandatory in PoV of the RP) > > IMO, if the spec doesn't mandate what should be returned for openid scope > then we can keep our existing implementation as it is. > +1 to keep existing claims if it's not a spec violation. Seems like we have defined all the standerd claims mentioned in the spec [1] under our openid scope implemenation. So if someone need to remove some of claims they can remove it from the oidc configurations in the registry. [1] http://openid.net/specs/openid-connect-core-1_0.html#StandardClaims > >> >>> Can you please help me on this issue? >>> >>> Thank you. >>> >>> >>> [1] - http://lists.openid.net/pipermail/openid-specs/2017-August/s >>> ubject.html >>> >>> -- >>> >>> *Hasini Witharana* >>> Software Engineering Intern | WSO2 >>> >>> >>> *Email : hasi...@wso2.com* >>> >>> *Mobile : +94713850143 <+94%2071%20385%200143>[image: >>> http://wso2.com/signature] <http://wso2.com/signature>* >>> >> >> >> Regards, >> Omindu. >> >> -- >> Omindu Rathnaweera >> Senior Software Engineer, WSO2 Inc. >> Mobile: +94 771 197 211 <+94%2077%20119%207211> >> > > > -- > Farasath Ahamed > Software Engineer, WSO2 Inc.; http://wso2.com > Mobile: +94777603866 > Blog: blog.farazath.com > Twitter: @farazath619 <https://twitter.com/farazath619> > <http://wso2.com/signature> > > > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Ashen Weerathunga* Software Engineer WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: +94716042995 <94716042995> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga <http://lk.linkedin.com/in/ashenweerathunga>* <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Please review and merge the PR
Hi Dilan, I have done the changes and successfully build the component and kernel with the tests. Thanks, Ashen On Fri, Aug 11, 2017 at 8:09 AM, Dilan Udara Ariyaratne <dil...@wso2.com> wrote: > Hi Ashen, > > Added Few more suggestions. Please go through and verify. > > Thanks, > Dilan. > > *Dilan U. Ariyaratne* > Senior Software Engineer > WSO2 Inc. <http://wso2.com/> > Mobile: +94766405580 <%2B94766405580> > lean . enterprise . middleware > > > On Thu, Aug 10, 2017 at 7:23 PM, Ashen Weerathunga <as...@wso2.com> wrote: > >> Hi Dilan, >> >> I have done the requested changes and updated the PR. >> >> Thanks, >> Ashen >> >> On Thu, Aug 10, 2017 at 6:23 AM, Dilan Udara Ariyaratne <dil...@wso2.com> >> wrote: >> >>> Hi Ashen, >>> >>> Went through the code and added few comments, Please go through and >>> verify. >>> >>> Thanks, >>> Dilan. >>> >>> *Dilan U. Ariyaratne* >>> Senior Software Engineer >>> WSO2 Inc. <http://wso2.com/> >>> Mobile: +94766405580 <%2B94766405580> >>> lean . enterprise . middleware >>> >>> >>> On Wed, Aug 9, 2017 at 1:44 PM, Ashen Weerathunga <as...@wso2.com> >>> wrote: >>> >>>> Hi, >>>> >>>> Can you please review and merge the PR [1]. This is regarding the Issue >>>> [2]. >>>> >>>> [1] https://github.com/wso2/carbon-kernel/pull/1464 >>>> [2] https://github.com/wso2/carbon-kernel/issues/1467 >>>> >>>> >>>> Thanks, >>>> Ashen >>>> -- >>>> *Ashen Weerathunga* >>>> Software Engineer >>>> WSO2 Inc.: http://wso2.com >>>> lean.enterprise.middleware >>>> >>>> Email: as...@wso2.com >>>> Mobile: +94716042995 <94716042995> >>>> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga >>>> <http://lk.linkedin.com/in/ashenweerathunga>* >>>> <http://wso2.com/signature> >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >> >> >> -- >> *Ashen Weerathunga* >> Software Engineer >> WSO2 Inc.: http://wso2.com >> lean.enterprise.middleware >> >> Email: as...@wso2.com >> Mobile: +94716042995 <94716042995> >> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga >> <http://lk.linkedin.com/in/ashenweerathunga>* >> <http://wso2.com/signature> >> > > -- *Ashen Weerathunga* Software Engineer WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: +94716042995 <94716042995> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga <http://lk.linkedin.com/in/ashenweerathunga>* <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Please review and merge the PR
Hi Dilan, I have done the requested changes and updated the PR. Thanks, Ashen On Thu, Aug 10, 2017 at 6:23 AM, Dilan Udara Ariyaratne <dil...@wso2.com> wrote: > Hi Ashen, > > Went through the code and added few comments, Please go through and verify. > > Thanks, > Dilan. > > *Dilan U. Ariyaratne* > Senior Software Engineer > WSO2 Inc. <http://wso2.com/> > Mobile: +94766405580 <%2B94766405580> > lean . enterprise . middleware > > > On Wed, Aug 9, 2017 at 1:44 PM, Ashen Weerathunga <as...@wso2.com> wrote: > >> Hi, >> >> Can you please review and merge the PR [1]. This is regarding the Issue >> [2]. >> >> [1] https://github.com/wso2/carbon-kernel/pull/1464 >> [2] https://github.com/wso2/carbon-kernel/issues/1467 >> >> >> Thanks, >> Ashen >> -- >> *Ashen Weerathunga* >> Software Engineer >> WSO2 Inc.: http://wso2.com >> lean.enterprise.middleware >> >> Email: as...@wso2.com >> Mobile: +94716042995 <94716042995> >> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga >> <http://lk.linkedin.com/in/ashenweerathunga>* >> <http://wso2.com/signature> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > -- *Ashen Weerathunga* Software Engineer WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: +94716042995 <94716042995> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga <http://lk.linkedin.com/in/ashenweerathunga>* <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Please review and merge the PR
Hi, Can you please review and merge the PR [1]. This is regarding the Issue [2]. [1] https://github.com/wso2/carbon-kernel/pull/1464 [2] https://github.com/wso2/carbon-kernel/issues/1467 Thanks, Ashen -- *Ashen Weerathunga* Software Engineer WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: +94716042995 <94716042995> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga <http://lk.linkedin.com/in/ashenweerathunga>* <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Markov extension is not filtering events properly with DAS-3.1.0
Hi Banu/Seshi, Actually, it's the expected behavior of this extension. According to the parameters you have provided in the above example, after 12 events, it will start triggering output events. All the input data will be used to update Markov matrix continuously while giving the outputs. There is an output parameter called 'notify' [1]. It will give the notification (true/false) if a particular event has a transition probability less than the given threshold (0.5 in this case). You can use that parameter to distinguish output events based on your requirement. Hope you will be able to meet your requirement by modifying the above query as below, from markovStream#markov:markovChain(id, state, 60 min, 0.5, 12, true) select txnid, id as cardnum, txnamt, currency, email, shippingaddress, billingaddress, ip, itemNo, qty, timestamp, 0.0 as score, 100 as fraudflag, transitionProbability as transitionProbability, notify having notify == true insert into FraudStream; [1] https://docs.wso2.com/display/CEP420/Markov+Models+Extension#319133f154a64f9bb1f2df7f2057a602 Thanks, Ashen On Tue, Apr 25, 2017 at 2:26 PM, Seshika Fernando <sesh...@wso2.com> wrote: > So to give bit more context, ideally the function should output only > events that have transition probability less than the given threshold (0.5 > in this case). > > But now the output contains events that have transition probability more > than the given threshold. > > On Tue, Apr 25, 2017 at 1:17 PM, Banu Nissanka <b...@wso2.com> wrote: > >> >> -- Forwarded message -- >> From: Banu Nissanka <b...@wso2.com> >> Date: Tue, Apr 25, 2017 at 1:12 PM >> Subject: Markov extension is not filtering events properly with DAS-3.1.0 >> To: Sriskandarajah Suhothayan <s...@ws02.com>, Mohanadarshan >> Vivekanandalingam <mo...@wso2.com> >> Cc: Seshika Fernando <sesh...@wso2.com> >> >> >> Hi, >> Im working on fraud detection setup and Im using the following markov >> extention with it. >> >> from markovStream#markov:markovChain(id, state, 60 min, 0.5, 12, true) >> select txnid,id as cardnum, txnamt,currency,email, shippingaddress, >> billingaddress, ip,itemNo, qty,timestamp,0.0 as score, 100 as fraudflag, >> transitionProbability as transitionProbability >> insert into FraudStream; >> >> But this not perform filtering properly, outputs events which has >> transitionProbability >> greater than 0.5 as well. >> >> Thanks, >> >> -- >> >> >> *Banu Nissanka* >> Email : b...@wso2.com >> Mobile : +94713151493 <+94%2071%20315%201493> >> Web : https://wso2.com/signature <http://wso2.com/signature> >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "WSO2 Engineering Group" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to engineering-group+unsubscr...@wso2.com. >> For more options, visit https://groups.google.com/a/wso2.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "WSO2 Engineering Group" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to engineering-group+unsubscr...@wso2.com. > For more options, visit https://groups.google.com/a/wso2.com/d/optout. > -- *Ashen Weerathunga* Software Engineer WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: +94716042995 <94716042995> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga <http://lk.linkedin.com/in/ashenweerathunga>* <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Please review and merge the PR
On Tue, Feb 21, 2017 at 6:03 PM, Ashen Weerathunga <as...@wso2.com> wrote: > Hi, > > Can you please review and merge the PR [1]. This is regarding the kernel > update requested in this mail thread [2]. > > [1] https://github.com/wso2/carbon-messaging/pull/57 > [2] [IS-6.0] Updating carbon-kernel version to 5.2.0-m3 > > Thanks, > Ashen > > -- > *Ashen Weerathunga* > Software Engineer > WSO2 Inc.: http://wso2.com > lean.enterprise.middleware > > Email: as...@wso2.com > Mobile: +94716042995 <94716042995> > LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga > <http://lk.linkedin.com/in/ashenweerathunga>* > <http://wso2.com/signature> > -- *Ashen Weerathunga* Software Engineer WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: +94716042995 <94716042995> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga <http://lk.linkedin.com/in/ashenweerathunga>* <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Please review and merge the PR
Hi all, Can you please review and merge the PR [1]. This is regarding the kernel update requested in this mail thread [2]. [1] https://github.com/wso2/carbon-jndi/pull/33 [2] [IS-6.0] Updating carbon-kernel version to 5.2.0-m3 Thanks, Ashen -- *Ashen Weerathunga* Software Engineer WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: +94716042995 <94716042995> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga <http://lk.linkedin.com/in/ashenweerathunga>* <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] STS Client sample Doesn't work for Non-repudiation
Hi Hasintha, Thanks for providing the solution. It worked fine after changing the *path.policy.sts* property to *sts-policy-signonly.xml *in the client.properties file. In the default sample it was sts-policy-ut.xml. Even though it worked for UsernameToken scenario, it needs to be changed for Non-repudiation scenario. I think it's better if we can mention it in the docs clearly. I created a doc Jira to track it [1]. [1] https://wso2.org/jira/browse/DOCUMENTATION-4150 Thanks, Ashen On Mon, Jan 16, 2017 at 9:33 PM, Hasintha Indrajee <hasin...@wso2.com> wrote: > Hi Ashen, > > Few things you need to pay attention while getting this client working. > > 1) As [1] suggests you need to generate a new key pair in client's key > store for user. The existing keys in the sample are expired. Therefore > please use a new key store and add a new key pair in order to get this > working. Also you need to import the public certificate of the particular > user to IS key store as described in [1] > > 2) You need to configure correct policy in client (client.properties file) > ie you need to uncomment following and comment the existing policy ( > sts-policy-ut.xml) > path.policy.sts=sts-policy-signonly.xml > > After uncommenting please build the sample and try the scenario. It should > be working properly once you follow these steps. > > [1] https://docs.wso2.com/display/IS510/Accessing+Claim+ > Aware+Services+using+STS+Secured+with+Non-repudiation > > > On Mon, Jan 16, 2017 at 7:11 PM, Ashen Weerathunga <as...@wso2.com> wrote: > >> Hi, >> >> I also tried the STS client with non-repudiation. But gives the following >> error. Is there any configs need to be changed in the sample? >> >> org.apache.rahas.TrustException: Error in obtaining token from : " >> https://localhost:9443/services/wso2carbon-sts; >> at org.apache.rahas.client.STSClient.requestSecurityToken(STSCl >> ient.java:174) >> at org.apache.rahas.client.STSClient.requestSecurityToken(STSCl >> ient.java:182) >> at org.wso2.carbon.identity.samples.sts.Client.run(Client.java:130) >> at org.wso2.carbon.identity.samples.sts.Client.main(Client.java:94) >> Caused by: org.apache.axis2.AxisFault: Must Understand check failed for >> header http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wsse >> curity-secext-1.0.xsd : Security >> at org.apache.axis2.engine.AxisEngine.checkMustUnderstand(AxisE >> ngine.java:105) >> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:171) >> at org.apache.axis2.description.OutInAxisOperationClient.handle >> Response(OutInAxisOperation.java:364) >> at org.apache.axis2.description.OutInAxisOperationClient.send(O >> utInAxisOperation.java:421) >> at org.apache.axis2.description.OutInAxisOperationClient.execut >> eImpl(OutInAxisOperation.java:229) >> at org.apache.axis2.client.OperationClient.execute(OperationCli >> ent.java:165) >> at org.apache.axis2.client.ServiceClient.sendReceive(ServiceCli >> ent.java:555) >> at org.apache.rahas.client.STSClient.requestSecurityToken(STSCl >> ient.java:165) >> ... 3 more >> >> Thanks, >> Ashen >> >> On Fri, Jan 6, 2017 at 12:12 AM, Gayan Gunawardana <ga...@wso2.com> >> wrote: >> >>> Steps and sample can be found from [1],[2]. Issue seems to be a problem >>> of default keystore. When I trace the request and response from tcpmon >>> found below issue. >>> >>> >>> *Request* >>> >>>http://www.w3.o >>> rg/2003/05/soap-envelope"> >>> http://schemas.xmls >>> oap.org/ws/2004/08/addressing"> >>> http://docs.oasis- >>> open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" >>> soapenv:mustUnderstand="true"> >>> http://docs.oasis-o >>> pen.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" >>> wsu:Id="Timestamp-1"> >>>2017-01-05T08:35:31.570Z >>>2017-01-05T08:40:31.570Z >>> >>> http://docs.oasis-o >>> pen.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" >>> EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-2 >>> 00401-wss-soap-message-security-1.0#Base64Binary" ValueType=" >>> http://docs.oasis-open.org/wss/2004/01/oasis-2004 >>> 01-wss-x509-token-profile-1.0#X509v3" wsu:Id="CertId-F1F5AE821BB8A9B >>> 28714836053316591">MIIBlzCCAQCgAwIBAgIEUVqxuDANBgkqhkiG9w0BA >>> QUFADAQMQ4wDAYDVQQDEwVhZG1pbjAe
Re: [Dev] STS Client sample Doesn't work for Non-repudiation
> http://schemas.xmlsoap.org/ws/2004/08/ > addressing/role/anonymous > > urn:uuid:c514e93f-6a96-4640-8304- > 400320f95d5a > http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Issue > > > http://docs.oasis- > open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" > wsu:Id="Id-100433527"> > http://schemas. > xmlsoap.org/ws/2005/02/trust"> > http://schemas.xmlsoap.org/ws/2005/ > 02/trust/Issue > http://schemas. > xmlsoap.org/ws/2004/09/policy"> >http://schemas. > xmlsoap.org/ws/2004/08/addressing"> > https://localhost:10443/services/echo< > /wsa:Address> > > > >2017-01-05T08:35:31.256Z >2017-01-05T08:40:31.256Z > > http://docs.oasis-open.org/wss/oasis-wss- > saml-token-profile-1.1#SAMLV2.0 > http://schemas.xmlsoap.org/ws/2005/02/trust/ > Bearer > http://schemas. > xmlsoap.org/ws/2005/02/trust" wsp:Dialect="http://wso2.org/claims;> >http://schemas. > xmlsoap.org/ws/2005/05/identity" Uri="http://wso2.org/claims/givenname; /> >http://schemas. > xmlsoap.org/ws/2005/05/identity" Uri="http://wso2.org/claims/emailaddress; > /> > > > > > > > > *Response * >http://www.w3. > org/2003/05/soap-envelope"> > http://schemas.xmlsoap.org/ws/2004/08/ > addressing"> > http://docs.oasis- > open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" > soapenv:mustUnderstand="true"> > http://docs.oasis- > open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" > wsu:Id="Timestamp-11"> >2017-01-05T08:35:31.867Z >2017-01-05T08:40:31.867Z > > http://www.w3.org/2000/09/xmldsig#; > Id="Signature-12"> > > http://www.w3.org/ > 2001/10/xml-exc-c14n#"/> > http://www.w3.org/ > 2000/09/xmldsig#rsa-sha1"/> > > > http://www.w3.org/ > 2001/10/xml-exc-c14n#"/> > > http://www.w3.org/ > 2000/09/xmldsig#sha1"/> > h5oo0fYSZXjhsCDyzJF2XFTbjEg= ds:DigestValue> > > > > http://www.w3.org/ > 2001/10/xml-exc-c14n#"/> > > http://www.w3.org/ > 2000/09/xmldsig#sha1"/> > 0SnksGqgO8yrwWLuJUUEw52habw= ds:DigestValue> > > >Pzwh9XSrKLMpze42EcGfYZweb+ > Th4FxX4rRt2+axHQRlt/p+A8YMwYUicKF93+a7RDiOhOdUOaoanIoN/CQaYtSskQZzK+ > LaqP9o1kcJCLulPgkGeYiC/fb3AilOuKKS+s5JWMchfgw2ebLgYTO43AalYwCtqNf > /VMycIpb30B4= > > http://docs.oasis-open.org/wss/2004/01/oasis- > 200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="STRId- > 649751EC57E04F21D3148360533186918"> > http://docs. > oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message- > security-1.0#Base64Binary" ValueType="http://docs.oasis- > open.org/wss/oasis-wss-soap-message-security-1.1#ThumbprintSHA1">a/ > jhNus21KVuoFx65LmkW2O/l10= > > > > > http://schemas.xmlsoap.org/ws/2004/08/ > addressing/role/anonymous > urn:uuid:8904e3e1-9aea-4271-bac1- > c99c52ce641f > http://schemas.xmlsoap.org/ws/2004/08/ > addressing/fault > urn:uuid:c514e93f-6a96-4640-8304- > 400320f95d5a > > http://docs.oasis- > open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" > wsu:Id="Id-1962192193"> > http://www. > w3.org/2003/05/soap-envelope"> > >axis2ns11:Sender > > http://docs. > oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd > ">axis2ns12:FailedCheck > > > >The signature or decryption > was invalid (The provided certificate is invalid); nested exception is: > java.security.cert.CertificateExpiredException: NotAfter: Mon Jul 01 > 15:53:52 IST 2013 > 11 > 32 >
Re: [Dev] [VOTE] Release WSO2 Identity Server 5.3.0- RC3
Hi, Tested the following IS Analytics features with IS Runtime, - Login attempts analytics - Login session analytics - Suspicious login alerts - Customizing alerts using template manager [+] Stable - go ahead and release Thanks, Ashen On Mon, Jan 9, 2017 at 11:51 AM, Thanuja Jayasinghe <than...@wso2.com> wrote: > Hi, > > Tested following, > >- Account recovery with notification >- Account recovery with security questions >- Recaptcha >- Self signup > > [+] Stable - go ahead and release > > Thanks, > Thanuja > > On Mon, Jan 9, 2017 at 11:05 AM, Rushmin Fernando <rush...@wso2.com> > wrote: > >> Tested following features with MSSQL >> >> 1) SAML flow >> 2) OAuth >> 3) OIDC >> 4) SAML metedata profile >> >> [+] Stable - go ahead and release >> >> Best Regards >> Rushmin >> >> On Mon, Jan 9, 2017 at 9:33 AM, Dinali Dabarera <din...@wso2.com> wrote: >> >>> Hi, >>> I tested the following on the Identity Server 5.3.0-RC3 pack, >>> >>>- Discovery >>>- DCR >>>- Form Post >>>- Introspection >>>- SCIM API >>>- User Management >>> >>> Worked fine without any issues. >>> [+] Stable - go ahead and release >>> >>> On Fri, Jan 6, 2017 at 10:06 PM, Pulasthi Mahawithana < >>> pulast...@wso2.com> wrote: >>> >>>> Hi All, >>>> >>>> This is the 3rd Release Candidate of WSO2 Identity Server 5.3.0. >>>> >>>> Please download, test the product and vote. Vote will be open for 72 >>>> hours or as needed. >>>> >>>> This release fixes the following issues: >>>> >>>> Runtime : https://wso2.org/jira/issues/?filter=13612 >>>> Analytics : https://wso2.org/jira/issues/?filter=13614 >>>> >>>> Source and distribution >>>> >>>> Run-time : https://github.com/wso2/prod >>>> uct-is/releases/tag/v5.3.0-rc3 >>>> Analytics : https://github.com/wso2/anal >>>> ytics-is/releases/tag/v5.3.0-rc3 >>>> >>>> Please vote as follows. >>>> [+] Stable - go ahead and release >>>> [-] Broken - do not release (explain why) >>>> >>>> Thanks, >>>> - WSO2 Identity Server Team - >>>> >>>> -- >>>> *Pulasthi Mahawithana* >>>> Senior Software Engineer >>>> WSO2 Inc., http://wso2.com/ >>>> Mobile: +94-71-5179022 <+94%2071%20517%209022> >>>> Blog: http://blog.pulasthi.org >>>> >>>> <https://wso2.com/signature> >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> *Dinali Rosemin Dabarera* >>> Software Engineer >>> WSO2 Lanka (pvt) Ltd. >>> Web: http://wso2.com/ >>> Email : gdrdabar...@gmail.com >>> LinkedIn <https://lk.linkedin.com/in/dinalidabarera> >>> Mobile: +94770198933 <+94%2077%20019%208933> >>> >>> >>> >>> >>> <https://lk.linkedin.com/in/dinalidabarera> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Best Regards* >> >> *Rushmin Fernando* >> *Technical Lead* >> >> WSO2 Inc. <http://wso2.com/> - Lean . Enterprise . Middleware >> >> mobile : +94775615183 >> >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Thanuja Lakmal* > Senior Software Engineer > WSO2 Inc. http://wso2.com/ > *lean.enterprise.middleware* > Mobile: +94715979891 +94758009992 > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Ashen Weerathunga* Software Engineer WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: tel:94716042995 <94716042995> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga <http://lk.linkedin.com/in/ashenweerathunga>* <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Sajith Perera
Congratulations Sajith!!! On Thu, Jan 5, 2017 at 10:49 AM, Maneesha Wijesekara <manee...@wso2.com> wrote: > Congratulations Sajith..!! > > On Thu, Jan 5, 2017 at 10:41 AM, Sajith Ravindra <saji...@wso2.com> wrote: > >> Congratz Sajith!!! >> >> Thanks >> *,Sajith Ravindra* >> Senior Software Engineer >> WSO2 Inc.; http://wso2.com >> lean.enterprise.middleware >> >> mobile: +94 77 2273550 >> blog: http://sajithr.blogspot.com/ >> <http://lk.linkedin.com/pub/shani-ranasinghe/34/111/ab> >> >> On Thu, Jan 5, 2017 at 8:32 AM, Mohanadarshan Vivekanandalingam < >> mo...@wso2.com> wrote: >> >>> Hi Devs, >>> >>> It is my pleasure to welcome Sajith Perera as a WSO2 Committer. Sajith >>> has been a valuable contributor in WSO2 analytics space and performed >>> enormous tasks on CEP tooling, CEP HA and Log Analyzer. >>> >>> SajithD, welcome aboard and keep up the good work. >>> >>> >>> Thanks, >>> Mohan >>> >>> >>> -- >>> *V. Mohanadarshan* >>> *Associate Tech Lead,* >>> *Data Technologies Team,* >>> *WSO2, Inc. http://wso2.com <http://wso2.com> * >>> *lean.enterprise.middleware.* >>> >>> email: mo...@wso2.com >>> phone:(+94) 771117673 <+94%2077%20111%207673> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Maneesha Wijesekara > Software Engineer - EE Team > WSO2 Inc. > > Email: manee...@wso2.com > Linkedin: http://linkedin.com/in/maneeshawijesekara > Mobile: +94712443119 > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Ashen Weerathunga* Software Engineer WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: tel:94716042995 <94716042995> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga <http://lk.linkedin.com/in/ashenweerathunga>* <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [APIM][Analytics] Issue in the default templated spark scripts
Hi, There is an issue in the default templated spark scripts available in the API manager analytics. I have noticed this issue with spark scripts scheduling. API manager analytics provides some default templates for every scenario. Therefore the user can configure some parameters using template manager or they can use default templates without configuring it. But those default spark scripts are not scheduling according to the provided cron expressions. Seems like those scripts are not added to the carbon tasks in the registry. Hence they never execute although they are supposed to be executed based on crons. Therefore if a user decided to go with a default template of a particular scenario wich includes a spark script, that won't work as expected. Best regards, Ashen -- *Ashen Weerathunga* Software Engineer WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: tel:94716042995 <94716042995> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga <http://lk.linkedin.com/in/ashenweerathunga>* <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Siddhi] [Markov Models Extension] What is the stored location of trained Markov matrices?
Hi Bhashinee, You can find the source code from here[1]. [1] https://github.com/wso2/siddhi/tree/master/modules/siddhi-extensions/markov-models Best Regards, Ashen On Wed, Oct 19, 2016 at 3:09 PM, Bhashinee Nirmali <bhashin...@gmail.com> wrote: > Hi All, > > Thank you for the information. I would like to study more about this. Can > you please point me to the source code of Markov model extension? > > Thanks > > On Tue, Oct 18, 2016 at 1:47 AM, Ashen Weerathunga <as...@wso2.com> wrote: > >> Hi Tishan, >> >> We don't have any non-serializable objects and we are currently using CEP >> persistence option to persist the state of Markov extension. But currently, >> we cannot export the Markov matrix separately as a csv. Therefore the >> Markov matrix generated by the extension cannot be used externally IMO. >> >> Thanks, >> Ashen >> >> On Tue, Oct 18, 2016 at 12:45 PM, Tishan Dahanayakage <tis...@wso2.com> >> wrote: >> >>> Ashen, >>> >>> Can't we use CEP persistence option to persist the state of Markov >>> extension to file system and re-use? Do we have any non-serializable >>> objects? >>> >>> /Tishan >>> >>> On Tue, Oct 18, 2016 at 12:28 PM, Ashen Weerathunga <as...@wso2.com> >>> wrote: >>> >>>> Hi Bhashinee, >>>> >>>> In the current implementation, we are storing the Markov matrix using a >>>> hashmap. Therefore if you shut down the server it won't be persisted. But >>>> we have provided a facility to input an already built Markov matrix as a >>>> CSV file. So in such case, you can use that option to input the matrix >>>> again and start training. Please refer docs[1] for more details. >>>> >>>> [1]https://docs.wso2.com/pages/viewpage.action?pageId=56993859 >>>> >>>> Best regards, >>>> Ashen >>>> >>>> >>>> On Tue, Oct 18, 2016 at 10:08 AM, Bhashinee Nirmali < >>>> bhashin...@gmail.com> wrote: >>>> >>>>> Hi All, >>>>> >>>>> I'm trying the Markov Models Extension of WSO2 CEP. I need to know the >>>>> location where the newly built matrices are stored in. And do I need to >>>>> built the matrix again after shutting down the CEP or is the created >>>>> matrix >>>>> still there in the memory? >>>>> >>>>> Thanks >>>>> >>>>> Undergraduate >>>>> Faculty of Information Technology >>>>> University of Moratuwa >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Ashen Weerathunga* >>>> Software Engineer >>>> WSO2 Inc.: http://wso2.com >>>> lean.enterprise.middleware >>>> >>>> Email: as...@wso2.com >>>> Mobile: tel:94716042995 <94716042995> >>>> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga >>>> <http://lk.linkedin.com/in/ashenweerathunga>* >>>> <http://wso2.com/signature> >>>> >>>> _______ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Tishan Dahanayakage >>> Senior Software Engineer >>> WSO2, Inc. >>> Mobile:+94 716481328 >>> >>> 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, re-transmit, 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. >>> >> >> >> >> -- >> *Ashen Weerathunga* >> Software Engineer >> WSO2 Inc.: http://wso2.com >> lean.enterprise.middleware >> >> Email: as...@wso2.com >> Mobile: tel:94716042995 <94716042995> >> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga >> <http://lk.linkedin.com/in/ashenweerathunga>* >> <http://wso2.com/signature> >> > > > > -- > Undergraduate > Faculty of Information Technology > University of Moratuwa > -- *Ashen Weerathunga* Software Engineer WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: tel:94716042995 <94716042995> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga <http://lk.linkedin.com/in/ashenweerathunga>* <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Siddhi] [Markov Models Extension] What is the stored location of trained Markov matrices?
Hi Tishan, We don't have any non-serializable objects and we are currently using CEP persistence option to persist the state of Markov extension. But currently, we cannot export the Markov matrix separately as a csv. Therefore the Markov matrix generated by the extension cannot be used externally IMO. Thanks, Ashen On Tue, Oct 18, 2016 at 12:45 PM, Tishan Dahanayakage <tis...@wso2.com> wrote: > Ashen, > > Can't we use CEP persistence option to persist the state of Markov > extension to file system and re-use? Do we have any non-serializable > objects? > > /Tishan > > On Tue, Oct 18, 2016 at 12:28 PM, Ashen Weerathunga <as...@wso2.com> > wrote: > >> Hi Bhashinee, >> >> In the current implementation, we are storing the Markov matrix using a >> hashmap. Therefore if you shut down the server it won't be persisted. But >> we have provided a facility to input an already built Markov matrix as a >> CSV file. So in such case, you can use that option to input the matrix >> again and start training. Please refer docs[1] for more details. >> >> [1]https://docs.wso2.com/pages/viewpage.action?pageId=56993859 >> >> Best regards, >> Ashen >> >> >> On Tue, Oct 18, 2016 at 10:08 AM, Bhashinee Nirmali <bhashin...@gmail.com >> > wrote: >> >>> Hi All, >>> >>> I'm trying the Markov Models Extension of WSO2 CEP. I need to know the >>> location where the newly built matrices are stored in. And do I need to >>> built the matrix again after shutting down the CEP or is the created matrix >>> still there in the memory? >>> >>> Thanks >>> >>> Undergraduate >>> Faculty of Information Technology >>> University of Moratuwa >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Ashen Weerathunga* >> Software Engineer >> WSO2 Inc.: http://wso2.com >> lean.enterprise.middleware >> >> Email: as...@wso2.com >> Mobile: tel:94716042995 <94716042995> >> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga >> <http://lk.linkedin.com/in/ashenweerathunga>* >> <http://wso2.com/signature> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Tishan Dahanayakage > Senior Software Engineer > WSO2, Inc. > Mobile:+94 716481328 > > 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, re-transmit, 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. > -- *Ashen Weerathunga* Software Engineer WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: tel:94716042995 <94716042995> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga <http://lk.linkedin.com/in/ashenweerathunga>* <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Siddhi] [Markov Models Extension] What is the stored location of trained Markov matrices?
Hi Bhashinee, In the current implementation, we are storing the Markov matrix using a hashmap. Therefore if you shut down the server it won't be persisted. But we have provided a facility to input an already built Markov matrix as a CSV file. So in such case, you can use that option to input the matrix again and start training. Please refer docs[1] for more details. [1]https://docs.wso2.com/pages/viewpage.action?pageId=56993859 Best regards, Ashen On Tue, Oct 18, 2016 at 10:08 AM, Bhashinee Nirmali <bhashin...@gmail.com> wrote: > Hi All, > > I'm trying the Markov Models Extension of WSO2 CEP. I need to know the > location where the newly built matrices are stored in. And do I need to > built the matrix again after shutting down the CEP or is the created matrix > still there in the memory? > > Thanks > > Undergraduate > Faculty of Information Technology > University of Moratuwa > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Ashen Weerathunga* Software Engineer WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: tel:94716042995 <94716042995> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga <http://lk.linkedin.com/in/ashenweerathunga>* <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Ashen Weerathunga
Thanks everyone!!! :) On Wed, Oct 5, 2016 at 5:50 PM, Lahiru Manohara <lahir...@wso2.com> wrote: > Hi Ashen, > > Congratulations ..!!! > > On Tue, Oct 4, 2016 at 4:37 PM, Charini Nanayakkara <chari...@wso2.com> > wrote: > >> Congrats Ashen! :) >> >> On Tue, Oct 4, 2016 at 3:56 PM, Mushthaq Rumy <musht...@wso2.com> wrote: >> >>> Congrats Ashen! >>> >>> Thanks & Regards, >>> Mushthaq >>> >>> On Tue, Oct 4, 2016 at 2:39 PM, Sameera Ramasinghe <samee...@wso2.com> >>> wrote: >>> >>>> Congratz Ashen!! >>>> >>>> On Tue, Oct 4, 2016 at 1:56 PM, Grainier Perera <grain...@wso2.com> >>>> wrote: >>>> >>>>> Congratulations Ashen.! >>>>> >>>>> On Tue, Oct 4, 2016 at 11:03 AM, Nirmal Fernando <nir...@wso2.com> >>>>> wrote: >>>>> >>>>>> Hi all, >>>>>> >>>>>> It is my pleasure to welcome Ashen Weerathunga as a WSO2 Committer. >>>>>> In recognition of Ashen's contributions to ML, Siddhi and IoT analytics, >>>>>> he >>>>>> has been voted as a Committer. >>>>>> >>>>>> Ashen, welcome aboard and keep up the good work. >>>>>> >>>>>> -- >>>>>> >>>>>> Thanks & regards, >>>>>> Nirmal >>>>>> >>>>>> Team Lead - WSO2 Machine Learner >>>>>> Associate Technical Lead - Data Technologies Team, WSO2 Inc. >>>>>> Mobile: +94715779733 >>>>>> Blog: http://nirmalfdo.blogspot.com/ >>>>>> >>>>>> >>>>>> >>>>>> ___ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Grainier Perera >>>>> Software Engineer >>>>> Mobile : +94716122384 >>>>> WSO2 Inc. | http://wso2.com >>>>> lean.enterprise.middleware >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Sameera Ramasinghe* >>>> Software Engineer, WSO2 Inc.; http://wso2.com >>>> mobile: *+94 714489682* >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Mushthaq Rumy >>> *Software Engineer* >>> Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194> >>> Email : musht...@wso2.com >>> WSO2, Inc.; http://wso2.com/ >>> lean . enterprise . middleware. >>> >>> <http://wso2.com/signature> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Charini Vimansha Nanayakkara* >> Software Engineer at WSO2 >> >> Mobile: 0714126293 >> E-mail: chari...@wso2.com >> Blog: http://www.charini.me/ >> >> <http://wso2.com/signature> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Lahiru Manohara* > *Software Engineer* > Mobile: +94716561576 > WSO2 Inc. | http://wso2.com > lean.enterprise.middleware > -- *Ashen Weerathunga* Software Engineer WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: tel:94716042995 <94716042995> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga <http://lk.linkedin.com/in/ashenweerathunga>* <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Vote] Release WSO2 Complex Event Processor (CEP) 4.2.0-RC2
t; Extension for calculate percentile values >>>>>>> [CEP-1510 <https://wso2.org/jira/browse/CEP-1510>] - External Time >>>>>>> Batch Window Implementation >>>>>>> [CEP-1511 <https://wso2.org/jira/browse/CEP-1511>] - Template >>>>>>> Manager support for other deployable artifacts >>>>>>> [CEP-1512 <https://wso2.org/jira/browse/CEP-1512>] - MaxForever and >>>>>>> MinForever Attribute Aggregators for Siddhi >>>>>>> [CEP-1514 <https://wso2.org/jira/browse/CEP-1514>] - Make >>>>>>> Distruptor as configurable in Siddhi >>>>>>> [CEP-1515 <https://wso2.org/jira/browse/CEP-1515>] - RDBMS event >>>>>>> table does not work with new RDBMS database types >>>>>>> [CEP-1516 <https://wso2.org/jira/browse/CEP-1516>] - Distinct >>>>>>> Attribute Aggretaor for Siddhi >>>>>>> [CEP-1517 <https://wso2.org/jira/browse/CEP-1517>] - Split Function >>>>>>> for String Siddhi Extension >>>>>>> [CEP-1520 <https://wso2.org/jira/browse/CEP-1520>] - Necessary >>>>>>> improvement to ExternalTimeBatch window >>>>>>> [CEP-1526 <https://wso2.org/jira/browse/CEP-1526>] - Improve event >>>>>>> receiver/publisher JMS configuration to support Tibco EMS >>>>>>> [CEP-1528 <https://wso2.org/jira/browse/CEP-1528>] - Provide >>>>>>> support for string values to be used in line charts x axis in real time >>>>>>> gadets >>>>>>> [CEP-1532 <https://wso2.org/jira/browse/CEP-1532>] - Add basicAuth >>>>>>> enable property for http event receiver >>>>>>> [CEP-1540 <https://wso2.org/jira/browse/CEP-1540>] - [Template >>>>>>> Manager UI] JSP pages which are not invoked through Ajax are named as >>>>>>> *_ajaxprocessor.jsp >>>>>>> [CEP-1574 <https://wso2.org/jira/browse/CEP-1574>] - JNDI Connector >>>>>>> to Sonic MQ. >>>>>>> >>>>>>> >>>>>>> *Fixed Issues in This Release* >>>>>>> >>>>>>>- Bug Fixes <https://wso2.org/jira/browse/CEP-1570?filter=13164> >>>>>>> >>>>>>> *Known Issues* >>>>>>> >>>>>>>- Known Issues >>>>>>><https://wso2.org/jira/browse/CEP-256?filter=13165> >>>>>>> >>>>>>> *Source and distribution packages:* >>>>>>> >>>>>>>- >>>>>>> *https://github.com/wso2/product-cep/releases/download/v4.2.0-rc2/wso2cep-4.2.0-RC2.zip >>>>>>> >>>>>>> <https://github.com/wso2/product-cep/releases/download/v4.2.0-rc2/wso2cep-4.2.0-RC2.zip>* >>>>>>> >>>>>>> >>>>>>> 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. Regards, >>>>>>> WSO2 CEP Team >>>>>>> >>>>>>> ___ >>>>>>> Dev mailing list >>>>>>> Dev@wso2.org >>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> Tharindu Edirisinghe >>>>>> Senior Software Engineer | WSO2 Inc >>>>>> Platform Security Team >>>>>> Blog : tharindue.blogspot.com >>>>>> mobile : +94 775181586 >>>>>> >>>>>> ___ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Tishan Dahanayakage >>>>> Senior Software Engineer >>>>> WSO2, Inc. >>>>> Mobile:+94 716481328 >>>>> >>>>> 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, re-transmit, 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. >>>>> >>>> >>>> >>>> >>>> -- >>>> Pamoda Wimalasiri >>>> *Software Engineering Intern* >>>> Mobile : 0713705814 >>>> Email : pam...@wso2.com >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Grainier Perera >>> Software Engineer >>> Mobile : +94716122384 >>> WSO2 Inc. | http://wso2.com >>> lean.enterprise.middleware >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> [image: http://wso2.com/signature] <http://wso2.com/signature> >> >> *Thilini Anoratna* >> Software Engineer >> WSO2 Inc.; http://wso2.com >> lean.enterprise.middleware >> >> mobile: +94 778955654 <+94+778955654> >> >> * <http://lk.linkedin.com/in/thilinianoratna>* >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Tishan Dahanayakage > Senior Software Engineer > WSO2, Inc. > Mobile:+94 716481328 > > 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, re-transmit, 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. > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Ashen Weerathunga* Software Engineer WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: tel:94716042995 <94716042995> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga <http://lk.linkedin.com/in/ashenweerathunga>* <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Heshitha Hettihewa
Congratulations Heshitha!!! :) On Mon, Sep 12, 2016 at 1:41 PM, Malintha Fernando <malinth...@wso2.com> wrote: > Congrats Heshitha! :) > > On Mon, Sep 12, 2016 at 12:33 PM, Kasun Thennakoon <kasu...@wso2.com> > wrote: > >> Congratulation Hetti J >> >> On Mon, Sep 12, 2016 at 12:16 PM, Dilshani Subasinghe <dilsh...@wso2.com> >> wrote: >> >>> Congratulations Heshitha !!! >>> >>> On Mon, Sep 12, 2016 at 11:55 AM, Nandika Jayawardana <nand...@wso2.com> >>> wrote: >>> >>>> Hi all, >>>> >>>> It is my pleasure to welcome Heshitha Hettihewa as a WSO2 Committer. >>>> Heshitha has been the leading contributor to Business Process Server >>>> tooling effort and in recognition of his contributions, he has been voted >>>> as a Committer. >>>> >>>> Heshitha, welcome aboard and keep up the good work. >>>> >>>> Regards, >>>> Nandika >>>> >>>> -- >>>> Nandika Jayawardana >>>> WSO2 Inc ; http://wso2.com >>>> lean.enterprise.middleware >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Best Regards, >>> >>> Dilshani Subasinghe >>> Software Engineer - QA *|* WSO2 >>> lean *|* enterprise *|* middleware >>> >>> Mobile : +94773375185 >>> Blog: dilshanilive.blogspot.com >>> >>> <https://wso2.com/signature> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Kasun Thennakoon* >> Software Engineer >> WSO2, Inc. >> Mobile:+94 711661919 >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Malintha Fernando > Software Engineer > WSO2 Inc. | http://wso2.com > Mobile : +94 718874922 > Blog : http://blog.malintha.org > > Lean . Enterprise . Middleware > > > > > > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Ashen Weerathunga* Software Engineer WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: tel:94716042995 <94716042995> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga <http://lk.linkedin.com/in/ashenweerathunga>* <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Mushthaq Rumy
Congratulations Rumy!!! On Fri, Sep 2, 2016 at 3:29 PM, Kasun Thennakoon <kasu...@wso2.com> wrote: > Congrats Rumy !! > > On Fri, Sep 2, 2016 at 12:15 PM, Farasath Ahamed <farasa...@wso2.com> > wrote: > >> Congratulations Rumy >> >> Farasath Ahamed >> Software Engineer, WSO2 Inc.; http://wso2.com >> Mobile: +94777603866 >> Blog: blog.farazath.com >> Twitter: @farazath619 <https://twitter.com/farazath619> >> <http://wso2.com/signature> >> >> >> >> On Fri, Sep 2, 2016 at 11:50 AM, Chandana Napagoda <chand...@wso2.com> >> wrote: >> >>> Hi all, >>> >>> It is my pleasure to welcome Mushthaq Rumy as a WSO2 Committer. Rumy has >>> made some great contributions to WSO2 Governance Registry and WSO2 >>> Enterprise Store products during the last few months and in recognition of >>> his commitment and contributions, he has been voted as a Committer for WSO2. >>> >>> Rumy, welcome aboard and keep up the good work. >>> >>> Best Regards, >>> Chandana >>> >>> -- >>> *Chandana Napagoda* >>> Associate Technical Lead >>> WSO2 Inc. - http://wso2.org >>> >>> *Email : chand...@wso2.com <chand...@wso2.com>**Mobile : +94718169299 >>> <%2B94718169299>* >>> >>> *Blog :http://cnapagoda.blogspot.com >>> <http://cnapagoda.blogspot.com> | http://chandana.napagoda.com >>> <http://chandana.napagoda.com>* >>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Kasun Thennakoon* > Software Engineer > WSO2, Inc. > Mobile:+94 711661919 > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Ashen Weerathunga* Software Engineer WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: tel:94716042995 <94716042995> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga <http://lk.linkedin.com/in/ashenweerathunga>* <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Natasha Wijesekara
Congratulations Natasha!!! :) On Wed, Jun 29, 2016 at 10:23 AM, Nandika Jayawardana <nand...@wso2.com> wrote: > Hi All, > > It's my pleasure to announce Natasha Wijesekara as a WSO2 Committer. > Natasha has been a great contributor to BPS and PC products and in > recognition of her contributions, she's been voted as a WSO2 Committer. > > Congratulations Natasha and keep up the good work! > > Regards > Nandika > > -- > Nandika Jayawardana > WSO2 Inc ; http://wso2.com > lean.enterprise.middleware > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Ashen Weerathunga* Software Engineer WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: +94 716042995 <94716042995> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga <http://lk.linkedin.com/in/ashenweerathunga>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Siddhi Query : group by results
Hi Aneela, As Charini mentioned above this is the expected output as for your query. There will be an output for each and every incoming event since you haven't included any window for your intermediateStream. But you can get your expected output by adding a batch window[1] to your query. As an example if you knew the event count you can simply add a lengthBatch[2] window as below, from intermediateStream#window.lengthBatch(3) select ts, count(ts) as ssh_logins group by ts insert into SSHOutStream; Then it will hold events as a batch of 3 events and return an output as below, ts ssh_logins 2016-05-08 08:59 1 2016-05-08 09:00 2 Similarly you can use other windows such as timeBatch, cron etc. as for your requirment. [1]https://docs.wso2.com/display/CEP410/SiddhiQL+Guide+3.0#SiddhiQLGuide3.0-InbuiltWindows [2]https://docs.wso2.com/display/CEP410/Inbuilt+Windows#InbuiltWindows-lengthBatch Best regards, Ashen On Wed, Jun 22, 2016 at 5:00 PM, Charini Nanayakkara <chari...@wso2.com> wrote: > Hi Aneela, > > The siddhi query you have specified processes each and every incoming > event. Since processing is done in real time, when the first event for ts= > 2016-05-08 > 09:00 arrives it gives count = 1 (due to no events with ts = 2016-05-08 > 09:00 having arrived earlier). When second event with ts = 2016-05-08 > 09:00 comes, we get count as 2 since an event with same ts arrived earlier > as well. > > Best Regards, > Charini > > On Wed, Jun 22, 2016 at 4:40 PM, Aneela Safdar <ansaf_...@yahoo.com> > wrote: > >> Hi all, >> >> I am having a trouble in digesting results of my group by query. My >> source stream named intermediateStream has data >> >> ts uid id_resp_h >> 2016-05-08 08:59 CLuCgz3HHzG7LpLwH9172.30.26.119 >> 2016-05-08 09:00 C3WnnK3TgUf2cSzxVa172.30.26.127 >> 2016-05-08 09:00 C3WnnK3TgUf2cSzxff172.30.26.119 >> >> SIDDHI query is >> >> from intermediateStream >> select ts, count(ts) as ssh_logins >> group by ts >> insert into SSHOutStream; >> >> I am expecting output to be like >> >> ts ssh_logins >> 2016-05-08 08:59 1 >> 2016-05-08 09:00 2 >> >> But instead it returns >> >> ts ssh_logins >> 2016-05-08 08:59 1 >> 2016-05-08 09:00 1 >> 2016-05-08 09:00 2 >> >> Any suggestions? >> >> Regards, Aneela Safdar >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Charini Vimansha Nanayakkara > Software Engineer at WSO2 > Mobile: 0714126293 > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Ashen Weerathunga* Software Engineer WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: +94 716042995 <94716042995> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga <http://lk.linkedin.com/in/ashenweerathunga>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Lahiru Manohara
Congratulations Lahiru! :) On Tue, Apr 19, 2016 at 1:04 PM, Fazlan Nazeem <fazl...@wso2.com> wrote: > Congrats Lahiru :) > > On Tue, Apr 19, 2016 at 11:47 AM, Manjula Rathnayake <manju...@wso2.com> > wrote: > >> Hi all, >> >> It's my pleasure to welcome Lahiru Manohara as a WSO2 Committer. Lahiru >> has been a key member of the AF/App Cloud team contributing to many aspects >> of App Cloud development/deployment ever since he joined us. In recognition >> of his contributions, ownership shown towards the tasks/responsibilities >> assigned to him, and commitment, he has been voted as a WSO2 committer. >> >> Lahiru, Welcome aboard and keep up the good work! >> >> thank you. >> >> -- >> Manjula Rathnayaka >> Associate Technical Lead >> WSO2, Inc. >> Mobile:+94 77 743 1987 >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Thanks & Regards, > > Fazlan Nazeem > > *Software Engineer* > > *WSO2 Inc* > Mobile : +94772338839 > <%2B94%20%280%29%20773%20451194> > fazl...@wso2.com > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Ashen Weerathunga* Software Engineer WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: +94 716042995 <94716042995> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga <http://lk.linkedin.com/in/ashenweerathunga>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Praminda Jayawardana
Congratulations Praminda!!! :) On Tue, Mar 29, 2016 at 11:26 AM, Janaka Ranabahu <jan...@wso2.com> wrote: > Hi, > > It is with great pleasure we welcome Praminda Jayawardana as a > WSO2 Committer. Congratulations Praminda and keep up the good work! > > ​Thanks, > Janaka​ > > -- > *Janaka Ranabahu* > Associate Technical Lead, WSO2 Inc. > http://wso2.com > > > *E-mail: jan...@wso2.com <http://wso2.com>**M: **+94 718370861 > <%2B94%20718370861>* > > Lean . Enterprise . Middleware > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Ashen Weerathunga* Software Engineer WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: +94 716042995 <94716042995> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga <http://lk.linkedin.com/in/ashenweerathunga>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Fazlan Nazeem
Congratulations Fazlan!!! :) On Tue, Jan 12, 2016 at 4:47 PM, Malintha Adikari <malin...@wso2.com> wrote: > Congratulations..!!! > > On Tue, Jan 12, 2016 at 4:36 PM, Nirmal Fernando <nir...@wso2.com> wrote: > >> Hi All, >> >> It's my pleasure to announce *Fazlan Nazeem* as a *WSO2 Committer*. He >> has been a key contributor to the *WSO2 Machine Learner *Product and in >> recognition of his work, he had been voted as a WSO2 Committer. >> >> Congratulations Fazlan and keep up the good work! >> >> -- >> >> Thanks & regards, >> Nirmal >> >> Team Lead - WSO2 Machine Learner >> Associate Technical Lead - Data Technologies Team, WSO2 Inc. >> Mobile: +94715779733 >> Blog: http://nirmalfdo.blogspot.com/ >> >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Malintha Adikari* > Software Engineer > WSO2 Inc.; http://wso2.com > lean.enterprise.middleware > > Mobile: +94 71 2312958 > Blog:http://malinthas.blogspot.com > Page: http://about.me/malintha > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Ashen Weerathunga* Software Engineer - Intern WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: +94 716042995 <94716042995> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga <http://lk.linkedin.com/in/ashenweerathunga>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [VOTE] Release WSO2 Machine Learner 1.1.0 RC5
Hi all, I've tested the following, - Verified both v10 APIs and v11 APIs. - Anomaly detection algorithms tested via ML wizard. - Default and tuned samples of Anomaly detection algorithms. Works fine. I didn't encounter any issues. [x] Stable - go ahead and release Thanks and Regards, Ashen On Tue, Dec 22, 2015 at 4:55 PM, Upul Bandara <u...@wso2.com> wrote: > Tested CEP extension, samples and ML Wizard. > > Looks OK > > [ x ] Stable - go ahead and release > > > On Tue, Dec 22, 2015 at 4:47 PM, Nirmal Fernando <nir...@wso2.com> wrote: > >> Tested samples and looks good! >> >> [ x ] Stable - go ahead and release >> >> >> On Tue, Dec 22, 2015 at 3:52 PM, Maheshakya Wijewardena < >> mahesha...@wso2.com> wrote: >> >>> Hi Devs, >>> >>> This is the 5th Release Candidate of WSO2 Machine Learner 1.1.0. >>> >>> This release fixes the following issues: >>> https://wso2.org/jira/issues/?filter=12601 >>> >>> Please download, test and vote. Vote will be open for 72 hours or as >>> longer as needed. >>> >>> *Binary distribution files:* >>> >>> https://github.com/wso2/product-ml/releases/download/v1.1.0-rc5/wso2ml-1.1.0.zip >>> >>> *P2 repository*: >>> >>> https://github.com/wso2/product-ml/releases/download/v1.1.0-rc5/p2-repo.zip >>> >>> >>> *Maven staging repository:* >>> http://maven.wso2.org/nexus/content/repositories/orgwso2ml-230/ >>> <http://www.google.com/url?q=http%3A%2F%2Fmaven.wso2.org%2Fnexus%2Fcontent%2Frepositories%2Forgwso2ml-230%2F=D=1=AFQjCNFgpNofnJ8T4zcllTSN8d7xq4cu4w> >>> >>> *The tag to be voted upon:* >>> https://github.com/wso2/product-ml/tree/v1.1.0-rc5 >>> >>> >>> [ ] Broken - do not release (explain why) >>> [ ] Stable - go ahead and release >>> >>> Thank you, >>> Machine Learner Team >>> >>> -- >>> Pruthuvi Maheshakya Wijewardena >>> mahesha...@wso2.com >>> +94711228855 >>> >>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> >> Thanks & regards, >> Nirmal >> >> Team Lead - WSO2 Machine Learner >> Associate Technical Lead - Data Technologies Team, WSO2 Inc. >> Mobile: +94715779733 >> Blog: http://nirmalfdo.blogspot.com/ >> >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Upul Bandara, > Associate Technical Lead, WSO2, Inc., > Mob: +94 715 468 345. > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Ashen Weerathunga* Software Engineer - Intern WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: +94 716042995 <94716042995> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga <http://lk.linkedin.com/in/ashenweerathunga>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [VOTE] Release WSO2 Machine Learner 1.1.0 RC4
Hi all, I've tested the following, - Verified both v10 APIs and v11 APIs. - UI and both default and tuned samples of Anomaly detection algorithms. Works fine. I didn't encounter any issues. [x] Stable - go ahead and release Thanks and Regards, Ashen On Tue, Dec 22, 2015 at 12:11 AM, Maheshakya Wijewardena < mahesha...@wso2.com> wrote: > Hi Devs, > > This is the 4th Release Candidate of WSO2 Machine Learner 1.1.0. > > This release fixes the following issues: > https://wso2.org/jira/issues/?filter=12600 > > Please download, test and vote. Vote will be open for 72 hours or as > longer as needed. > > *Binary distribution files:* > > https://github.com/wso2/product-ml/releases/download/v1.1.0-rc4/wso2ml-1.1.0.zip > > *P2 repository*: > https://github.com/wso2/product-ml/releases/download/v1.1.0-rc4/p2-repo.zip > > > *Maven staging repository:* > http://maven.wso2.org/nexus/content/repositories/orgwso2ml-224/ > <http://www.google.com/url?q=http%3A%2F%2Fmaven.wso2.org%2Fnexus%2Fcontent%2Frepositories%2Forgwso2ml-224%2F=D=1=AFQjCNEGJebhoedukGL1bLh-YnHj8A_Upw> > > *The tag to be voted upon:* > https://github.com/wso2/product-ml/tree/v1.1.0-rc4 > > > [ ] Broken - do not release (explain why) > [ ] Stable - go ahead and release > > Thank you, > Machine Learner Team > > -- > Pruthuvi Maheshakya Wijewardena > mahesha...@wso2.com > +94711228855 > > > > _______ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Ashen Weerathunga* Software Engineer - Intern WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: +94 716042995 <94716042995> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga <http://lk.linkedin.com/in/ashenweerathunga>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Machine Learner 1.1.0 - Alpha Released!
*WSO2 Machine Learner 1.1.0 - Alpha Released!* We are pleased to announce that the Alpha release of WSO2 Machine Learner 1.1.0 is now available to download from here <https://github.com/wso2/product-ml/releases/download/v1.1.0-alpha/wso2ml-1.1.0-alpha.zip>. Source and tag location for this release is available here <https://github.com/wso2/product-ml/releases/tag/v1.1.0-alpha>. Machine learning has emerged as a key component of big data analytics space. The goal of WSO2 Machine Learner is to make machine learning accessible to WSO2 big data platform. WSO2 Machine Learner ( http://wso2.com/products/machine-learner/) provides a user friendly wizard like interface, which guides users through a set of steps to find and configure machine learning algorithms. The outcome of this process is a model that can be deployed in multiple WSO2 products, such as WSO2 Enterprise Service Bus (ESB), WSO2 Complex Event Processor (CEP), WSO2 Data Analytics Server (DAS) etc. The novice-friendly machine learning analysis allows developers, data scientists and database administrators to quickly implement machine learning methods. If you are familiar with WSO2 products, you can utilize WSO2 Machine Learner to build machine learning models for various tasks, such as fraud detection, anomaly detection, classification etc. WSO2 Machine Learner is built up on the award-winning, WSO2 Carbon platform, which is based on the OSGi framework enabling better modularity for your service oriented architecture (SOA). *Key Features of WSO2 ML 1.1.0 Release* - Deep learning algorithm support - Anomaly detection algorithm support - Recommendation algorithm support - PMML support *Documentation*: 1.1.0 Alpha release specific documentation can be downloaded from https://github.com/wso2/product-ml/files/47652/WSO2MachineLearner1.1.0-AlphaRelease.pdf For general information on WSO2 Machine Learner 1.1.0 release, please visit our documentation https://docs.wso2.com/display/ML110/WSO2+Machine+Learner+Documentation *How You Can Contribute* *Mailing Lists* Join our mailing list and correspond with the developers directly. Developer List : dev@wso2.org | Mail Archive <http://mail.wso2.org/mailarchive/dev/> *Reporting Issues* We encourage you to report issues, documentation faults and feature requests regarding WSO2 Machine Learner through the public JIRA <https://wso2.org/jira/browse/ML>. You can use the Carbon JIRA <https://wso2.org/jira/browse/CARBON> to report any issues related to the Carbon framework or associated Carbon components. *~~~ WSO2 Machine Learner Team ~~~* -- *Ashen Weerathunga* Software Engineer - Intern WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: +94 716042995 <94716042995> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga <http://lk.linkedin.com/in/ashenweerathunga>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Sachith Withana
Congratz Sachith!!! :) On Tue, Dec 1, 2015 at 11:14 AM, Vithulan Vijayanandan <vithu...@wso2.com> wrote: > Congratzz aiyaa! :D > > On Tue, Dec 1, 2015 at 11:10 AM, Nuwan Pallewela <nuw...@wso2.com> wrote: > >> Congratz sachith >> >> On Tue, Dec 1, 2015 at 11:00 AM, Malintha Adikari <malin...@wso2.com> >> wrote: >> >>> Congratulations Sachith... >>> >>> On Tue, Dec 1, 2015 at 10:59 AM, Dunith Dhanushka <dun...@wso2.com> >>> wrote: >>> >>>> Congrats Sachith! >>>> >>>> On Tue, Dec 1, 2015 at 10:54 AM, Anjana Fernando <anj...@wso2.com> >>>> wrote: >>>> >>>>> Hi everyone, >>>>> >>>>> It is my pleasure to welcome Sachith as a WSO2 committer. He has done >>>>> numerous contributions to the Data Analytics Server product, in doing >>>>> development and bringing in ideas, and has proved to be a valuable and a >>>>> dependable person. So Sachith welcome aboard, and keep up with the good >>>>> work! .. >>>>> >>>>> Cheers, >>>>> Anjana. >>>>> -- >>>>> *Anjana Fernando* >>>>> Senior Technical Lead >>>>> WSO2 Inc. | http://wso2.com >>>>> lean . enterprise . middleware >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Regards, >>>> >>>> Dunith Dhanushka, >>>> Senior Software Engineer >>>> WSO2 Inc, >>>> >>>> Mobile - +94 71 8615744 >>>> Blog - dunithd.wordpress.com <http://blog.dunith.com> >>>> Twitter - @dunithd <http://twitter.com/dunithd> >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> *Malintha Adikari* >>> Software Engineer >>> WSO2 Inc.; http://wso2.com >>> lean.enterprise.middleware >>> >>> Mobile: +94 71 2312958 >>> Blog:http://malinthas.blogspot.com >>> Page: http://about.me/malintha >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> -- >> >> *Nuwan Chamara Pallewela* >> >> >> *Software Engineer* >> >> *WSO2, Inc. *http://wso2.com >> *lean . enterprise . middleware* >> >> Email *nuw...@wso2.com <nuw...@wso2.com>* >> Mobile *+94719079739 <%2B94719079739>@* >> >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Vithulan MV* > > Intern-Software Engineering > WSO2, Inc : wso2.com > Mobile: +94712540524 > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Ashen Weerathunga* Software Engineer - Intern WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: +94 716042995 <94716042995> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga <http://lk.linkedin.com/in/ashenweerathunga>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Maheshakya Wijewardena
Congratz Maheshakya!!! :) On Tue, Oct 20, 2015 at 10:42 AM, Nirmal Fernando <nir...@wso2.com> wrote: > Hi All, > > It's my pleasure to announce *Maheshakya Wijewardena* as a > *WSO2 Committer*. He has been a key contributor to the *WSO2 Machine > Learner *Product and in recognition of his excellent work, he had been > voted as a WSO2 Committer. > > Congratulations Maheshakya and keep up the good work! > > -- > > Thanks & regards, > Nirmal > > Team Lead - WSO2 Machine Learner > Associate Technical Lead - Data Technologies Team, WSO2 Inc. > Mobile: +94715779733 > Blog: http://nirmalfdo.blogspot.com/ > > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Ashen Weerathunga* Software Engineer - Intern WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: +94 716042995 <94716042995> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga <http://lk.linkedin.com/in/ashenweerathunga>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ML] Accuracy Measure for Anomaly Detection?
Thanks Dr. Ruvan and Supun for the suggestions! Yes Supun, In this scenario we consider a percentile value of all distances to identify the cluster boundary rather than just considering the max distance. Right now we are getting that percentile value from the user. yes, If we do calculate set of confusion matrices by considering set of boundary values it will help user to identify the best option. will work on that. Thanks for the idea! On Thu, Sep 24, 2015 at 8:05 PM, Supun Sethunga <sup...@wso2.com> wrote: > ...test data according to the percentile value that user provided. > > > Sorry I missed this part. If so, can't we not ask the user the percentile, > but instead create the ROC and let him decide the best percentile looking > at the ROC? > > On Thu, Sep 24, 2015 at 10:26 AM, Supun Sethunga <sup...@wso2.com> wrote: > >> Hi Ashen, >> >> In probabilistic models, what we do is, compare the predicted output of a >> new data-point, against a cutoff probability, to decide which class it >> belongs to. And this cutoff probability is decided by the user, hence has >> the freedom to change from 0 to 1. So for a set of newly-arrived data >> points, we can change the "cutoff probability" for any number of times >> (between 0-1) and find a series of confusion matrices. >> >> But in this case, (From what understood from the other mail thread, the >> logic applied here is..) you first cluster the data, then for each incoming >> data, you find the nearest cluster, then compare the distance between the >> new point and the cluster's center, with the cluster-boundary. (please >> correct me if i've mistaken). So we have only one static value as the class >> boundary, and hence cannot have a series of confusion matrices. (which >> means no ROC). But again, in the other mail thread you mentioned "*select >> the* *percentile value from distances of each clusters as their cluster >> boundaries*", Im not really sure what that "percentile" value is, but if >> this is a volatile value or a user preferred value, I think we can change >> that and do a similar thing as in the probabilistic case.. This means we >> are changing the cluster boundaries and see how the accuracy (or the >> measurement statistics) change. >> >> Regards, >> Supun >> >> >> On Wed, Sep 23, 2015 at 9:17 AM, Ashen Weerathunga <as...@wso2.com> >> wrote: >> >>> Hi all, >>> >>> Thanks Mahesan for the suggestion. yes we can give all the measure if It >>> is better. >>> >>> But there is some problem of drawing PR curve or ROC curve. Since we can >>> get only one point using the confusion matrix we cant give PR curve or ROC >>> curve in the summary of the model. Currently ROC curve provided only in >>> probabilistic classification methods. It's also calculated using the model >>> itself. But in this scenario we use K means algorithm. after generating the >>> clusters we evaluate the model using the test data according to the >>> percentile value that user provided. So as a result we can get the >>> confusion matrix which consist of TP,TN,FP,FN. But to draw a PR curve or >>> ROC curve that is not enough. Does anyone have any suggestions about that? >>> or should we drop it? >>> >>> On Mon, Sep 21, 2015 at 7:05 AM, Sinnathamby Mahesan < >>> sinnatha...@wso2.com> wrote: >>> >>>> Ashen >>>> Here is a situation: >>>> Doctors are testing a person for a disease, say, d. >>>> Doctor's point of view +ve means patient has (d) >>>> >>>> Which is of the following is worse than the other? >>>> (1) The person who does NOT have (d) is identified as having (d) - >>>> (that is, false positive ) >>>> (2) The person who does have (d) is identified as NOT having (d) - >>>> (that is, false negative) >>>> >>>> Doctors argument is that we have to be more concern on reducing case >>>> (2) >>>> That is to say, the sensitivity needs to be high. >>>> >>>> Anyway, I also thought it is better to display all measures : >>>> sensitivity, specificity, precision and F1-Score >>>> (suggesting to consider sensitivity for the case of anomalous being >>>> positive. >>>> >>>> Good Luck >>>> Mahesan >>>> >>>> >>>> On 18 September 2015 at 15:27, Ashen Weerathunga <as...@wso2.com> >>>> wrote: >>>> >>>>&g
Re: [Dev] [ML] Accuracy Measure for Anomaly Detection?
Hi all, Thanks Mahesan for the suggestion. yes we can give all the measure if It is better. But there is some problem of drawing PR curve or ROC curve. Since we can get only one point using the confusion matrix we cant give PR curve or ROC curve in the summary of the model. Currently ROC curve provided only in probabilistic classification methods. It's also calculated using the model itself. But in this scenario we use K means algorithm. after generating the clusters we evaluate the model using the test data according to the percentile value that user provided. So as a result we can get the confusion matrix which consist of TP,TN,FP,FN. But to draw a PR curve or ROC curve that is not enough. Does anyone have any suggestions about that? or should we drop it? On Mon, Sep 21, 2015 at 7:05 AM, Sinnathamby Mahesan <sinnatha...@wso2.com> wrote: > Ashen > Here is a situation: > Doctors are testing a person for a disease, say, d. > Doctor's point of view +ve means patient has (d) > > Which is of the following is worse than the other? > (1) The person who does NOT have (d) is identified as having (d) - > (that is, false positive ) > (2) The person who does have (d) is identified as NOT having (d) - > (that is, false negative) > > Doctors argument is that we have to be more concern on reducing case > (2) > That is to say, the sensitivity needs to be high. > > Anyway, I also thought it is better to display all measures : sensitivity, > specificity, precision and F1-Score > (suggesting to consider sensitivity for the case of anomalous being > positive. > > Good Luck > Mahesan > > > On 18 September 2015 at 15:27, Ashen Weerathunga <as...@wso2.com> wrote: > >> Hi all. >> >> Since we are considering the anomaly detection true positive would be a >> case where a true anomaly detected as a anomaly by the model. Since in the >> real world scenario of anomaly detection as you said the positive(anomaly) >> instances are vary rare we can't go for more general measure. So I can >> summarized the most applicable measures as below, >> >>- Sensitivity(recall) - gives the True Positive Rate. ( TP/(TP + FN) ) >>- Precision - gives the probability of predicting a True Positive >>from all positive predictions ( TP/(TP+FP) ) >>- PR cure - Precision recall(Sensitivity) curve - PR curve plots >>Precision Vs. Recall. >>- F1 score - gives the harmonic mean of Precision and >>Sensitivity(recall) ( 2TP / (2TP + FP + FN) ) >> >> So Precision and the Sensitivity are the most suitable measures to >> measure a model where positive instances are very less. And PR curve and F1 >> score are mixtures of both Sensitivity and Precision. So PR curve and F1 >> score can be used to tell how good is the model IMO. We can give >> Sensitivity and Precision also separately. >> >> Thanks everyone for the support. >> >> @Srinath, sure, I will write an article. >> >> >> Thanks and Regards, >> >> Ashen >> >> On Thu, Sep 17, 2015 at 10:19 AM, madhuka udantha < >> madhukaudan...@gmail.com> wrote: >> >>> Hi, >>> >>> This is good survey paper that can be found regard to Anomaly detection >>> [1], According to your need; it seems you will no need to go through whole >>> the survey papers. But few sub topics will be very useful for you. This >>> paper will be useful for your work. >>> >>> [1] Varun Chandola, Arindam Banerjee, and Vipin Kumar. 2009. Anomaly >>> detection: A survey. ACM Comput. Surv. 41, 3, Article 15 (July 2009), 58 >>> pages. DOI=10.1145/1541880.1541882 >>> <http://www.researchgate.net/profile/Vipin_Kumar26/publication/220565847_Anomaly_detection_A_survey/links/0deec5161f0ca7302a00.pdf> >>> [Cited by 2458] >>> >>> On Wed, Sep 16, 2015 at 3:35 PM, Ashen Weerathunga <as...@wso2.com> >>> wrote: >>> >>>> Hi all, >>>> >>>> I am currently doing the integration of anomaly detection feature for >>>> ML. I have a problem of choosing the best accuracy measure for the model. I >>>> can get the confusion matrix which consists of true positives, true >>>> negatives, false positives and false negatives. There are few different >>>> measures such as sensitivity, accuracy, F1 score, etc. So what will be the >>>> best measure to give as the model accuracy for anomaly detection model. >>>> >>>> [1] <https://en.wikipedia.org/wiki/Sensitivity_and_specificity>Some >>>> details about those measures. >>>> >>>&g
Re: [Dev] [ML] Accuracy Measure for Anomaly Detection?
Hi all.
Since we are considering the anomaly detection true positive would be a
case where a true anomaly detected as a anomaly by the model. Since in the
real world scenario of anomaly detection as you said the positive(anomaly)
instances are vary rare we can't go for more general measure. So I can
summarized the most applicable measures as below,
- Sensitivity(recall) - gives the True Positive Rate. ( TP/(TP + FN) )
- Precision - gives the probability of predicting a True Positive from
all positive predictions ( TP/(TP+FP) )
- PR cure - Precision recall(Sensitivity) curve - PR curve plots
Precision Vs. Recall.
- F1 score - gives the harmonic mean of Precision and
Sensitivity(recall) ( 2TP / (2TP + FP + FN) )
So Precision and the Sensitivity are the most suitable measures to measure
a model where positive instances are very less. And PR curve and F1 score
are mixtures of both Sensitivity and Precision. So PR curve and F1 score
can be used to tell how good is the model IMO. We can give Sensitivity and
Precision also separately.
Thanks everyone for the support.
@Srinath, sure, I will write an article.
Thanks and Regards,
Ashen
On Thu, Sep 17, 2015 at 10:19 AM, madhuka udantha <madhukaudan...@gmail.com>
wrote:
> Hi,
>
> This is good survey paper that can be found regard to Anomaly detection
> [1], According to your need; it seems you will no need to go through whole
> the survey papers. But few sub topics will be very useful for you. This
> paper will be useful for your work.
>
> [1] Varun Chandola, Arindam Banerjee, and Vipin Kumar. 2009. Anomaly
> detection: A survey. ACM Comput. Surv. 41, 3, Article 15 (July 2009), 58
> pages. DOI=10.1145/1541880.1541882
> <http://www.researchgate.net/profile/Vipin_Kumar26/publication/220565847_Anomaly_detection_A_survey/links/0deec5161f0ca7302a00.pdf>
> [Cited by 2458]
>
> On Wed, Sep 16, 2015 at 3:35 PM, Ashen Weerathunga <as...@wso2.com> wrote:
>
>> Hi all,
>>
>> I am currently doing the integration of anomaly detection feature for ML.
>> I have a problem of choosing the best accuracy measure for the model. I can
>> get the confusion matrix which consists of true positives, true negatives,
>> false positives and false negatives. There are few different measures such
>> as sensitivity, accuracy, F1 score, etc. So what will be the best measure
>> to give as the model accuracy for anomaly detection model.
>>
>> [1] <https://en.wikipedia.org/wiki/Sensitivity_and_specificity>Some
>> details about those measures.
>>
>> Terminology and derivations
>> from a confusion matrix <https://en.wikipedia.org/wiki/Confusion_matrix> true
>> positive (TP)eqv. with hittrue negative (TN)eqv. with correct rejectionfalse
>> positive (FP)eqv. with false alarm
>> <https://en.wikipedia.org/wiki/False_alarm>, Type I error
>> <https://en.wikipedia.org/wiki/Type_I_error>false negative (FN)eqv. with
>> miss, Type II error <https://en.wikipedia.org/wiki/Type_II_error>
>> --
>> sensitivity <https://en.wikipedia.org/wiki/Sensitivity_%28test%29> or
>> true positive rate (TPR)eqv. with hit rate
>> <https://en.wikipedia.org/wiki/Hit_rate>, recall
>> <https://en.wikipedia.org/wiki/Information_retrieval#Recall>[image:
>> \mathit{TPR} = \mathit{TP} / P = \mathit{TP} / (\mathit{TP}+\mathit{FN})]
>> specificity <https://en.wikipedia.org/wiki/Specificity_%28tests%29>
>> (SPC) or true negative rate[image: \mathit{SPC} = \mathit{TN} / N =
>> \mathit{TN} / (\mathit{TN}+\mathit{FP})]precision
>> <https://en.wikipedia.org/wiki/Information_retrieval#Precision> or positive
>> predictive value
>> <https://en.wikipedia.org/wiki/Positive_predictive_value> (PPV)[image:
>> \mathit{PPV} = \mathit{TP} / (\mathit{TP} + \mathit{FP})]negative
>> predictive value
>> <https://en.wikipedia.org/wiki/Negative_predictive_value> (NPV)[image:
>> \mathit{NPV} = \mathit{TN} / (\mathit{TN} + \mathit{FN})]fall-out
>> <https://en.wikipedia.org/wiki/Information_retrieval#Fall-out> or false
>> positive rate <https://en.wikipedia.org/wiki/False_positive_rate>
>> (FPR)[image:
>> \mathit{FPR} = \mathit{FP} / N = \mathit{FP} / (\mathit{FP} + \mathit{TN})
>> = 1-\mathit{SPC}]false negative rate
>> <https://en.wikipedia.org/wiki/False_negative_rate> (FNR)[image:
>> \mathit{FNR} = \mathit{FN} / (\mathit{TP} + \mathit{FN}) =
>> 1-\mathit{TPR}]false
>> discovery rate <https://en.wikipedia.org/wiki/False_discovery_rate>
>> (FDR)[image:
>> \mathit{FDR} = \mathit{FP} / (\mathit{TP} + \mathit{FP}) = 1 - \mathit{PPV}]
>> --
[Dev] [ML] Accuracy Measure for Anomaly Detection?
Hi all,
I am currently doing the integration of anomaly detection feature for ML. I
have a problem of choosing the best accuracy measure for the model. I can
get the confusion matrix which consists of true positives, true negatives,
false positives and false negatives. There are few different measures such
as sensitivity, accuracy, F1 score, etc. So what will be the best measure
to give as the model accuracy for anomaly detection model.
[1] <https://en.wikipedia.org/wiki/Sensitivity_and_specificity>Some details
about those measures.
Terminology and derivations
from a confusion matrix <https://en.wikipedia.org/wiki/Confusion_matrix> true
positive (TP)eqv. with hittrue negative (TN)eqv. with correct rejectionfalse
positive (FP)eqv. with false alarm
<https://en.wikipedia.org/wiki/False_alarm>, Type I error
<https://en.wikipedia.org/wiki/Type_I_error>false negative (FN)eqv. with
miss, Type II error <https://en.wikipedia.org/wiki/Type_II_error>
--
sensitivity <https://en.wikipedia.org/wiki/Sensitivity_%28test%29> or true
positive rate (TPR)eqv. with hit rate
<https://en.wikipedia.org/wiki/Hit_rate>, recall
<https://en.wikipedia.org/wiki/Information_retrieval#Recall>[image:
\mathit{TPR} = \mathit{TP} / P = \mathit{TP} / (\mathit{TP}+\mathit{FN})]
specificity <https://en.wikipedia.org/wiki/Specificity_%28tests%29> (SPC)
or true negative rate[image: \mathit{SPC} = \mathit{TN} / N = \mathit{TN} /
(\mathit{TN}+\mathit{FP})]precision
<https://en.wikipedia.org/wiki/Information_retrieval#Precision> or positive
predictive value <https://en.wikipedia.org/wiki/Positive_predictive_value>
(PPV)[image: \mathit{PPV} = \mathit{TP} / (\mathit{TP} + \mathit{FP})]negative
predictive value <https://en.wikipedia.org/wiki/Negative_predictive_value>
(NPV)[image: \mathit{NPV} = \mathit{TN} / (\mathit{TN} + \mathit{FN})]
fall-out <https://en.wikipedia.org/wiki/Information_retrieval#Fall-out>
or false
positive rate <https://en.wikipedia.org/wiki/False_positive_rate> (FPR)[image:
\mathit{FPR} = \mathit{FP} / N = \mathit{FP} / (\mathit{FP} + \mathit{TN})
= 1-\mathit{SPC}]false negative rate
<https://en.wikipedia.org/wiki/False_negative_rate> (FNR)[image:
\mathit{FNR} = \mathit{FN} / (\mathit{TP} + \mathit{FN}) = 1-\mathit{TPR}]false
discovery rate <https://en.wikipedia.org/wiki/False_discovery_rate>
(FDR)[image:
\mathit{FDR} = \mathit{FP} / (\mathit{TP} + \mathit{FP}) = 1 - \mathit{PPV}]
--
accuracy <https://en.wikipedia.org/wiki/Accuracy> (ACC)[image: \mathit{ACC}
= (\mathit{TP} + \mathit{TN}) / (\mathit{TP} + \mathit{FP} + \mathit{FN} +
\mathit{TN})]F1 score <https://en.wikipedia.org/wiki/F1_score>is the harmonic
mean
<https://en.wikipedia.org/wiki/Harmonic_mean#Harmonic_mean_of_two_numbers>
of precision <https://en.wikipedia.org/wiki/Information_retrieval#Precision>
and sensitivity <https://en.wikipedia.org/wiki/Sensitivity_%28test%29>[image:
\mathit{F1} = 2 \mathit{TP} / (2 \mathit{TP} + \mathit{FP} +
\mathit{FN})]Matthews
correlation coefficient
<https://en.wikipedia.org/wiki/Matthews_correlation_coefficient> (MCC)[image:
\frac{ \mathit{TP} \times \mathit{TN} - \mathit{FP} \times \mathit{FN} }
{\sqrt{ (\mathit{TP}+\mathit{FP}) ( \mathit{TP} + \mathit{FN} ) (
\mathit{TN} + \mathit{FP} ) ( \mathit{TN} + \mathit{FN} ) }
}]Informedness[image:
\mathit{TPR} + \mathit{SPC} - 1]Markedness
<https://en.wikipedia.org/wiki/Markedness>[image: \mathit{PPV} +
\mathit{NPV} - 1]
*Sources: Fawcett (2006) and Powers (2011).*[1]
<https://en.wikipedia.org/wiki/Sensitivity_and_specificity#cite_note-Fawcett2006-1>
[2]
<https://en.wikipedia.org/wiki/Sensitivity_and_specificity#cite_note-Powers2011-2>
Thanks and Regards,
Ashen
--
*Ashen Weerathunga*
Software Engineer - Intern
WSO2 Inc.: http://wso2.com
lean.enterprise.middleware
Email: as...@wso2.com
Mobile: +94 716042995 <94716042995>
LinkedIn:
*http://lk.linkedin.com/in/ashenweerathunga
<http://lk.linkedin.com/in/ashenweerathunga>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ML] Spark K-means clustering on KDD cup 99 dataset
@Nirmal, okay i'll arange it today. @Mahesan Thanks for the suggestion. yes 100 must me too high for some cases. I thought that during 100 iterations most probably it will converge to stable clusters. Thats why I put 100. yes as cases like k = 100 it might be not enough. Thanks and ill try with different number of iterations also. On Wed, Aug 26, 2015 at 9:31 AM, Nirmal Fernando nir...@wso2.com wrote: @Ashen let's have a code review today, if it's possible. @Srinath Forgot to mention that I've already given some feedback to Ashen, on how he could use Spark transformations effectively in his code. On Tue, Aug 25, 2015 at 4:33 PM, Ashen Weerathunga as...@wso2.com wrote: Okay sure. On Tue, Aug 25, 2015 at 3:55 PM, Nirmal Fernando nir...@wso2.com wrote: Sure. @Ashen, can you please arrange one? On Tue, Aug 25, 2015 at 2:35 PM, Srinath Perera srin...@wso2.com wrote: Nirmal, Seshika, shall we do a code review? This code should go into ML after UI part is done. Thanks Srinath On Tue, Aug 25, 2015 at 2:20 PM, Ashen Weerathunga as...@wso2.com wrote: Hi all, This is the source code of the project. https://github.com/ashensw/Spark-KMeans-fraud-detection Best Regards, Ashen On Tue, Aug 25, 2015 at 2:00 PM, Ashen Weerathunga as...@wso2.com wrote: Thanks all for the suggestions, There are few assumptions I have made, - Clusters are uniform - Fraud data always will be outliers to the normal clusters - Clusters are not intersect with each other - I have given the number of Iterations as 100. So I assume that 100 iterations will be enough to make almost stable clusters @Maheshakya, In this dataset consist of higher amount of anomaly data than the normal data. But the practical scenario will be otherwise. Because of that It will be more unrealistic if I use those 65% of anomaly data to evaluate the model. The amount of normal data I used to build the model is also less than those 65% of anomaly data. Yes since our purpose is to detect anomalies It would be good to try with more anomaly data to evaluate the model.Thanks and I'll try to use them also. Best Regards, Ashen On Tue, Aug 25, 2015 at 12:35 PM, Maheshakya Wijewardena mahesha...@wso2.com wrote: Is there any particular reason why you are putting aside 65% of anomalous data at the evaluation? Since there is an obvious imbalance when the numbers of normal and abnormal cases are taken into account, you will get greater accuracy at the evaluation because a model tends to produce more accurate results for the class with the greater size. But it's not the case for the class of smaller size. With less number of records, it wont make much impact on the accuracy. Hence IMO, it would be better if you could evaluate with more anomalous data. i.e. number of records of each class needs to be roughly equal. Best regards On Tue, Aug 25, 2015 at 12:05 PM, CD Athuraliya chathur...@wso2.com wrote: Hi Ashen, It would be better if you can add the assumptions you make in this process (uniform clusters etc). It will make the process more clear IMO. Regards, CD On Tue, Aug 25, 2015 at 11:39 AM, Nirmal Fernando nir...@wso2.com wrote: Can we see the code too? On Tue, Aug 25, 2015 at 11:36 AM, Ashen Weerathunga as...@wso2.com wrote: Hi all, I am currently working on fraud detection project. I was able to cluster the KDD cup 99 network anomaly detection dataset using apache spark k means algorithm. So far I was able to achieve 99% accuracy rate from this dataset.The steps I have followed during the process are mentioned below. - Separate the dataset into two parts (normal data and anomaly data) by filtering the label - Splits each two parts of data as follows - normal data - 65% - to train the model - 15% - to optimize the model by adjusting hyper parameters - 20% - to evaluate the model - anomaly data - 65% - no use - 15% - to optimize the model by adjusting hyper parameters - 20% - to evaluate the model - Prepossess the dataset - Drop out non numerical features since k means can only handle numerical values - Normalize all the values to 1-0 range - Cluster the 65% of normal data using Apache spark K means and build the model (15% of both normal and anomaly data were used to tune the hyper parameters such as k, percentile etc. to get an optimized model) - Finally evaluate the model using 20% of both normal and anomaly data. Method of identifying a fraud as follows, - When a new data point comes, get the closest cluster center by using k means predict function. - I have calculate 98th percentile distance for each cluster. (98 was the best value I got by tuning the model with different values) - Then I checked whether the distance of new data point with the given
Re: [Dev] [ML] Spark K-means clustering on KDD cup 99 dataset
Thanks all for the suggestions, There are few assumptions I have made, - Clusters are uniform - Fraud data always will be outliers to the normal clusters - Clusters are not intersect with each other - I have given the number of Iterations as 100. So I assume that 100 iterations will be enough to make almost stable clusters @Maheshakya, In this dataset consist of higher amount of anomaly data than the normal data. But the practical scenario will be otherwise. Because of that It will be more unrealistic if I use those 65% of anomaly data to evaluate the model. The amount of normal data I used to build the model is also less than those 65% of anomaly data. Yes since our purpose is to detect anomalies It would be good to try with more anomaly data to evaluate the model.Thanks and I'll try to use them also. Best Regards, Ashen On Tue, Aug 25, 2015 at 12:35 PM, Maheshakya Wijewardena mahesha...@wso2.com wrote: Is there any particular reason why you are putting aside 65% of anomalous data at the evaluation? Since there is an obvious imbalance when the numbers of normal and abnormal cases are taken into account, you will get greater accuracy at the evaluation because a model tends to produce more accurate results for the class with the greater size. But it's not the case for the class of smaller size. With less number of records, it wont make much impact on the accuracy. Hence IMO, it would be better if you could evaluate with more anomalous data. i.e. number of records of each class needs to be roughly equal. Best regards On Tue, Aug 25, 2015 at 12:05 PM, CD Athuraliya chathur...@wso2.com wrote: Hi Ashen, It would be better if you can add the assumptions you make in this process (uniform clusters etc). It will make the process more clear IMO. Regards, CD On Tue, Aug 25, 2015 at 11:39 AM, Nirmal Fernando nir...@wso2.com wrote: Can we see the code too? On Tue, Aug 25, 2015 at 11:36 AM, Ashen Weerathunga as...@wso2.com wrote: Hi all, I am currently working on fraud detection project. I was able to cluster the KDD cup 99 network anomaly detection dataset using apache spark k means algorithm. So far I was able to achieve 99% accuracy rate from this dataset.The steps I have followed during the process are mentioned below. - Separate the dataset into two parts (normal data and anomaly data) by filtering the label - Splits each two parts of data as follows - normal data - 65% - to train the model - 15% - to optimize the model by adjusting hyper parameters - 20% - to evaluate the model - anomaly data - 65% - no use - 15% - to optimize the model by adjusting hyper parameters - 20% - to evaluate the model - Prepossess the dataset - Drop out non numerical features since k means can only handle numerical values - Normalize all the values to 1-0 range - Cluster the 65% of normal data using Apache spark K means and build the model (15% of both normal and anomaly data were used to tune the hyper parameters such as k, percentile etc. to get an optimized model) - Finally evaluate the model using 20% of both normal and anomaly data. Method of identifying a fraud as follows, - When a new data point comes, get the closest cluster center by using k means predict function. - I have calculate 98th percentile distance for each cluster. (98 was the best value I got by tuning the model with different values) - Then I checked whether the distance of new data point with the given cluster center is less than or grater than the 98th percentile of that cluster. If it is less than the percentile it is considered as a normal data. If it is grater than the percentile it is considered as a fraud since it is in outside the cluster. Our next step is to integrate this feature to ML product and try out it with more realistic dataset. A summery of results I have obtained using 98th percentile during the process is attached with this. https://docs.google.com/a/wso2.com/spreadsheets/d/1E5fXk9CM31QEkyFCIEongh8KAa6jPeoY7OM3HraGPd4/edit?usp=sharing Thanks and Regards, Ashen -- *Ashen Weerathunga* Software Engineer - Intern WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: +94 716042995 94716042995 LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga http://lk.linkedin.com/in/ashenweerathunga* -- Thanks regards, Nirmal Team Lead - WSO2 Machine Learner Associate Technical Lead - Data Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ -- *CD Athuraliya* Software Engineer WSO2, Inc. lean . enterprise . middleware Mobile: +94 716288847 94716288847 LinkedIn http://lk.linkedin.com/in/cdathuraliya | Twitter https://twitter.com/cdathuraliya | Blog http://cdathuraliya.tumblr.com/ -- Pruthuvi Maheshakya
[Dev] [ML] Spark K-means clustering on KDD cup 99 dataset
Hi all, I am currently working on fraud detection project. I was able to cluster the KDD cup 99 network anomaly detection dataset using apache spark k means algorithm. So far I was able to achieve 99% accuracy rate from this dataset.The steps I have followed during the process are mentioned below. - Separate the dataset into two parts (normal data and anomaly data) by filtering the label - Splits each two parts of data as follows - normal data - 65% - to train the model - 15% - to optimize the model by adjusting hyper parameters - 20% - to evaluate the model - anomaly data - 65% - no use - 15% - to optimize the model by adjusting hyper parameters - 20% - to evaluate the model - Prepossess the dataset - Drop out non numerical features since k means can only handle numerical values - Normalize all the values to 1-0 range - Cluster the 65% of normal data using Apache spark K means and build the model (15% of both normal and anomaly data were used to tune the hyper parameters such as k, percentile etc. to get an optimized model) - Finally evaluate the model using 20% of both normal and anomaly data. Method of identifying a fraud as follows, - When a new data point comes, get the closest cluster center by using k means predict function. - I have calculate 98th percentile distance for each cluster. (98 was the best value I got by tuning the model with different values) - Then I checked whether the distance of new data point with the given cluster center is less than or grater than the 98th percentile of that cluster. If it is less than the percentile it is considered as a normal data. If it is grater than the percentile it is considered as a fraud since it is in outside the cluster. Our next step is to integrate this feature to ML product and try out it with more realistic dataset. A summery of results I have obtained using 98th percentile during the process is attached with this. https://docs.google.com/a/wso2.com/spreadsheets/d/1E5fXk9CM31QEkyFCIEongh8KAa6jPeoY7OM3HraGPd4/edit?usp=sharing Thanks and Regards, Ashen -- *Ashen Weerathunga* Software Engineer - Intern WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: +94 716042995 94716042995 LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga http://lk.linkedin.com/in/ashenweerathunga* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ML] Spark K-means clustering on KDD cup 99 dataset
Hi all, This is the source code of the project. https://github.com/ashensw/Spark-KMeans-fraud-detection Best Regards, Ashen On Tue, Aug 25, 2015 at 2:00 PM, Ashen Weerathunga as...@wso2.com wrote: Thanks all for the suggestions, There are few assumptions I have made, - Clusters are uniform - Fraud data always will be outliers to the normal clusters - Clusters are not intersect with each other - I have given the number of Iterations as 100. So I assume that 100 iterations will be enough to make almost stable clusters @Maheshakya, In this dataset consist of higher amount of anomaly data than the normal data. But the practical scenario will be otherwise. Because of that It will be more unrealistic if I use those 65% of anomaly data to evaluate the model. The amount of normal data I used to build the model is also less than those 65% of anomaly data. Yes since our purpose is to detect anomalies It would be good to try with more anomaly data to evaluate the model.Thanks and I'll try to use them also. Best Regards, Ashen On Tue, Aug 25, 2015 at 12:35 PM, Maheshakya Wijewardena mahesha...@wso2.com wrote: Is there any particular reason why you are putting aside 65% of anomalous data at the evaluation? Since there is an obvious imbalance when the numbers of normal and abnormal cases are taken into account, you will get greater accuracy at the evaluation because a model tends to produce more accurate results for the class with the greater size. But it's not the case for the class of smaller size. With less number of records, it wont make much impact on the accuracy. Hence IMO, it would be better if you could evaluate with more anomalous data. i.e. number of records of each class needs to be roughly equal. Best regards On Tue, Aug 25, 2015 at 12:05 PM, CD Athuraliya chathur...@wso2.com wrote: Hi Ashen, It would be better if you can add the assumptions you make in this process (uniform clusters etc). It will make the process more clear IMO. Regards, CD On Tue, Aug 25, 2015 at 11:39 AM, Nirmal Fernando nir...@wso2.com wrote: Can we see the code too? On Tue, Aug 25, 2015 at 11:36 AM, Ashen Weerathunga as...@wso2.com wrote: Hi all, I am currently working on fraud detection project. I was able to cluster the KDD cup 99 network anomaly detection dataset using apache spark k means algorithm. So far I was able to achieve 99% accuracy rate from this dataset.The steps I have followed during the process are mentioned below. - Separate the dataset into two parts (normal data and anomaly data) by filtering the label - Splits each two parts of data as follows - normal data - 65% - to train the model - 15% - to optimize the model by adjusting hyper parameters - 20% - to evaluate the model - anomaly data - 65% - no use - 15% - to optimize the model by adjusting hyper parameters - 20% - to evaluate the model - Prepossess the dataset - Drop out non numerical features since k means can only handle numerical values - Normalize all the values to 1-0 range - Cluster the 65% of normal data using Apache spark K means and build the model (15% of both normal and anomaly data were used to tune the hyper parameters such as k, percentile etc. to get an optimized model) - Finally evaluate the model using 20% of both normal and anomaly data. Method of identifying a fraud as follows, - When a new data point comes, get the closest cluster center by using k means predict function. - I have calculate 98th percentile distance for each cluster. (98 was the best value I got by tuning the model with different values) - Then I checked whether the distance of new data point with the given cluster center is less than or grater than the 98th percentile of that cluster. If it is less than the percentile it is considered as a normal data. If it is grater than the percentile it is considered as a fraud since it is in outside the cluster. Our next step is to integrate this feature to ML product and try out it with more realistic dataset. A summery of results I have obtained using 98th percentile during the process is attached with this. https://docs.google.com/a/wso2.com/spreadsheets/d/1E5fXk9CM31QEkyFCIEongh8KAa6jPeoY7OM3HraGPd4/edit?usp=sharing Thanks and Regards, Ashen -- *Ashen Weerathunga* Software Engineer - Intern WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: +94 716042995 94716042995 LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga http://lk.linkedin.com/in/ashenweerathunga* -- Thanks regards, Nirmal Team Lead - WSO2 Machine Learner Associate Technical Lead - Data Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ -- *CD Athuraliya* Software Engineer WSO2, Inc. lean
Re: [Dev] [ML] Spark K-means clustering on KDD cup 99 dataset
Okay sure. On Tue, Aug 25, 2015 at 3:55 PM, Nirmal Fernando nir...@wso2.com wrote: Sure. @Ashen, can you please arrange one? On Tue, Aug 25, 2015 at 2:35 PM, Srinath Perera srin...@wso2.com wrote: Nirmal, Seshika, shall we do a code review? This code should go into ML after UI part is done. Thanks Srinath On Tue, Aug 25, 2015 at 2:20 PM, Ashen Weerathunga as...@wso2.com wrote: Hi all, This is the source code of the project. https://github.com/ashensw/Spark-KMeans-fraud-detection Best Regards, Ashen On Tue, Aug 25, 2015 at 2:00 PM, Ashen Weerathunga as...@wso2.com wrote: Thanks all for the suggestions, There are few assumptions I have made, - Clusters are uniform - Fraud data always will be outliers to the normal clusters - Clusters are not intersect with each other - I have given the number of Iterations as 100. So I assume that 100 iterations will be enough to make almost stable clusters @Maheshakya, In this dataset consist of higher amount of anomaly data than the normal data. But the practical scenario will be otherwise. Because of that It will be more unrealistic if I use those 65% of anomaly data to evaluate the model. The amount of normal data I used to build the model is also less than those 65% of anomaly data. Yes since our purpose is to detect anomalies It would be good to try with more anomaly data to evaluate the model.Thanks and I'll try to use them also. Best Regards, Ashen On Tue, Aug 25, 2015 at 12:35 PM, Maheshakya Wijewardena mahesha...@wso2.com wrote: Is there any particular reason why you are putting aside 65% of anomalous data at the evaluation? Since there is an obvious imbalance when the numbers of normal and abnormal cases are taken into account, you will get greater accuracy at the evaluation because a model tends to produce more accurate results for the class with the greater size. But it's not the case for the class of smaller size. With less number of records, it wont make much impact on the accuracy. Hence IMO, it would be better if you could evaluate with more anomalous data. i.e. number of records of each class needs to be roughly equal. Best regards On Tue, Aug 25, 2015 at 12:05 PM, CD Athuraliya chathur...@wso2.com wrote: Hi Ashen, It would be better if you can add the assumptions you make in this process (uniform clusters etc). It will make the process more clear IMO. Regards, CD On Tue, Aug 25, 2015 at 11:39 AM, Nirmal Fernando nir...@wso2.com wrote: Can we see the code too? On Tue, Aug 25, 2015 at 11:36 AM, Ashen Weerathunga as...@wso2.com wrote: Hi all, I am currently working on fraud detection project. I was able to cluster the KDD cup 99 network anomaly detection dataset using apache spark k means algorithm. So far I was able to achieve 99% accuracy rate from this dataset.The steps I have followed during the process are mentioned below. - Separate the dataset into two parts (normal data and anomaly data) by filtering the label - Splits each two parts of data as follows - normal data - 65% - to train the model - 15% - to optimize the model by adjusting hyper parameters - 20% - to evaluate the model - anomaly data - 65% - no use - 15% - to optimize the model by adjusting hyper parameters - 20% - to evaluate the model - Prepossess the dataset - Drop out non numerical features since k means can only handle numerical values - Normalize all the values to 1-0 range - Cluster the 65% of normal data using Apache spark K means and build the model (15% of both normal and anomaly data were used to tune the hyper parameters such as k, percentile etc. to get an optimized model) - Finally evaluate the model using 20% of both normal and anomaly data. Method of identifying a fraud as follows, - When a new data point comes, get the closest cluster center by using k means predict function. - I have calculate 98th percentile distance for each cluster. (98 was the best value I got by tuning the model with different values) - Then I checked whether the distance of new data point with the given cluster center is less than or grater than the 98th percentile of that cluster. If it is less than the percentile it is considered as a normal data. If it is grater than the percentile it is considered as a fraud since it is in outside the cluster. Our next step is to integrate this feature to ML product and try out it with more realistic dataset. A summery of results I have obtained using 98th percentile during the process is attached with this. https://docs.google.com/a/wso2.com/spreadsheets/d/1E5fXk9CM31QEkyFCIEongh8KAa6jPeoY7OM3HraGPd4/edit?usp=sharing Thanks and Regards, Ashen -- *Ashen Weerathunga* Software Engineer - Intern WSO2 Inc.: http://wso2.com
Re: [Dev] WSO2 Committers += CD Athuraliya
Congratulations!!! :) On Sat, Aug 1, 2015 at 6:21 AM, Sinnathamby Mahesan sinnatha...@wso2.com wrote: Congratulations CD! Best Wishes Mahesan On 31 July 2015 at 14:04, Nirmal Fernando nir...@wso2.com wrote: Hi All, It's my pleasure to announce *CD Athuraliya* as a *WSO2 Committer*. He has been a key contributor to the *WSO2 Machine Learner *Product and in recognition of his excellent work, he had been voted as a WSO2 Committer. Congratulations CD and keep up the good work! -- Thanks regards, Nirmal Associate Technical Lead - Data Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- ~~ Sinnathamby Mahesan ~~ ~~ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Ashen Weerathunga* Software Engineer - Intern WSO2 Inc.: http://wso2.com lean.enterprise.middleware Email: as...@wso2.com Mobile: +94 716042995 94716042995 LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga http://lk.linkedin.com/in/ashenweerathunga* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
