Re: [Architecture] [Iam-dev] [VOTE] Release WSO2 Identity Server 5.10.0 RC2
7 >>>>><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 > Architecture@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 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
[Architecture] WSO2 Identity Server 5.10.0-beta3 Released!
WSO2 Identity and Access Management team is pleased to announce the release of Identity Server 5.10.0 Beta3! <https://github.com/wso2/product-is/blob/master/release-guidelines.md#download> Download You can download WSO2 Identity Server 5.10.0 Beta3 from here <https://github.com/wso2/product-is/releases/download/v5.10.0-beta3/wso2is-5.10.0-beta3.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 in WSO2 Identity Server 5.10.0 Beta3 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/109?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 location: - IS Runtime <https://github.com/wso2/product-is/issues> <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: d...@wso2.org - Architecture List: architecture@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 ~ -- *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 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
[Architecture] WSO2 Identity Server 5.10.0-beta2 Released!
WSO2 Identity and Access Management team is pleased to announce the release of Identity Server 5.10.0 Beta2! <https://github.com/wso2/product-is/blob/master/release-guidelines.md#download> Download You can download WSO2 Identity Server 5.10.0 Beta2 from here <https://github.com/wso2/product-is/releases/download/v5.10.0-beta2/wso2is-5.10.0-beta2.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 in WSO2 Identity Server 5.10.0 Beta2 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/108?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 location: - IS Runtime <https://github.com/wso2/product-is/issues> <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: d...@wso2.org - Architecture List: architecture@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 ~ -- *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 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
[Architecture] WSO2 Identity Server 5.10.0-beta Released!
WSO2 Identity and Access Management team is pleased to announce the release of Identity Server 5.10.0 Beta! <https://github.com/wso2/product-is/blob/master/release-guidelines.md#download> Download You can download WSO2 Identity Server 5.10.0 Beta from here <https://github.com/wso2/product-is/releases/download/v5.10.0-beta/wso2is-5.10.0-beta.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 in WSO2 Identity Server 5.10.0 Beta 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/107?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 location: - IS Runtime <https://github.com/wso2/product-is/issues> <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: d...@wso2.org - Architecture List: architecture@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 ~ -- *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 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
[Architecture] WSO2 Identity Server 5.10.0-alpha3 Released!
WSO2 Identity and Access Management team is pleased to announce the release of Identity Server 5.10.0 Alpha3! <https://github.com/wso2/product-is/blob/master/release-guidelines.md#download> Download You can download WSO2 Identity Server 5.10.0 Alpha3 from here <https://github.com/wso2/product-is/releases/download/v5.10.0-alpha3/wso2is-5.10.0-alpha3.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 in WSO2 Identity Server 5.10.0 Alpha3 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/106?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 location: - IS Runtime <https://github.com/wso2/product-is/issues> <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: d...@wso2.org - Architecture List: architecture@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 ~ -- *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 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
[Architecture] WSO2 Identity Server 5.10.0-alpha2 Released!
WSO2 Identity and Access Management team is pleased to announce the release of Identity Server 5.10.0 Alpha2! <https://github.com/wso2/product-is/blob/master/release-guidelines.md#download> Download You can download WSO2 Identity Server 5.10.0 Alpha2 from here <https://github.com/wso2/product-is/releases/download/v5.10.0-alpha2/wso2is-5.10.0-alpha2.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 in WSO2 Identity Server 5.10.0 Alpha2 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/105?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 location: - IS Runtime <https://github.com/wso2/product-is/issues> <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: d...@wso2.org - Architecture List: architecture@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 ~ -- *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 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
[Architecture] WSO2 Identity Server 5.10.0-alpha Released!
WSO2 Identity and Access Management team is pleased to announce the release of Identity Server 5.10.0 Alpha! <https://github.com/wso2/product-is/blob/master/release-guidelines.md#download> Download You can download WSO2 Identity Server 5.10.0 Alpha from here <https://github.com/wso2/product-is/releases/download/v5.10.0-alpha/wso2is-5.10.0-alpha.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 in WSO2 Identity Server 5.10.0 Alpha 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/104?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 location: - IS Runtime <https://github.com/wso2/product-is/issues> <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: d...@wso2.org - Architecture List: architecture@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 ~ -- *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 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
[Architecture] WSO2 Identity Server 5.10.0 M9 Released!
WSO2 Identity and Access Management team is pleased to announce the release of Identity Server 5.10.0 M9! <https://github.com/wso2/product-is/blob/master/release-guidelines.md#download> Download You can download WSO2 Identity Server 5.10.0 M9 from here <https://github.com/wso2/product-is/releases/download/v5.10.0-m9/wso2is-5.10.0-m9.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 in WSO2 Identity Server 5.10.0 M9 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/103?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 location: - IS Runtime <https://github.com/wso2/product-is/issues> <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: d...@wso2.org - Architecture List: architecture@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 ~ -- *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 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
[Architecture] WSO2 Identity Server 5.10.0 M8 Released!
WSO2 Identity and Access Management team is pleased to announce the release of Identity Server 5.10.0 M8! <https://github.com/wso2/product-is/blob/master/release-guidelines.md#download> Download You can download WSO2 Identity Server 5.10.0 M8 from, here <https://github.com/wso2/product-is/releases/download/v5.10.0-m8/wso2is-5.10.0-m8.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 in WSO2 Identity Server 5.10.0 M8 A list of all the new features and bug fixes shipped with this release can be found from, here <https://github.com/wso2/product-is/milestone/102?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 location: - IS Runtime <https://github.com/wso2/product-is/issues> <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: d...@wso2.org - Architecture List: architecture@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 ~ -- *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 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [IAM][IS 5.10.0] REST APIs For Federated Associations Of The User
+Adding to the above as discussed in [1] Considering this requirement, we will add the following user attributes(if > exists), to the */me/association GET* response. This approach is used, to have *only* a limited number of user-friendly attributes(sp: considering scenarios like user portals) and it was decided that the given three attributes(first name, last name, and email) satisfies this condition. Other than that,* to get any other user attribute*, the switch grant must be used. [1] "Updated invitation with note: [Discussion] Calling REST APIs On Behalf Of Associated User @ Thu Nov 21, 2019 11:30am - 12:30pm (IST) (WSO2 Engineering Group)" Regards, Tharindu. On Thu, Nov 21, 2019 at 5:16 PM Tharindu Bandara wrote: > Hi all, > > >>- Returning user attributes with the */me/association GET* response >>is not suitable considering the API path. Therefore, the user ID of the >>associated user returned from this response will be used to call SCIM >>APIs(or any similar API to retrieve user attributes) to get user >> attributes >>of the associated user. >> >> >>- There might be some authorization issues with the existing >> implementation with this approach(Ex: The user portal is trying to call >> SCIM APIs for the associated user's attributes, with the currently >> authenticated user). But these issues need to be solved from the >> authorization level, as associated users are basically the same user, >> therefore anyone should have the privilege to retrieve their associated >> user attributes. >> >> For this requirement, we have decided to go with a switch grant type, > which will provide a token for an associated user. > > But having a limited set of user attributes in the */me/association GET* > response > could actually be a better option, given that the switching and getting a > token might decrease the performance when there is a large number of > switching to be done. > > For example, if a user portal needs to display all the associated user > accounts of the logged-in user, it needs user-friendly attributes > representing the associated accounts. In this case, if the */me/association > GET* response contains attributes like first name and last name, that > would be a better approach, other than obtaining tokens for each associated > user, then call SCIM */me* endpoint to obtain these attributes. > > Considering this requirement, we will add the following user attributes(if > exists), to the */me/association GET* response. > >- First name >- Last name > - Email > > [1] "[IAM] Calling REST APIs On-behalf Of My Associated Accounts"@ > architecture-gr...@wso2.com > > Regards, > Tharindu. > > On Wed, Nov 6, 2019 at 11:23 AM Tharindu Bandara > wrote: > >> Hi all, >> >> We had a review meeting[1] yesterday and the following were discussed. >> >> *Participants: *+Ruwan Abeykoon +Isura Karunaratne >> +Thanuja Jayasinghe +Maduranga >> Siriwardena +Farasath Ahamed * >> +Tharindu >> Bandara * >> >>- Returning user attributes with the */me/association GET* response >>is not suitable considering the API path. Therefore, the user ID of the >>associated user returned from this response will be used to call SCIM >>APIs(or any similar API to retrieve user attributes) to get user >> attributes >>of the associated user. >> - There might be some authorization issues with the existing >> implementation with this approach(Ex: The user portal is trying to call >> SCIM APIs for the associated user's attributes, with the currently >> authenticated user). But these issues need to be solved from the >> authorization level, as associated users are basically the same user, >> therefore anyone should have the privilege to retrieve their associated >> user attributes. >>- The existing implementation for the federated associations is, the >>UserProfileAdmin admin service in the identity-framework handles all the >>API calls regarding the federated associations by directly calling the DAO >>layer. It lacks an OSGi service between the admin service and the DAO >> layer >>for federated associations. >> - A new OSGi service will be introduced in the framework with >> this effort, which will contain APIs to handle federated associations. >> - UserProfileAdmin service will be refactored to call the above >> OSGi service. >> - The associations REST APIs will call the same OSGi service in >> the framewor
Re: [Architecture] [IAM][IS 5.10.0] REST APIs For Federated Associations Of The User
Hi all,
>- Returning user attributes with the */me/association GET* response is
>not suitable considering the API path. Therefore, the user ID of the
>associated user returned from this response will be used to call SCIM
>APIs(or any similar API to retrieve user attributes) to get user attributes
>of the associated user.
>
>
>- There might be some authorization issues with the existing
> implementation with this approach(Ex: The user portal is trying to call
> SCIM APIs for the associated user's attributes, with the currently
> authenticated user). But these issues need to be solved from the
> authorization level, as associated users are basically the same user,
> therefore anyone should have the privilege to retrieve their associated
> user attributes.
>
> For this requirement, we have decided to go with a switch grant type,
which will provide a token for an associated user.
But having a limited set of user attributes in the */me/association
GET* response
could actually be a better option, given that the switching and getting a
token might decrease the performance when there is a large number of
switching to be done.
For example, if a user portal needs to display all the associated user
accounts of the logged-in user, it needs user-friendly attributes
representing the associated accounts. In this case, if the */me/association
GET* response contains attributes like first name and last name, that would
be a better approach, other than obtaining tokens for each associated user,
then call SCIM */me* endpoint to obtain these attributes.
Considering this requirement, we will add the following user attributes(if
exists), to the */me/association GET* response.
- First name
- Last name
- Email
[1] "[IAM] Calling REST APIs On-behalf Of My Associated Accounts"@
architecture-gr...@wso2.com
Regards,
Tharindu.
On Wed, Nov 6, 2019 at 11:23 AM Tharindu Bandara wrote:
> Hi all,
>
> We had a review meeting[1] yesterday and the following were discussed.
>
> *Participants: *+Ruwan Abeykoon +Isura Karunaratne
> +Thanuja Jayasinghe +Maduranga
> Siriwardena +Farasath Ahamed *
> +Tharindu
> Bandara *
>
>- Returning user attributes with the */me/association GET* response is
>not suitable considering the API path. Therefore, the user ID of the
>associated user returned from this response will be used to call SCIM
>APIs(or any similar API to retrieve user attributes) to get user attributes
>of the associated user.
> - There might be some authorization issues with the existing
> implementation with this approach(Ex: The user portal is trying to call
> SCIM APIs for the associated user's attributes, with the currently
> authenticated user). But these issues need to be solved from the
> authorization level, as associated users are basically the same user,
> therefore anyone should have the privilege to retrieve their associated
> user attributes.
>- The existing implementation for the federated associations is, the
>UserProfileAdmin admin service in the identity-framework handles all the
>API calls regarding the federated associations by directly calling the DAO
>layer. It lacks an OSGi service between the admin service and the DAO layer
>for federated associations.
> - A new OSGi service will be introduced in the framework with this
> effort, which will contain APIs to handle federated associations.
> - UserProfileAdmin service will be refactored to call the above
> OSGi service.
> - The associations REST APIs will call the same OSGi service in the
> framework for federated associations related APIs.
>
> [1] "Invitation: [Code Review] Federation Association REST APIs @ Tue Nov
> 5, 2019 3:30pm - 4:30pm (IST) (WSO2 Engineering Group)"@engineering-group
>
> Regards,
> Tharindu.
>
> On Mon, Nov 4, 2019 at 6:08 PM Tharindu Bandara
> wrote:
>
>> Hi all,
>>
>> We had an offline discussion today with +Ishara Karunarathna
>> +Malithi Edirisinghe +Darshana
>> Gunawardana +Isura Karunaratne
>> +Tharindu
>> Bandara . According to the discussion, it was
>> decided that the */{user-id}/association *and
>> */{user-id}/federated-association
>> *POST requests are not needed for this API, as such use case of allowing
>> an admin user to associate local/federated account with another is not
>> needed. I will remove these admin APIs from the APIs[1].
>>
>> [1] https://app.swaggerhub.com/apis/WSO8/association/v1
>>
>> Thanks,
>> Tharindu.
>>
>> On Wed, Oct 30, 2019 at 6:51 PM Tharindu Bandara
>> wrote:
>>
>>> Hi
Re: [Architecture] [IAM] Calling REST APIs On-behalf Of My Associated Accounts
Hi all, We had an offline meeting with +Darshana Gunawardana +Ishara Karunarathna +Isura Karunaratne +Maduranga Siriwardena +Thanuja Jayasinghe +Farasath Ahamed , regarding the concern raised by Darshana. We have discussed the following. Changing the authorized user dynamically will be a custom approach that > will not work with any other resource server other than for the IS product > APIs. Therefore, fixing the authentication valve and using the header to call REST APIs on behalf of the associated user approach is not suitable. Since we have introduced a new grant type to switch and get tokens on behalf of the associated user, an appropriate way of doing this requirement is to get a new access token via the switch grant, then call REST APIs as required. Therefore, we will not be making any changes with the authentication valve to fulfill this requirement, but going with the above-approach using the switch grant. Regards, Tharindu. On Wed, Nov 20, 2019 at 10:50 AM Darshana Gunawardana wrote: > Hi Tharindu, > > IMO, we should keep the authorization at API level (resource server level) > simple as possible. And expect a token that have permission to access a > protected resource on behalf of a user. Changing the authorized user > dynamically will be a custom approach that will not work with any other > resource server other than for the IS product APIs. > > If the client wants to access API for any other user, it should, first > obtain a new access token that have permission to access a protected > resource on behalf of the new user and then invoke APIs with the new access > token. This way any resource server can be used to integrate with the > client, rather limiting to IS product APIs. > > When obtaining the new access token, authorization server can use the > context details like, > >- What's the existing LOA when obtained when issuing the previous >token as the user: *john* >- Any association details that user: *john* has >- The LOA that need to access requested resources for the new user: >*ben* > > and authorize the user with the required level and get the other details > like user consent, or any missing details etc. > > So, I'm -1 to go with suggested approach and if we have a specific need to > pull some more details of the associated users, we can fix those at the API > level. > > WDYT? > > Thanks, > > On Mon, Nov 18, 2019 at 6:58 PM Tharindu Bandara > wrote: > >> Hi all, >> >> Imagine my user account in WSO2 Identity Server is *john*. I have also >> one other associated user account in the identity server under the name, >> *ben*. >> >> I use an application, which shows all my user accounts in the identity >> server once I successfully logged in. >> >> As of now, the above scenario can be done successfully. The application >> can call the WSO2 Identity Server user account association APIs and list >> all the associated accounts on-behalf of me(once I logged in). >> >> But I want to see some of my attributes of the associated accounts(Ex: >> email addresses). This should be possible in a way that the application >> calls WSO2 IS SCIM APIs on-behalf of my associated accounts, then retrieve >> any attributes, without me logging in as each associated user(Ex: When I >> log in as *john*, the email address of *ben* should be shown by the >> application). >> >> The idea here is that all my associated accounts are essentially mine, >> therefore once logged in as a user, any of the subsequent REST API calls >> on-behalf of any associated user account, should be allowed. >> >> Please find the corresponding public JIRA >> <https://github.com/wso2/product-is/issues/6882>[2]. >> >> I had an initial discussion on this with +Isura Karunaratne >> . Based on that, I have implemented the following >> approach. >> >> We will introduce a new header called "AssociatedUserId". If this header >> is present for a REST API call, the authentication valve is responsible to >> read the fully qualified name of the associated user sent with this header. >> Then if a valid association exists with the authenticated user, the >> authentication valve will set the associated user in the carbon context, >> instead of the authenticated user, during the post-authentication stage. >> This will make sure that the REST API call is called on-behalf of the >> associated user identified with the above-mentioned header. >> >> Please find the pull request >> <https://github.com/wso2-extensions/identity-carbon-auth-rest/pull/92>[3] >> with this approach. >> >> Your valuable feedback is highly apprecia
[Architecture] [IAM] Calling REST APIs On-behalf Of My Associated Accounts
Hi all, Imagine my user account in WSO2 Identity Server is *john*. I have also one other associated user account in the identity server under the name, *ben*. I use an application, which shows all my user accounts in the identity server once I successfully logged in. As of now, the above scenario can be done successfully. The application can call the WSO2 Identity Server user account association APIs and list all the associated accounts on-behalf of me(once I logged in). But I want to see some of my attributes of the associated accounts(Ex: email addresses). This should be possible in a way that the application calls WSO2 IS SCIM APIs on-behalf of my associated accounts, then retrieve any attributes, without me logging in as each associated user(Ex: When I log in as *john*, the email address of *ben* should be shown by the application). The idea here is that all my associated accounts are essentially mine, therefore once logged in as a user, any of the subsequent REST API calls on-behalf of any associated user account, should be allowed. Please find the corresponding public JIRA <https://github.com/wso2/product-is/issues/6882>[2]. I had an initial discussion on this with +Isura Karunaratne . Based on that, I have implemented the following approach. We will introduce a new header called "AssociatedUserId". If this header is present for a REST API call, the authentication valve is responsible to read the fully qualified name of the associated user sent with this header. Then if a valid association exists with the authenticated user, the authentication valve will set the associated user in the carbon context, instead of the authenticated user, during the post-authentication stage. This will make sure that the REST API call is called on-behalf of the associated user identified with the above-mentioned header. Please find the pull request <https://github.com/wso2-extensions/identity-carbon-auth-rest/pull/92>[3] with this approach. Your valuable feedback is highly appreciated. PS: This requirement initially discussed at [1]. [1] "[IAM][IS 5.10.0] REST APIs For Federated Associations Of The User"@architecture-group [2] https://github.com/wso2/product-is/issues/6882 [3] https://github.com/wso2-extensions/identity-carbon-auth-rest/pull/92 Regards, Tharindu. -- *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 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [IAM][IS 5.10.0] REST APIs For Federated Associations Of The User
Hi all,
We had a review meeting[1] yesterday and the following were discussed.
*Participants: *+Ruwan Abeykoon +Isura Karunaratne
+Thanuja Jayasinghe +Maduranga
Siriwardena +Farasath Ahamed
* +Tharindu
Bandara *
- Returning user attributes with the */me/association GET* response is
not suitable considering the API path. Therefore, the user ID of the
associated user returned from this response will be used to call SCIM
APIs(or any similar API to retrieve user attributes) to get user attributes
of the associated user.
- There might be some authorization issues with the existing
implementation with this approach(Ex: The user portal is trying to call
SCIM APIs for the associated user's attributes, with the currently
authenticated user). But these issues need to be solved from the
authorization level, as associated users are basically the same user,
therefore anyone should have the privilege to retrieve their associated
user attributes.
- The existing implementation for the federated associations is, the
UserProfileAdmin admin service in the identity-framework handles all the
API calls regarding the federated associations by directly calling the DAO
layer. It lacks an OSGi service between the admin service and the DAO layer
for federated associations.
- A new OSGi service will be introduced in the framework with this
effort, which will contain APIs to handle federated associations.
- UserProfileAdmin service will be refactored to call the above OSGi
service.
- The associations REST APIs will call the same OSGi service in the
framework for federated associations related APIs.
[1] "Invitation: [Code Review] Federation Association REST APIs @ Tue Nov
5, 2019 3:30pm - 4:30pm (IST) (WSO2 Engineering Group)"@engineering-group
Regards,
Tharindu.
On Mon, Nov 4, 2019 at 6:08 PM Tharindu Bandara wrote:
> Hi all,
>
> We had an offline discussion today with +Ishara Karunarathna
> +Malithi Edirisinghe +Darshana
> Gunawardana +Isura Karunaratne +Tharindu
> Bandara . According to the discussion, it was
> decided that the */{user-id}/association *and
> */{user-id}/federated-association
> *POST requests are not needed for this API, as such use case of allowing
> an admin user to associate local/federated account with another is not
> needed. I will remove these admin APIs from the APIs[1].
>
> [1] https://app.swaggerhub.com/apis/WSO8/association/v1
>
> Thanks,
> Tharindu.
>
> On Wed, Oct 30, 2019 at 6:51 PM Tharindu Bandara
> wrote:
>
>> Hi all,
>>
>> Today we had a review meeting[1] to finalize the swagger API
>> definition[2]. Please find the meeting notes below.
>>
>> *Participants:* +Thanuja Jayasinghe +Isura Karunaratne
>> +Tharindu Bandara
>>
>> *Notes:*
>>
>>- *[GET] : /me/associations *
>> - This API returns a list of associated users. For an associated
>> user, we would need the associated user's attributes. Therefore the
>> possibility of retrieving user attributes requested via query params
>> should
>> be considered.
>>- *[DELETE] : /me/federated-associations/{id}, [DELETE]
>>: /{user-id}/federated-associations/{id}, [DELETE]
>>: /me/associations/{user-id}*
>>- These new APIs will be added to support deleting a given
>> association.
>> - The *{id} *parameter in the above should be a UUID for a
>> federated association. As of now, all the federated associations are
>> stored
>> in "IDN_ASSOCIATED_ID" table, which does not have a unique
>> identifier for an association. Therefore a new column will be added to
>> the
>> table "IDN_ASSOCIATED_ID" to have a UUID for an association entry.
>> - The *{user-id} *parameter in above is the UUID for the user.
>> Which would be the same Id in the* GET /me/association* response.
>>
>> [1] "Invitation: [Federated User Account Association REST APIs] API
>> Review @ Wed Oct 30, 2019 4:30pm - 5:30pm (IST) (WSO2 Engineering Group)"
>> [2] https://app.swaggerhub.com/apis/WSO8/association/v1
>>
>> Regards,
>> Tharindu.
>>
>> On Wed, Oct 30, 2019 at 1:10 PM Tharindu Bandara
>> wrote:
>>
>>> Hi Darshana,
>>>
>>> Why do we need the,
>>>>
>>>>- [POST] : /{user-id}/federated-associations
>>>>
>>>> The same API is available for the local account association. Now for
>>> the federated account scenario, we grant this capability to an admin user,
>>> as an admin API.
>>>
>>> We cannot provide a */me *API for this cap
Re: [Architecture] [IAM][IS 5.10.0] REST APIs For Federated Associations Of The User
Hi all,
We had an offline discussion today with +Ishara Karunarathna
+Malithi Edirisinghe +Darshana
Gunawardana +Isura Karunaratne +Tharindu
Bandara . According to the discussion, it was decided
that the */{user-id}/association *and */{user-id}/federated-association *POST
requests are not needed for this API, as such use case of allowing an admin
user to associate local/federated account with another is not needed. I
will remove these admin APIs from the APIs[1].
[1] https://app.swaggerhub.com/apis/WSO8/association/v1
Thanks,
Tharindu.
On Wed, Oct 30, 2019 at 6:51 PM Tharindu Bandara wrote:
> Hi all,
>
> Today we had a review meeting[1] to finalize the swagger API
> definition[2]. Please find the meeting notes below.
>
> *Participants:* +Thanuja Jayasinghe +Isura Karunaratne
> +Tharindu Bandara
>
> *Notes:*
>
>- *[GET] : /me/associations *
> - This API returns a list of associated users. For an associated
> user, we would need the associated user's attributes. Therefore the
> possibility of retrieving user attributes requested via query params
> should
> be considered.
>- *[DELETE] : /me/federated-associations/{id}, [DELETE]
>: /{user-id}/federated-associations/{id}, [DELETE]
>: /me/associations/{user-id}*
>- These new APIs will be added to support deleting a given association.
> - The *{id} *parameter in the above should be a UUID for a
> federated association. As of now, all the federated associations are
> stored
> in "IDN_ASSOCIATED_ID" table, which does not have a unique
> identifier for an association. Therefore a new column will be added to
> the
> table "IDN_ASSOCIATED_ID" to have a UUID for an association entry.
> - The *{user-id} *parameter in above is the UUID for the user.
> Which would be the same Id in the* GET /me/association* response.
>
> [1] "Invitation: [Federated User Account Association REST APIs] API Review
> @ Wed Oct 30, 2019 4:30pm - 5:30pm (IST) (WSO2 Engineering Group)"
> [2] https://app.swaggerhub.com/apis/WSO8/association/v1
>
> Regards,
> Tharindu.
>
> On Wed, Oct 30, 2019 at 1:10 PM Tharindu Bandara
> wrote:
>
>> Hi Darshana,
>>
>> Why do we need the,
>>>
>>>- [POST] : /{user-id}/federated-associations
>>>
>>> The same API is available for the local account association. Now for
>> the federated account scenario, we grant this capability to an admin user,
>> as an admin API.
>>
>> We cannot provide a */me *API for this capability, as any user would be
>> able to associate any federated account with his account. This was the
>> concern raised earlier by +Isura Karunaratne .
>>
>> The idea behind this approach is as a privileged user, an admin is able
>> to associate both local and a *federated* accounts to a given user.
>>
>> Regards,
>> Tharindu.
>>
>> On Wed, Oct 30, 2019 at 12:55 PM Darshana Gunawardana
>> wrote:
>>
>>> Hi Isura\Tharindu,
>>>
>>> Why do we need the,
>>>>
>>>>
>>>>- [POST] : /{user-id}/federated-associations
>>>>
>>>>
>>> Thanks,
>>>
>>> On Wed, Oct 30, 2019 at 10:00 AM Tharindu Bandara
>>> wrote:
>>>
>>>> Hi Isura,
>>>>
>>>> I think this API is not required. If this is supported, anyone can
>>>>> associate federated accounts without authentication. That can cause a
>>>>> security issue.
>>>>>
>>>>
>>>> +1. I will remove the [POST] : /me/federated-associations API.
>>>>
>>>> Regards,
>>>> --
>>>> *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
>>>>
>>>
>>>
>>> --
>>> Regards,
>>>
>>>
>>> *Darshana Gunawardana*Technical Lead
>>> WSO2 Inc.; http://wso2.com
>>>
>>> *E-mail: darsh...@wso2.com *
>>> *Mobile: +94718566859*Lean . Enterprise . Middleware
>>>
>>
>>
>> --
>> *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
>>
>
>
> --
> *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
>
--
*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
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [IAM][IS 5.10.0] REST APIs For Federated Associations Of The User
Hi all,
Today we had a review meeting[1] to finalize the swagger API definition[2].
Please find the meeting notes below.
*Participants:* +Thanuja Jayasinghe +Isura Karunaratne
+Tharindu Bandara
*Notes:*
- *[GET] : /me/associations *
- This API returns a list of associated users. For an associated
user, we would need the associated user's attributes. Therefore the
possibility of retrieving user attributes requested via query
params should
be considered.
- *[DELETE] : /me/federated-associations/{id}, [DELETE]
: /{user-id}/federated-associations/{id}, [DELETE]
: /me/associations/{user-id}*
- These new APIs will be added to support deleting a given association.
- The *{id} *parameter in the above should be a UUID for a federated
association. As of now, all the federated associations are stored in "
IDN_ASSOCIATED_ID" table, which does not have a unique identifier for
an association. Therefore a new column will be added to the table "
IDN_ASSOCIATED_ID" to have a UUID for an association entry.
- The *{user-id} *parameter in above is the UUID for the user. Which
would be the same Id in the* GET /me/association* response.
[1] "Invitation: [Federated User Account Association REST APIs] API Review
@ Wed Oct 30, 2019 4:30pm - 5:30pm (IST) (WSO2 Engineering Group)"
[2] https://app.swaggerhub.com/apis/WSO8/association/v1
Regards,
Tharindu.
On Wed, Oct 30, 2019 at 1:10 PM Tharindu Bandara wrote:
> Hi Darshana,
>
> Why do we need the,
>>
>>- [POST] : /{user-id}/federated-associations
>>
>> The same API is available for the local account association. Now for
> the federated account scenario, we grant this capability to an admin user,
> as an admin API.
>
> We cannot provide a */me *API for this capability, as any user would be
> able to associate any federated account with his account. This was the
> concern raised earlier by +Isura Karunaratne .
>
> The idea behind this approach is as a privileged user, an admin is able to
> associate both local and a *federated* accounts to a given user.
>
> Regards,
> Tharindu.
>
> On Wed, Oct 30, 2019 at 12:55 PM Darshana Gunawardana
> wrote:
>
>> Hi Isura\Tharindu,
>>
>> Why do we need the,
>>>
>>>
>>>- [POST] : /{user-id}/federated-associations
>>>
>>>
>> Thanks,
>>
>> On Wed, Oct 30, 2019 at 10:00 AM Tharindu Bandara
>> wrote:
>>
>>> Hi Isura,
>>>
>>> I think this API is not required. If this is supported, anyone can
>>>> associate federated accounts without authentication. That can cause a
>>>> security issue.
>>>>
>>>
>>> +1. I will remove the [POST] : /me/federated-associations API.
>>>
>>> Regards,
>>> --
>>> *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
>>>
>>
>>
>> --
>> Regards,
>>
>>
>> *Darshana Gunawardana*Technical Lead
>> WSO2 Inc.; http://wso2.com
>>
>> *E-mail: darsh...@wso2.com *
>> *Mobile: +94718566859*Lean . Enterprise . Middleware
>>
>
>
> --
> *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
>
--
*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
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [IAM][IS 5.10.0] REST APIs For Federated Associations Of The User
Hi Darshana,
Why do we need the,
>
>- [POST] : /{user-id}/federated-associations
>
> The same API is available for the local account association. Now for
the federated account scenario, we grant this capability to an admin user,
as an admin API.
We cannot provide a */me *API for this capability, as any user would be
able to associate any federated account with his account. This was the
concern raised earlier by +Isura Karunaratne .
The idea behind this approach is as a privileged user, an admin is able to
associate both local and a *federated* accounts to a given user.
Regards,
Tharindu.
On Wed, Oct 30, 2019 at 12:55 PM Darshana Gunawardana
wrote:
> Hi Isura\Tharindu,
>
> Why do we need the,
>>
>>
>>- [POST] : /{user-id}/federated-associations
>>
>>
> Thanks,
>
> On Wed, Oct 30, 2019 at 10:00 AM Tharindu Bandara
> wrote:
>
>> Hi Isura,
>>
>> I think this API is not required. If this is supported, anyone can
>>> associate federated accounts without authentication. That can cause a
>>> security issue.
>>>
>>
>> +1. I will remove the [POST] : /me/federated-associations API.
>>
>> Regards,
>> --
>> *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
>>
>
>
> --
> Regards,
>
>
> *Darshana Gunawardana*Technical Lead
> WSO2 Inc.; http://wso2.com
>
> *E-mail: darsh...@wso2.com *
> *Mobile: +94718566859*Lean . Enterprise . Middleware
>
--
*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
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [IAM][IS 5.10.0] REST APIs For Federated Associations Of The User
Hi Isura, I think this API is not required. If this is supported, anyone can > associate federated accounts without authentication. That can cause a > security issue. > +1. I will remove the [POST] : /me/federated-associations API. Regards, -- *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 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [IAM][IS 5.10.0] REST APIs For Federated Associations Of The User
Hi, Darshana/All,
If we are doing any backend changes for this API, I suggest to do those in
> identity-user-account-association[1], not in UserProfileAdmin.
+1. I have initially planned to re-use UserProfileAdmin as it seemed to
serve all the requirements thus we would not do the backend changes. But
alongside with the concern raised by @Farasath Ahamed in
[2], I will move the backend implementation to the
identity-user-account-association[1] as this would be a much cleaner
approach.
To give an update on the progress,
I have added two more APIs to create federated associations.
- [POST] : /me/federated-associations
- Associate a federated user to the authenticated user.
- [POST] : /{user-id}/federated-associations
- Associate Federated users
Please find the swagger definition[3] of the improved API which will be
updated along the way.
[1] https://github.com/wso2-extensions/identity-user-account-association
[2]
https://github.com/wso2/carbon-identity-framework/pull/2499#discussion_r339903378
[3] https://app.swaggerhub.com/apis/WSO8/association/v1
Regards,
Tharindu.
On Tue, Oct 29, 2019 at 11:52 AM Darshana Gunawardana
wrote:
> If we are doing any backend changes for this API, I suggest to do those in
> identity-user-account-association[1], not in UserProfileAdmin.
>
> [1] https://github.com/wso2-extensions/identity-user-account-association
>
> Thanks,
>
> On Tue, Oct 29, 2019 at 11:41 AM Tharindu Bandara
> wrote:
>
>> Hi all,
>>
>> WSO2 Identity Server has REST APIs for user account associations[1]. As
>> of now these APIs provide the capability to work with local user account
>> associations and do not support federated user account associations.
>>
>> I have been working on this to support federated user account
>> associations with the User Account Associations API[1]. As planned, the
>> following APIs will be added with this effort.
>>
>>- [GET] : /me/federated-associations
>> - Retrieve the federated associations of the authenticated user.
>>- [GET] : /{user-id}/federated-associations
>> - Get user's federated associations
>> - [DELETE] : /me/federated-associations
>> - Delete all my federated user associations
>> - [DELETE] : /{user-id}/federated-associations
>>- Delete user's all user federated associations
>>
>> I am also evaluating the possibility of adding an API to create federated
>> associations. I will update this thread with the progress.
>>
>> The internal implementation for the above APIs will use the
>> UserProfileAdmin[2] underneath(The UserProfileAdmin[2] is used by the
>> UserProfileMgtService) through the OSGi framework. In the early
>> discussions, we have tested registering the UserProfileAdmin[2] directly as
>> an OSGi service, but we will discuss it further to find the optimum
>> approach.
>>
>> Please provide your valuable feedback on this.
>>
>> [1] https://is.docs.wso2.com/en/next/develop/association-rest-api/#/
>> [2]
>> https://github.com/wso2/carbon-identity-framework/blob/master/components/user-mgt/org.wso2.carbon.identity.user.profile/src/main/java/org/wso2/carbon/identity/user/profile/mgt/UserProfileAdmin.java
>>
>> Regards,
>> --
>> *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
>>
>
>
> --
> Regards,
>
>
> *Darshana Gunawardana*Technical Lead
> WSO2 Inc.; http://wso2.com
>
> *E-mail: darsh...@wso2.com *
> *Mobile: +94718566859*Lean . Enterprise . Middleware
>
--
*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
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
[Architecture] [IAM][IS 5.10.0] REST APIs For Federated Associations Of The User
Hi all,
WSO2 Identity Server has REST APIs for user account associations[1]. As of
now these APIs provide the capability to work with local user account
associations and do not support federated user account associations.
I have been working on this to support federated user account associations
with the User Account Associations API[1]. As planned, the following APIs
will be added with this effort.
- [GET] : /me/federated-associations
- Retrieve the federated associations of the authenticated user.
- [GET] : /{user-id}/federated-associations
- Get user's federated associations
- [DELETE] : /me/federated-associations
- Delete all my federated user associations
- [DELETE] : /{user-id}/federated-associations
- Delete user's all user federated associations
I am also evaluating the possibility of adding an API to create federated
associations. I will update this thread with the progress.
The internal implementation for the above APIs will use the
UserProfileAdmin[2] underneath(The UserProfileAdmin[2] is used by the
UserProfileMgtService) through the OSGi framework. In the early
discussions, we have tested registering the UserProfileAdmin[2] directly as
an OSGi service, but we will discuss it further to find the optimum
approach.
Please provide your valuable feedback on this.
[1] https://is.docs.wso2.com/en/next/develop/association-rest-api/#/
[2]
https://github.com/wso2/carbon-identity-framework/blob/master/components/user-mgt/org.wso2.carbon.identity.user.profile/src/main/java/org/wso2/carbon/identity/user/profile/mgt/UserProfileAdmin.java
Regards,
--
*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
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] WSO2 Identity Server 5.10.0 M3 Released!
+Correction On Fri, Oct 25, 2019 at 5:49 PM Tharindu Bandara wrote: > WSO2 Identity and Access Management team is pleased to announce the > release of Identity Server 5.10.0 M3! > Download > > You can download WSO2 Identity Server 5.9.0 M3 from here > <https://github.com/wso2/product-is/releases/download/v5.10.0-m3/wso2is-5.10.0-m3.zip> > . > "WSO2 Identity Server 5.9.0 M3" needs to be changed to "WSO2 Identity Server 5.10.0 M3" Regards, -- *Tharindu Bandara* 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 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
[Architecture] WSO2 Identity Server 5.10.0 M3 Released!
WSO2 Identity and Access Management team is pleased to announce the release of Identity Server 5.10.0 M3! Download You can download WSO2 Identity Server 5.9.0 M3 from here <https://github.com/wso2/product-is/releases/download/v5.10.0-m3/wso2is-5.10.0-m3.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.10.0 M3 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/97?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> 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: d...@wso2.org - Architecture List: architecture@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 ~ -- *Tharindu Bandara* 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 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Maintaining IS-Archetypes
Hi all, Find the best approach to maintain the archetypes (in a single repo or > inside the feature repo). Shall we finalize on the approach to maintain the archetypes? This would be helpful to proceed with the effort [1]. [1] "[IS] Maven Archetype for Custom Event Handlers" Thanks, Tharindu. On Mon, Aug 5, 2019 at 10:40 AM Kanapriya Kuleswararajan wrote: > In the repo [1] we have archetypes for IS extensions and seems they are > outdated as it still uses the old dependency of carbon-identity. This need > to be improved/refactor in order to make this to a stable with the latest > product version. > > BTW, we couldn't see any specific reason to have all archetypes here under > the repo [1]. Hence we thought to move all the IS-related archetypes > >- To a separate repo? But here we have to decide, how we are going to >maintain the releases (major or minor) if we have all the archetypes in the >same repo? In this way, there can be chances that some archetypes get >released unnecessary (ie, without any changes). >- Or else we can keep the archetypes inside the feature repo itself? > > Appreciate your valuable suggestions on the above? > > Further, In this effort, we (myself and @Inthi) are planning the following > as the initial step: > >- Refactor the existing archetypes and Making that to work with IS >5.8.0 for now. >- Find the best approach to maintain the archetypes (in a single repo >or inside the feature repo). >- Add more archetypes as part of this effort. We could see a couple of >archetypes already developed, but that need to be reviewed and we have to >add those to the specific repo. @Inthirakumaaran Tharmakulasingham > will share the details on this. >- Generate guidance for creating an archetype. > > Please share your thoughts and suggestions about this effort, that will be > very helpful to us to continue on this :) > > [1] https://github.com/wso2-extensions/archetypes > <https://www.google.com/url?q=https://github.com/wso2-extensions/archetypes=D=hangouts=1564833739149000=AFQjCNFopSwDYqHH3VV8GZORIXe7CmhGTQ> > > 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 > > -- *Tharindu Bandara* 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 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [IS] Maven Archetype for Custom Event Handlers
Hi Athiththan, This is good! Can you please send a PR of this, to the is sample repository[1]? [1] https://github.com/wso2-incubator/samples-is Thanks, Tharindu. On Thu, Jul 25, 2019 at 3:53 PM Athiththan Kathirgamasegaran < athitht...@wso2.com> wrote: > Hi Tharindu/All, > > Sorry for the delayed response. > > You can clone or download the latest event-handler maven archetype from > here > <https://github.com/athiththan11/WSO2-Event-Handler-Maven-Archetype/tree/v2.0.0> > [1], > which now supports generating boilerplates with or without > IdentityConnectorConfig. This can be achieved by using the > >- -DIdentityConnectorConfig flag with either Y or N values > > to specify the generation of boilerplate with or without connector > configurations. > > Also, you can follow the provided README.md (in GitHub) file for more > instructions. > > [1]: > https://github.com/athiththan11/WSO2-Event-Handler-Maven-Archetype/tree/v2.0.0 > > Thanks & Regards, > *Kathirgamasegaran Athiththan *| Software Engineer | WSO2 Inc. > (m) +94774922931 | (e) athitht...@wso2.com > > <http://wso2.com/signature> > > > On Mon, Jul 8, 2019 at 12:23 PM Tharindu Bandara > wrote: > >> Hi Athiththan, >> >> Thanks! >> >> Can we also support the following capability? >> >>- Generate the code with/without IdentityConnectorConfig support. >> >> Thanks, >> Tharindu. >> >> On Fri, Jul 5, 2019 at 8:27 AM Athiththan Kathirgamasegaran < >> athitht...@wso2.com> wrote: >> >>> Hi Tharindu, >>> >>> Thank you for your question and suggestion regarding maven archetype and >>> maven interactive mode. >>> >>> You can skip the interactive-mode by appending the following >>> parameter-line with your archetype generation command. >>> *-DinteractiveMode=false* >>> >>> Also, I will do update all relevant docs on how-to skip the >>> interactive-mode with related snippets. >>> >>> Cheers!!! >>> Thanks & Regards, >>> *Kathirgamasegaran Athiththan *| Software Engineer | WSO2 Inc. >>> (m) +94774922931 | (e) athitht...@wso2.com >>> >>> <http://wso2.com/signature> >>> >>> >>> On Thu, Jul 4, 2019 at 11:49 PM Tharindu Bandara >>> wrote: >>> >>>> Hi Athiththan, >>>> >>>> This looks great! I have a few questions also. >>>> >>>> I tried to install the archetype[1] and then generate the code, but >>>> could not get passed through the interactive mode. I might have missed a >>>> step here. >>>> >>>> Can you please update readme file with step by step guide, or a link to >>>> such guide, so we will be able to locally install the archetype and >>>> generate the code through the shell. >>>> >>>> [1] https://github.com/athiththan11/WSO2-Event-Handler-Maven-Archetype >>>> >>>> Thanks, >>>> Tharindu. >>>> >>>> On Thu, Jul 4, 2019 at 11:37 AM Athiththan Kathirgamasegaran < >>>> athitht...@wso2.com> wrote: >>>> >>>>> Hi All, >>>>> >>>>> WSO2 Identity Server (from 5.3.0 onwards) supports handling published >>>>> events via an integrated event framework. So, I have developed a custom >>>>> maven archetype to generate boilerplates to kickstart custom event-handler >>>>> implementations. Check out the implementation below ... >>>>> >>>>>- Event-Handlers: >>>>>https://github.com/athiththan11/WSO2-Event-Handler-Maven-Archetype >>>>> >>>>> Additionally >>>>> >>>>>- Class Mediators: >>>>>https://github.com/athiththan11/WSO2-Mediators-Maven-Archetype >>>>>- Handler: >>>>>https://github.com/athiththan11/WSO2-Handler-Maven-Archetype >>>>>- Password Validator: >>>>>https://github.com/athiththan11/WSO2-Password-Validator-Maven-Archetype >>>>> >>>>> Let me know your thoughts and suggestions. >>>>> >>>>> Thanks & Regards, >>>>> *Kathirgamasegaran Athiththan *| Software Engineer | WSO2 Inc. >>>>> (m) +94774922931 | (e) athitht...@wso2.com >>>>> >>>>> <http://wso2.com/signature> >>>>> >>>> >>>> >>>> -- >>>> *Tharindu Bandara* >>>> 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 >>>> >>> >> >> -- >> *Tharindu Bandara* >> 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 >> > -- *Tharindu Bandara* 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 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [IS] Maven Archetype for Custom Event Handlers
Hi Athiththan, Thanks! Can we also support the following capability? - Generate the code with/without IdentityConnectorConfig support. Thanks, Tharindu. On Fri, Jul 5, 2019 at 8:27 AM Athiththan Kathirgamasegaran < athitht...@wso2.com> wrote: > Hi Tharindu, > > Thank you for your question and suggestion regarding maven archetype and > maven interactive mode. > > You can skip the interactive-mode by appending the following > parameter-line with your archetype generation command. > *-DinteractiveMode=false* > > Also, I will do update all relevant docs on how-to skip the > interactive-mode with related snippets. > > Cheers!!! > Thanks & Regards, > *Kathirgamasegaran Athiththan *| Software Engineer | WSO2 Inc. > (m) +94774922931 | (e) athitht...@wso2.com > > <http://wso2.com/signature> > > > On Thu, Jul 4, 2019 at 11:49 PM Tharindu Bandara > wrote: > >> Hi Athiththan, >> >> This looks great! I have a few questions also. >> >> I tried to install the archetype[1] and then generate the code, but could >> not get passed through the interactive mode. I might have missed a step >> here. >> >> Can you please update readme file with step by step guide, or a link to >> such guide, so we will be able to locally install the archetype and >> generate the code through the shell. >> >> [1] https://github.com/athiththan11/WSO2-Event-Handler-Maven-Archetype >> >> Thanks, >> Tharindu. >> >> On Thu, Jul 4, 2019 at 11:37 AM Athiththan Kathirgamasegaran < >> athitht...@wso2.com> wrote: >> >>> Hi All, >>> >>> WSO2 Identity Server (from 5.3.0 onwards) supports handling published >>> events via an integrated event framework. So, I have developed a custom >>> maven archetype to generate boilerplates to kickstart custom event-handler >>> implementations. Check out the implementation below ... >>> >>>- Event-Handlers: >>>https://github.com/athiththan11/WSO2-Event-Handler-Maven-Archetype >>> >>> Additionally >>> >>>- Class Mediators: >>>https://github.com/athiththan11/WSO2-Mediators-Maven-Archetype >>>- Handler: >>>https://github.com/athiththan11/WSO2-Handler-Maven-Archetype >>>- Password Validator: >>>https://github.com/athiththan11/WSO2-Password-Validator-Maven-Archetype >>> >>> Let me know your thoughts and suggestions. >>> >>> Thanks & Regards, >>> *Kathirgamasegaran Athiththan *| Software Engineer | WSO2 Inc. >>> (m) +94774922931 | (e) athitht...@wso2.com >>> >>> <http://wso2.com/signature> >>> >> >> >> -- >> *Tharindu Bandara* >> 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 >> > -- *Tharindu Bandara* 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 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [IS] Maven Archetype for Custom Event Handlers
Hi Athiththan, This looks great! I have a few questions also. I tried to install the archetype[1] and then generate the code, but could not get passed through the interactive mode. I might have missed a step here. Can you please update readme file with step by step guide, or a link to such guide, so we will be able to locally install the archetype and generate the code through the shell. [1] https://github.com/athiththan11/WSO2-Event-Handler-Maven-Archetype Thanks, Tharindu. On Thu, Jul 4, 2019 at 11:37 AM Athiththan Kathirgamasegaran < athitht...@wso2.com> wrote: > Hi All, > > WSO2 Identity Server (from 5.3.0 onwards) supports handling published > events via an integrated event framework. So, I have developed a custom > maven archetype to generate boilerplates to kickstart custom event-handler > implementations. Check out the implementation below ... > >- Event-Handlers: >https://github.com/athiththan11/WSO2-Event-Handler-Maven-Archetype > > Additionally > >- Class Mediators: >https://github.com/athiththan11/WSO2-Mediators-Maven-Archetype >- Handler: https://github.com/athiththan11/WSO2-Handler-Maven-Archetype >- Password Validator: >https://github.com/athiththan11/WSO2-Password-Validator-Maven-Archetype > > Let me know your thoughts and suggestions. > > Thanks & Regards, > *Kathirgamasegaran Athiththan *| Software Engineer | WSO2 Inc. > (m) +94774922931 | (e) athitht...@wso2.com > > <http://wso2.com/signature> > -- *Tharindu Bandara* 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 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [Dev] [VOTE] Release WSO2 Identity Server 5.8.0 RC3
lestone/63?closed=1> >>>>- 5.8.0-M4 fixes >>>><https://github.com/wso2/product-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/> >>> >> >> >> -- >> >> *Dilin Dampahalage* >> Software Engineer | WSO2 >> >> Email : di...@wso2.com >> Mobile : +94 771 462939 >> web : http://wso2.com >> >> <http://wso2.com/signature> >> ___ >> Dev mailing list >> d...@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> > > > -- > *Ayesha Dissanayaka* > Associate Technical Lead > WSO2, Inc : http://wso2.com > <http://www.google.com/url?q=http%3A%2F%2Fwso2.com=D=1=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> > 20, Palm grove Avenue, Colombo 3 > E-Mail: aye...@wso2.com > Mobile: +94713580922 > ___ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > -- *Tharindu Bandara* 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 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [Dev] [VOTE] Release WSO2 Identity Server 5.8.0 RC2
tps://github.com/wso2/product-is/milestone/71?closed=1> >>>>>>- 5.8.0-Alpha fixes >>>>>><https://github.com/wso2/product-is/milestone/70?closed=1> >>>>>>- 5.8.0-M26 fixes >>>>>><https://github.com/wso2/product-is/milestone/69?closed=1> >>>>>>- 5.8.0-M25 fixes >>>>>><https://github.com/wso2/product-is/milestone/68?closed=1> >>>>>>- 5.8.0-M24 fixes >>>>>><https://github.com/wso2/product-is/milestone/67?closed=1> >>>>>>- 5.8.0-M6 fixes >>>>>><https://github.com/wso2/product-is/milestone/64?closed=1> >>>>>>- 5.8.0-M5 fixes >>>>>><https://github.com/wso2/product-is/milestone/63?closed=1> >>>>>>- 5.8.0-M4 fixes >>>>>><https://github.com/wso2/product-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-rc2/wso2is-5.8.0-rc2.zip> >>>>>> 5.8.0-rc2 >>>>>> <https://github.com/wso2/product-is/releases/download/v5.8.0-rc2/wso2is-5.8.0.zip> >>>>>> Analytics - >>>>>> https://github.com/wso2/analytics-is/releases/tag/v5.8.0-rc2 >>>>>> <https://github.com/wso2/analytics-is/releases/download/v5.8.0-rc2/wso2is-analytics-5.8.0-rc2.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/> >>>>> ___ >>>>> Dev mailing list >>>>> d...@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 >>>> <https://wso2.com/signature> >>>> ___ >>>> Dev mailing list >>>> d...@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>> >>> >>> -- >>> *Janak Amarasena* >>> >>> Software Engineer >>> >>> Email: ja...@wso2.com >>> >>> Mobile: +9464144 >>> >>> Web: https://wso2.com >>> >>> >>> <http://wso2.com/signature> >>> ___ >>> Dev mailing list >>> d...@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >> >> >> -- >> Nilasini Thirunavukkarasu >> Senior Software Engineer - WSO2 >> >> Email : nilas...@wso2.com >> Mobile : +94775241823 >> Web : http://wso2.com/ >> >> >> <http://wso2.com/signature> >> ___ >> Dev mailing list >> d...@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> > > > -- > > *Mathuriga Thavarajah* > Software Engineer > WSO2 Inc. - http ://wso2.com > > Email : mathur...@wso2.com > Mobile : +94778191300 > > > > *[image: http://wso2.com/signature] <http://wso2.com/signature>* > ___ > Dev mailing list > d...@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- *Tharindu Bandara* 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 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [Dev][VOTE] Release WSO2 Identity Server 5.8.0 RC1
Hi All, We are closing the vote as we found an issue with the email confirmation with user self-registration and another with is-analytics dependency versions. We will fix the issues and release another release candidate as soon as possible. Thanks, Tharindu On Sat, May 11, 2019 at 2:32 AM Hasanthi Purnima Dissanayake < hasan...@wso2.com> wrote: > Hi all, > > We are pleased to announce the first release candidate of WSO2 Identity > Server 5.8.0. > > This release fixes the following issues, > >- 5.8.0-RC1 fixes ><https://github.com/wso2/product-is/milestone/78?closed=1> >- 5.8.0-Beta5 fixes ><https://github.com/wso2/product-is/milestone/80?closed=1> >- 5.8.0-Beta4 fixes ><https://github.com/wso2/product-is/milestone/79?closed=1> >- 5.8.0-Beta3 fixes ><https://github.com/wso2/product-is/milestone/77?closed=1> >- 5.8.0-Beta fixes ><https://github.com/wso2/product-is/milestone/75?closed=1> >- 5.8.0-Alpha5 fixes ><https://github.com/wso2/product-is/milestone/74?closed=1> >- 5.8.0-Alpha4 fixes ><https://github.com/wso2/product-is/milestone/73?closed=1> >- 5.8.0-Alpha3 fixes ><https://github.com/wso2/product-is/milestone/72?closed=1> >- 5.8.0-Alpha2 fixes ><https://github.com/wso2/product-is/milestone/71?closed=1> >- 5.8.0-Alpha fixes ><https://github.com/wso2/product-is/milestone/70?closed=1> >- 5.8.0-M26 fixes ><https://github.com/wso2/product-is/milestone/69?closed=1> >- 5.8.0-M25 fixes ><https://github.com/wso2/product-is/milestone/68?closed=1> >- 5.8.0-M24 fixes ><https://github.com/wso2/product-is/milestone/67?closed=1> >- 5.8.0-M6 fixes ><https://github.com/wso2/product-is/milestone/64?closed=1> >- 5.8.0-M5 fixes ><https://github.com/wso2/product-is/milestone/63?closed=1> >- 5.8.0-M4 fixes ><https://github.com/wso2/product-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/v5.8.0-rc1 > Analytics - > https://github.com/wso2/analytics-is/releases/tag/v5.8.0-rc1 > > > 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/> > > -- > You received this message because you are subscribed to the Google Groups > "IAM team" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to iam-group+unsubscr...@wso2.com. > To view this discussion on the web visit > https://groups.google.com/a/wso2.com/d/msgid/iam-group/CANox4YgAgBJ4XZeLTxPNBV9irYUk4ja_1oqaJMz%3DfjLmb4oGmg%40mail.gmail.com > <https://groups.google.com/a/wso2.com/d/msgid/iam-group/CANox4YgAgBJ4XZeLTxPNBV9irYUk4ja_1oqaJMz%3DfjLmb4oGmg%40mail.gmail.com?utm_medium=email_source=footer> > . > -- *Tharindu Bandara* 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 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [IS] JDBC based Configuration Store for WSO2 IS
Hi Ruwan,
SCIM uses a different kind of query syntax than FIQL. Hence IMO we need to
> stick to SCIM like query syntax.
>
+1. I have changed the API to use Open Data Protocol based filter query[1]
which is SCIM like.
[1]
https://cwiki.apache.org/confluence/display/CXF20DOC/JAX-RS+Search#JAX-RSSearch-OpenDataProtocol
Thanks,
Tharindu.
On Tue, Dec 11, 2018 at 7:24 AM Ruwan Abeykoon wrote:
> Hi Folks,
> We need to stick to one type of query syntax.
> SCIM uses a different kind of query syntax than FIQL. Hence IMO we need to
> stick to SCIM like query syntax.
>
> Cheers,
> Ruwan
>
>
> On Mon, Dec 10, 2018 at 9:59 AM Tharindu Bandara
> wrote:
>
>> Hi all,
>>
>> I have refactored the API to include a search endpoint and on endpoint
>> naming. Please find the refactored REST API[1].
>>
>> For the implementation, I am using Apache CXF framework. Therefore for
>> the HTTP GET operations, endpoints are enabled with Feed Item Query
>> Language(FIQL) based search query support in Apache CXF[2]. This will be
>> used to support complex query based search with the endpoints.
>>
>> [1]
>> https://app.swaggerhub.com/apis-docs/WSO8/wso-2_identity_server_configuration_management_rest_api/1.0.0#/
>> [2]
>> https://cwiki.apache.org/confluence/display/CXF20DOC/JAX-RS+Search#JAX-RSSearch-FeedItemQueryLanguage
>>
>> Thanks,
>> Tharindu.
>>
>> On Wed, Dec 5, 2018 at 4:44 PM Tharindu Bandara
>> wrote:
>>
>>> Hi all,
>>>
>>> The database schema for the $subject is prepared and refactored with the
>>> review meeting[1] suggestions. Please find the corresponding DB schema
>>> architecture from the architecture mail thread[2].
>>>
>>> Based on the database schema, configuration store REST API is changed to
>>> include the required changes.
>>>
>>> Please find the refactored REST API[3].
>>>
>>> HTTP GET method for the “resource” and the “resource/{name}” endpoints
>>> support searching based on query parameter filters. These search filter
>>> parameters used in the GET method accept multiple values. For an
>>> example let’s look at the tenant query parameter. This parameter can be a
>>> list, containing multiple tenant domain values. This list parameter is used
>>> in the URL in the following manner.
>>>
>>> Ex:
>>>
>>> Parameter value would be, tenant=[adc.com, wso2.com]. In the HTTP GET
>>> request URL, this parameter will be passed as a repeating tenant parameter
>>> with multiple values.
>>>
>>>
>>> https://localhost:9443/api/identity/config-mgt/v1.0/configuration/email?tenant=wso2.com=abc.com.
>>> From the JAX-RS service, this repeating parameter will be collected into a
>>> List.
>>>
>>> Please add your valuable suggestions on this.
>>>
>>> [1] [1] "Invitation: [IAM][Review]JDBC Based Configuration Store @ Mon
>>> Dec 3, 2018 1pm - 2pm (IST) (WSO2 Engineering Group)"
>>>
>>> [2] [Architecture][IAM][JDBC based Configuration Store] Database Schema
>>>
>>> [3]
>>> https://app.swaggerhub.com/apis-docs/WSO8/wso-2_identity_server_configuration_management_rest_api/1.0.0
>>>
>>> Thanks,
>>>
>>> Tharindu.
>>>
>>> On Wed, Dec 5, 2018 at 1:53 PM Isura Karunaratne wrote:
>>>
>>>> Hi Chamila,
>>>>
>>>> On Tue, Dec 4, 2018 at 10:38 AM Chamila De Alwis
>>>> wrote:
>>>>
>>>>> Hi Tharindu, IS team,
>>>>>
>>>>> A quick clarification. Is this related to storing product
>>>>> configuration in a DBMS or are these only the configurations created at
>>>>> runtime? If it is the former, is this going to (gradually?) replace the
>>>>> XML
>>>>> config files?
>>>>>
>>>>> This is not a replacement for xml config files. Main objective is to
>>>> store tenant wise configurations at runtime.
>>>>
>>>> Cheers,
>>>> Isura.
>>>>
>>>>>
>>>>> *Chamila de Alwis* | Associate Technical Lead | WSO2 Inc.
>>>>> (m) +94 77 220 7163 | (e) chami...@wso2.com
>>>>> [image: Get Integration Agile] <https://wso2.com/signature>
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Oct 17, 2018 at 12:11 PM Tharindu Bandara
>>>>> wrote:
>>>>>
>>>>>> Hi Farasath,
>>>>>>
>&g
Re: [Architecture] [IS] JDBC based Configuration Store for WSO2 IS
Hi all,
I have refactored the API to include a search endpoint and on endpoint
naming. Please find the refactored REST API[1].
For the implementation, I am using Apache CXF framework. Therefore for the
HTTP GET operations, endpoints are enabled with Feed Item Query
Language(FIQL) based search query support in Apache CXF[2]. This will be
used to support complex query based search with the endpoints.
[1]
https://app.swaggerhub.com/apis-docs/WSO8/wso-2_identity_server_configuration_management_rest_api/1.0.0#/
[2]
https://cwiki.apache.org/confluence/display/CXF20DOC/JAX-RS+Search#JAX-RSSearch-FeedItemQueryLanguage
Thanks,
Tharindu.
On Wed, Dec 5, 2018 at 4:44 PM Tharindu Bandara wrote:
> Hi all,
>
> The database schema for the $subject is prepared and refactored with the
> review meeting[1] suggestions. Please find the corresponding DB schema
> architecture from the architecture mail thread[2].
>
> Based on the database schema, configuration store REST API is changed to
> include the required changes.
>
> Please find the refactored REST API[3].
>
> HTTP GET method for the “resource” and the “resource/{name}” endpoints
> support searching based on query parameter filters. These search filter
> parameters used in the GET method accept multiple values. For an example
> let’s look at the tenant query parameter. This parameter can be a list,
> containing multiple tenant domain values. This list parameter is used in
> the URL in the following manner.
>
> Ex:
>
> Parameter value would be, tenant=[adc.com, wso2.com]. In the HTTP GET
> request URL, this parameter will be passed as a repeating tenant parameter
> with multiple values.
>
>
> https://localhost:9443/api/identity/config-mgt/v1.0/configuration/email?tenant=wso2.com=abc.com.
> From the JAX-RS service, this repeating parameter will be collected into a
> List.
>
> Please add your valuable suggestions on this.
>
> [1] [1] "Invitation: [IAM][Review]JDBC Based Configuration Store @ Mon Dec
> 3, 2018 1pm - 2pm (IST) (WSO2 Engineering Group)"
>
> [2] [Architecture][IAM][JDBC based Configuration Store] Database Schema
>
> [3]
> https://app.swaggerhub.com/apis-docs/WSO8/wso-2_identity_server_configuration_management_rest_api/1.0.0
>
> Thanks,
>
> Tharindu.
>
> On Wed, Dec 5, 2018 at 1:53 PM Isura Karunaratne wrote:
>
>> Hi Chamila,
>>
>> On Tue, Dec 4, 2018 at 10:38 AM Chamila De Alwis
>> wrote:
>>
>>> Hi Tharindu, IS team,
>>>
>>> A quick clarification. Is this related to storing product configuration
>>> in a DBMS or are these only the configurations created at runtime? If it is
>>> the former, is this going to (gradually?) replace the XML config files?
>>>
>>> This is not a replacement for xml config files. Main objective is to
>> store tenant wise configurations at runtime.
>>
>> Cheers,
>> Isura.
>>
>>>
>>> *Chamila de Alwis* | Associate Technical Lead | WSO2 Inc.
>>> (m) +94 77 220 7163 | (e) chami...@wso2.com
>>> [image: Get Integration Agile] <https://wso2.com/signature>
>>>
>>>
>>>
>>> On Wed, Oct 17, 2018 at 12:11 PM Tharindu Bandara
>>> wrote:
>>>
>>>> Hi Farasath,
>>>>
>>>> The current plan is to manage email configurations per tenant.
>>>>
>>>> In the future, we can move similar tenant wise configurations to here.
>>>> A few examples would be email templates, challenge questions, issuer
>>>> details.
>>>>
>>>> Thanks,
>>>> Tharindu.
>>>>
>>>> On Wed, Oct 17, 2018 at 11:53 AM Farasath Ahamed
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Wed, Oct 17, 2018 at 10:36 AM Tharindu Bandara
>>>>> wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> I have been working on the $subject as WSO2 IS need a common place to
>>>>>> store configurations.
>>>>>>
>>>>>
>>>>> Can you give some examples for the types of configurations we plan to
>>>>> manage with this endpoint?
>>>>>
>>>>>
>>>>>>
>>>>>> Above diagramme is a high-level, modularized view of $subject
>>>>>> approach.
>>>>>>
>>>>>> I am working on the Configuration Management Endpoint. Below include
>>>>>> the REST API for this.
>>>>>>
>>>>>> Name : WSO2 Identity Server Configuration Management Rest API
Re: [Architecture] [IS] JDBC based Configuration Store for WSO2 IS
Hi all,
The database schema for the $subject is prepared and refactored with the
review meeting[1] suggestions. Please find the corresponding DB schema
architecture from the architecture mail thread[2].
Based on the database schema, configuration store REST API is changed to
include the required changes.
Please find the refactored REST API[3].
HTTP GET method for the “resource” and the “resource/{name}” endpoints
support searching based on query parameter filters. These search filter
parameters used in the GET method accept multiple values. For an example
let’s look at the tenant query parameter. This parameter can be a list,
containing multiple tenant domain values. This list parameter is used in
the URL in the following manner.
Ex:
Parameter value would be, tenant=[adc.com, wso2.com]. In the HTTP GET
request URL, this parameter will be passed as a repeating tenant parameter
with multiple values.
https://localhost:9443/api/identity/config-mgt/v1.0/configuration/email?tenant=wso2.com=abc.com.
>From the JAX-RS service, this repeating parameter will be collected into a
List.
Please add your valuable suggestions on this.
[1] [1] "Invitation: [IAM][Review]JDBC Based Configuration Store @ Mon Dec
3, 2018 1pm - 2pm (IST) (WSO2 Engineering Group)"
[2] [Architecture][IAM][JDBC based Configuration Store] Database Schema
[3]
https://app.swaggerhub.com/apis-docs/WSO8/wso-2_identity_server_configuration_management_rest_api/1.0.0
Thanks,
Tharindu.
On Wed, Dec 5, 2018 at 1:53 PM Isura Karunaratne wrote:
> Hi Chamila,
>
> On Tue, Dec 4, 2018 at 10:38 AM Chamila De Alwis
> wrote:
>
>> Hi Tharindu, IS team,
>>
>> A quick clarification. Is this related to storing product configuration
>> in a DBMS or are these only the configurations created at runtime? If it is
>> the former, is this going to (gradually?) replace the XML config files?
>>
>> This is not a replacement for xml config files. Main objective is to
> store tenant wise configurations at runtime.
>
> Cheers,
> Isura.
>
>>
>> *Chamila de Alwis* | Associate Technical Lead | WSO2 Inc.
>> (m) +94 77 220 7163 | (e) chami...@wso2.com
>> [image: Get Integration Agile] <https://wso2.com/signature>
>>
>>
>>
>> On Wed, Oct 17, 2018 at 12:11 PM Tharindu Bandara
>> wrote:
>>
>>> Hi Farasath,
>>>
>>> The current plan is to manage email configurations per tenant.
>>>
>>> In the future, we can move similar tenant wise configurations to here. A
>>> few examples would be email templates, challenge questions, issuer details.
>>>
>>> Thanks,
>>> Tharindu.
>>>
>>> On Wed, Oct 17, 2018 at 11:53 AM Farasath Ahamed
>>> wrote:
>>>
>>>>
>>>>
>>>> On Wed, Oct 17, 2018 at 10:36 AM Tharindu Bandara
>>>> wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> I have been working on the $subject as WSO2 IS need a common place to
>>>>> store configurations.
>>>>>
>>>>
>>>> Can you give some examples for the types of configurations we plan to
>>>> manage with this endpoint?
>>>>
>>>>
>>>>>
>>>>> Above diagramme is a high-level, modularized view of $subject approach.
>>>>>
>>>>> I am working on the Configuration Management Endpoint. Below include
>>>>> the REST API for this.
>>>>>
>>>>> Name : WSO2 Identity Server Configuration Management Rest API
>>>>>
>>>>> Base URL : {tenant-domain}/api/identity/config-mgt/v1.0
>>>>>
>>>>> URL
>>>>>
>>>>> Method
>>>>>
>>>>> Body
>>>>>
>>>>> Description
>>>>>
>>>>> /configuration
>>>>>
>>>>> POST
>>>>>
>>>>> Tenant Configurations object
>>>>>
>>>>> Add configurations
>>>>>
>>>>> PUT
>>>>>
>>>>> Tenant Configurations object
>>>>>
>>>>> Add or Replace configurations
>>>>>
>>>>> PATCH
>>>>>
>>>>> Tenant Configurations object
>>>>>
>>>>> Update existing configurations
>>>>>
>>>>> GET
>>>>>
>>>>> -
>>>>>
>>>>> Retrieve configurations
>>>>>
>>>>> DELETE
>>>>>
>>>>> -
>>>>>
>>>>> Revoke conf
Re: [Architecture] [IAM][JDBC based Configuration Store] Database Schema
> > Also, let's remove the unique index of CONFIG_ID in IDN_CONFIG_FILE table. > Then we can maintain multiple files for a given resource. > +1. I will remove the unique index of CONFIG_ID in the IDN_CONFIG_FILE table. Thanks, Tharindu. On Tue, Dec 4, 2018 at 10:48 AM Isura Karunaratne wrote: > Also, let's remove the unique index of CONFIG_ID in IDN_CONFIG_FILE table. > Then we can maintain multiple files for a given resource. > > Cheers, > Isura. > > On Tue, Dec 4, 2018 at 9:37 AM Tharindu Bandara > wrote: > >> Hi Isura, >> >> We better to restrict this in API level since there is no need of having >>> config resources without config attributes or config file. >> >> >> +1. I will add this restriction in the API level. >> >> Thanks, >> Tharindu. >> >> On Tue, Dec 4, 2018 at 9:24 AM Isura Karunaratne wrote: >> >>> Hi Tharindu, >>> >>> According to the database schema, we can add config resources without >>> any config attribute or config file. We better to restrict this in API >>> level since there is no need of having config resources without config >>> attributes or config file. >>> >>> Cheers, >>> Isura. >>> >>> On Mon, Dec 3, 2018 at 6:13 PM Tharindu Bandara >>> wrote: >>> >>>> Hi all, >>>> >>>> Following is the diagramme for the $subject. Configuration store REST >>>> API for WSO2 IS[2] will be refactored to support this. >>>> >>>> >>>> Above diagramme is based on the following key points as discussed in >>>> the review meeting[1]. >>>> >>>> >>>>- >>>> >>>>Resources will be grouped under its type. Ex: For resources grouped >>>>under the issuer, type would be the issuer. >>>>- >>>> >>>>A resource can either contain a file or not. Ex: Email template >>>>file for the email resource. >>>>- >>>> >>>>A resource can contain zero or more attributes. Ex: For an email >>>>resource, from and to values are attributes. >>>>- >>>> >>>>Attributes and the file will be kept in separate tables and boolean >>>>flags will be included in the resource table to indicate the existence >>>> of >>>>each category. >>>> >>>> [1] "Invitation: [IAM][Review]JDBC Based Configuration Store @ Mon Dec >>>> 3, 2018 1pm - 2pm (IST) (WSO2 Engineering Group)" >>>> >>>> [2] "[Architecture] [IS] JDBC based Configuration Store for WSO2 IS" >>>> >>>> Thanks, >>>> >>>> Tharindu. >>>> -- >>>> *Tharindu Bandara* >>>> 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 >>>> >>> >>> >>> -- >>> >>> *Isura Dilhara Karunaratne* >>> Associate Technical Lead | WSO2 <http://wso2.com/> >>> *lean.enterprise.middleware* >>> Email: is...@wso2.com >>> Mob : +94 772 254 810 >>> Blog : http://isurad.blogspot.com/ >>> >>> >>> >>> >> >> -- >> *Tharindu Bandara* >> 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 >> > > > -- > > *Isura Dilhara Karunaratne* > Associate Technical Lead | WSO2 <http://wso2.com/> > *lean.enterprise.middleware* > Email: is...@wso2.com > Mob : +94 772 254 810 > Blog : http://isurad.blogspot.com/ > > > > -- *Tharindu Bandara* 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 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [IAM][JDBC based Configuration Store] Database Schema
Hi Isura, We better to restrict this in API level since there is no need of having > config resources without config attributes or config file. +1. I will add this restriction in the API level. Thanks, Tharindu. On Tue, Dec 4, 2018 at 9:24 AM Isura Karunaratne wrote: > Hi Tharindu, > > According to the database schema, we can add config resources without any > config attribute or config file. We better to restrict this in API level > since there is no need of having config resources without config attributes > or config file. > > Cheers, > Isura. > > On Mon, Dec 3, 2018 at 6:13 PM Tharindu Bandara > wrote: > >> Hi all, >> >> Following is the diagramme for the $subject. Configuration store REST API >> for WSO2 IS[2] will be refactored to support this. >> >> >> Above diagramme is based on the following key points as discussed in the >> review meeting[1]. >> >> >>- >> >>Resources will be grouped under its type. Ex: For resources grouped >>under the issuer, type would be the issuer. >>- >> >>A resource can either contain a file or not. Ex: Email template file >>for the email resource. >>- >> >>A resource can contain zero or more attributes. Ex: For an email >>resource, from and to values are attributes. >>- >> >>Attributes and the file will be kept in separate tables and boolean >>flags will be included in the resource table to indicate the existence of >>each category. >> >> [1] "Invitation: [IAM][Review]JDBC Based Configuration Store @ Mon Dec 3, >> 2018 1pm - 2pm (IST) (WSO2 Engineering Group)" >> >> [2] "[Architecture] [IS] JDBC based Configuration Store for WSO2 IS" >> >> Thanks, >> >> Tharindu. >> -- >> *Tharindu Bandara* >> 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 >> > > > -- > > *Isura Dilhara Karunaratne* > Associate Technical Lead | WSO2 <http://wso2.com/> > *lean.enterprise.middleware* > Email: is...@wso2.com > Mob : +94 772 254 810 > Blog : http://isurad.blogspot.com/ > > > > -- *Tharindu Bandara* 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 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [IS] JDBC based Configuration Store for WSO2 IS
Hi Farasath,
The current plan is to manage email configurations per tenant.
In the future, we can move similar tenant wise configurations to here. A
few examples would be email templates, challenge questions, issuer details.
Thanks,
Tharindu.
On Wed, Oct 17, 2018 at 11:53 AM Farasath Ahamed wrote:
>
>
> On Wed, Oct 17, 2018 at 10:36 AM Tharindu Bandara
> wrote:
>
>> Hi all,
>>
>> I have been working on the $subject as WSO2 IS need a common place to
>> store configurations.
>>
>
> Can you give some examples for the types of configurations we plan to
> manage with this endpoint?
>
>
>>
>> Above diagramme is a high-level, modularized view of $subject approach.
>>
>> I am working on the Configuration Management Endpoint. Below include the
>> REST API for this.
>>
>> Name : WSO2 Identity Server Configuration Management Rest API
>>
>> Base URL : {tenant-domain}/api/identity/config-mgt/v1.0
>>
>> URL
>>
>> Method
>>
>> Body
>>
>> Description
>>
>> /configuration
>>
>> POST
>>
>> Tenant Configurations object
>>
>> Add configurations
>>
>> PUT
>>
>> Tenant Configurations object
>>
>> Add or Replace configurations
>>
>> PATCH
>>
>> Tenant Configurations object
>>
>> Update existing configurations
>>
>> GET
>>
>> -
>>
>> Retrieve configurations
>>
>> DELETE
>>
>> -
>>
>> Revoke configurations
>>
>> /configuration/{key}
>>
>> POST
>>
>> Configuration object
>>
>> Add the configuration
>>
>> PUT
>>
>> Configuration object
>>
>> Add or Replace the configuration
>>
>> PATCH
>>
>> Configuration object
>>
>> Update existing configuration
>>
>> GET
>>
>> -
>>
>> Retrieve the configuration
>>
>> DELETE
>>
>> -
>>
>> Revoke the configuration
>>
>> A path parameter named ‘key’ is used to identify a configuration.
>>
>> Path Parameter
>>
>> Description
>>
>> {key}
>>
>> Key of the configuration
>>
>> Two types of data objects are used for above REST API calls.
>>
>> Data object
>>
>> Model
>>
>> Tenant Configurations object
>>
>> Configuration object
>>
>>
>> Let’s have a look at an example POST request to add the “email
>> configuration” using WSO2 Identity Server Configuration Management Rest API.
>>
>> Method
>>
>> POST
>>
>> URL
>>
>> /api/identity/config-mgt/v1.0/configuration/email
>>
>> Body
>>
>>
>> Please refer to the detailed REST API documentation for in-depth
>> information[1]
>> <https://app.swaggerhub.com/apis-docs/WSO8/wso-2_identity_server_configuration_management_rest_api/1.0.0>
>> .
>>
>> Please note that naming in the API is not finalized yet.
>>
>> Your valuable comments and suggestions are highly appreciated.
>>
>>
>> [1]
>> https://app.swaggerhub.com/apis-docs/WSO8/wso-2_identity_server_configuration_management_rest_api/1.0.0
>> <https://app.swaggerhub.com/apis-docs/WSO8/wso-2_identity_server_configuration_management_rest_api/1.0.0#/>
>>
>> Thanks,
>>
>> Tharindu.
>> --
>> *Tharindu Bandara*
>> 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
>>
>
>
> --
> Farasath Ahamed
> Senior Software Engineer, WSO2 Inc.; http://wso2.com
> Mobile: +94777603866
> Blog: blog.farazath.com
> Twitter: @farazath619 <https://twitter.com/farazath619>
> <http://wso2.com/signature>
>
>
>
>
--
*Tharindu Bandara*
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
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [IS] JDBC based Configuration Store for WSO2 IS
+1. Will change accordingly.
On Wed, Oct 17, 2018 at 10:54 AM Isura Karunaratne wrote:
> Hi Tharindu,
>
>
>
> On Wed, Oct 17, 2018 at 10:36 AM Tharindu Bandara
> wrote:
>
>> Hi all,
>>
>> I have been working on the $subject as WSO2 IS need a common place to
>> store configurations.
>>
>>
>> Above diagramme is a high-level, modularized view of $subject approach.
>>
>> I am working on the Configuration Management Endpoint. Below include the
>> REST API for this.
>>
>> Name : WSO2 Identity Server Configuration Management Rest API
>>
>> Base URL : {tenant-domain}/api/identity/config-mgt/v1.0
>>
>> URL
>>
>> Method
>>
>> Body
>>
>> Description
>>
>> /configuration
>>
>> POST
>>
>> Tenant Configurations object
>>
>> Add configurations
>>
>> PUT
>>
>> Tenant Configurations object
>>
>> Add or Replace configurations
>>
>> PATCH
>>
>> Tenant Configurations object
>>
>> Update existing configurations
>>
>> GET
>>
>> -
>>
>> Retrieve configurations
>>
>> DELETE
>>
>> -
>>
>> Revoke configurations
>>
>> /configuration/{key}
>>
>> POST
>>
>> Configuration object
>>
>> Add the configuration
>>
>> PUT
>>
>> Configuration object
>>
>> Add or Replace the configuration
>>
>> PATCH
>>
>> Configuration object
>>
>> Update existing configuration
>>
>> GET
>>
>> -
>>
>> Retrieve the configuration
>>
>> DELETE
>>
>> -
>>
>> Revoke the configuration
>>
>> A path parameter named ‘key’ is used to identify a configuration.
>>
>
> According to the swagger definition, the POST body of the adding a new
> configuration is as follows. According to that, you need to use "name" as
> the path paramter instead of "key".
>
>
> {
> "configurations": [
> {
> "name": "string",
> "attributes": [
> {
> "key": "string",
> "value": "string"
> }
> ]
> }
> ]
> }
>
>
> Thanks
> Isura.
>
>
>>
>> Path Parameter
>>
>> Description
>>
>> {key}
>>
>> Key of the configuration
>>
>> Two types of data objects are used for above REST API calls.
>>
>> Data object
>>
>> Model
>>
>> Tenant Configurations object
>>
>> Configuration object
>>
>>
>> Let’s have a look at an example POST request to add the “email
>> configuration” using WSO2 Identity Server Configuration Management Rest API.
>>
>> Method
>>
>> POST
>>
>> URL
>>
>> /api/identity/config-mgt/v1.0/configuration/email
>>
>> Body
>>
>>
>> Please refer to the detailed REST API documentation for in-depth
>> information[1]
>> <https://app.swaggerhub.com/apis-docs/WSO8/wso-2_identity_server_configuration_management_rest_api/1.0.0>
>> .
>>
>> Please note that naming in the API is not finalized yet.
>>
>> Your valuable comments and suggestions are highly appreciated.
>>
>>
>> [1]
>> https://app.swaggerhub.com/apis-docs/WSO8/wso-2_identity_server_configuration_management_rest_api/1.0.0
>> <https://app.swaggerhub.com/apis-docs/WSO8/wso-2_identity_server_configuration_management_rest_api/1.0.0#/>
>>
>> Thanks,
>>
>> Tharindu.
>> --
>> *Tharindu Bandara*
>> 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
>>
>
>
> --
>
> *Isura Dilhara Karunaratne*
> Associate Technical Lead | WSO2 <http://wso2.com/>
> *lean.enterprise.middleware*
> Email: is...@wso2.com
> Mob : +94 772 254 810
> Blog : http://isurad.blogspot.com/
>
>
>
>
--
*Tharindu Bandara*
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
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
[Architecture] [IS] JDBC based Configuration Store for WSO2 IS
Hi all,
I have been working on the $subject as WSO2 IS need a common place to store
configurations.
Above diagramme is a high-level, modularized view of $subject approach.
I am working on the Configuration Management Endpoint. Below include the
REST API for this.
Name : WSO2 Identity Server Configuration Management Rest API
Base URL : {tenant-domain}/api/identity/config-mgt/v1.0
URL
Method
Body
Description
/configuration
POST
Tenant Configurations object
Add configurations
PUT
Tenant Configurations object
Add or Replace configurations
PATCH
Tenant Configurations object
Update existing configurations
GET
-
Retrieve configurations
DELETE
-
Revoke configurations
/configuration/{key}
POST
Configuration object
Add the configuration
PUT
Configuration object
Add or Replace the configuration
PATCH
Configuration object
Update existing configuration
GET
-
Retrieve the configuration
DELETE
-
Revoke the configuration
A path parameter named ‘key’ is used to identify a configuration.
Path Parameter
Description
{key}
Key of the configuration
Two types of data objects are used for above REST API calls.
Data object
Model
Tenant Configurations object
Configuration object
Let’s have a look at an example POST request to add the “email
configuration” using WSO2 Identity Server Configuration Management Rest API.
Method
POST
URL
/api/identity/config-mgt/v1.0/configuration/email
Body
Please refer to the detailed REST API documentation for in-depth information
[1]
<https://app.swaggerhub.com/apis-docs/WSO8/wso-2_identity_server_configuration_management_rest_api/1.0.0>
.
Please note that naming in the API is not finalized yet.
Your valuable comments and suggestions are highly appreciated.
[1]
https://app.swaggerhub.com/apis-docs/WSO8/wso-2_identity_server_configuration_management_rest_api/1.0.0
<https://app.swaggerhub.com/apis-docs/WSO8/wso-2_identity_server_configuration_management_rest_api/1.0.0#/>
Thanks,
Tharindu.
--
*Tharindu Bandara*
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
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [Dev] [VOTE] Release of WSO2 Identity Server Analytics 5.7.0 RC3
Hi all, I have tested the followings on WSO2 Identity Server Analytics 5.7.0 RC3. - Risk based adaptive authentication. - Successful local login attempt. - Failed local login attempt. - Suspicious login attempt. No blocking issues were found. *[+] Stable - go ahead and release* Thanks, Tharindu On Tue, Sep 18, 2018 at 5:07 PM Chamath Samarawickrama wrote: > Hi, > > I have tested the following on WSO2 Identity Server Analytics 5.7.0 RC3. > >- Overall login attempts dashboard >- Suspicious login attempts dashboard >- Login sessions dashboard >- Configuring risk-based Adaptive Authentication > > No blocking issues were found. > > *[+] Stable - go ahead and release* > > Thanks, > Chamath > > On Tue, Sep 18, 2018 at 3:42 PM Nuwandi Wickramasinghe > wrote: > >> Hi All, >> >> >> We are pleased to announce the third release candidate of WSO2 Identity >> Server Analytics 5.7.0. >> >> >> This release fixes the following issues, >> >> >> >>- 5.7.0-RC3 Fixes >><https://github.com/wso2/analytics-is/milestone/4?closed=1> >>- 5.7.0-RC2 Fixes >><https://github.com/wso2/analytics-is/milestone/3?closed=1> >>- 5.7.0-RC1 Fixes >><https://github.com/wso2/analytics-is/milestone/2?closed=1> >> >> >> >> Source and distribution, >> >> >>- https://github.com/wso2/analytics-is/releases/v5.7.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 - >> >> -- >> >> Best Regards, >> >> Nuwandi Wickramasinghe >> >> Senior Software Engineer >> >> WSO2 Inc. >> >> Web : http://wso2.com >> >> Mobile : 0719214873 >> > > > -- > *C**h**amath Samarawickrama* > Intern | WSO2, Inc. > Mobile : +94772598944 > Twitter <https://twitter.com/htamahc> LinkedIn > <https://www.linkedin.com/in/htamahc/> GitHub > <https://github.com/htamahc> > ___ > Dev mailing list > d...@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- *Tharindu Bandara* 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 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [VOTE] Release of WSO2 Stream Processor 4.3.0 RC3
Hi all, I have tested EI Analytics dashboard in SP 4.3.0 RC3. No blockers found. [+] Stable - Go ahead and release. Thanks, Tharindu. On Mon, Sep 17, 2018 at 5:26 PM Dileesha Rajapakse wrote: > Hi everyone, > > Tested EI analytics functionalities. No blockers found. > > [+] Stable - Go ahead and release. > > Regards. > > On Mon, Sep 17, 2018 at 4:55 PM Ambujaa Satchithananthan > wrote: > >> Hi All, >> >> I've tested the following pages in the IS Analytics. >> >>1. Login Session >>2. Alert Type >>3. Suspicious Login Alerts >>4. Long Session Alerts >> >> No issues found. >> >> [+] Stable go ahead and release >> >> On Mon, Sep 17, 2018 at 11:42 AM, Tuan Muraad wrote: >> >>> Hi all, >>> >>> I've tested the following editor samples. >>> >>>1. Redis Sample >>>2. Clustree Sample >>>3. Data Preprocessing >>>4. Extract Named Entities >>>5. Streaming Perceptron >>>6. Extreme Bottom K >>>7. HBase Sample >>> >>> No issues found >>> >>> [+] Stable go ahead and release >>> >>> Regards, >>> >>> On Sat, Sep 15, 2018 at 1:05 AM, Dilini Muthumala >>> wrote: >>> >>>> Hi all, >>>> >>>> >>>> WSO2 Stream Processor team is pleased to announce the third >>>> release candidate of WSO2 Stream Processor 4.3.0. >>>> >>>> >>>> WSO2 Stream Processor is an open source embodiment of the WSO2 >>>> Analytics platform, of which the real-time, incremental & intelligent >>>> data processing capabilities let digital businesses create actionable >>>> business insights and data products. >>>> >>>> >>>> Please find the improvements and fixes related to this release: >>>> >>>> - siddhi >>>> <https://github.com/wso2/siddhi/issues?utf8=%E2%9C%93=is%3Aissue+closed%3A2018-06-20..2018-09-15> >>>> >>>> - carbon-analytics-common >>>> <https://github.com/wso2/carbon-analytics-common/issues?utf8=%E2%9C%93=is%3Aissue+closed%3A2018-06-20..2018-09-15> >>>> >>>> - carbon-analytics >>>> <https://github.com/wso2/carbon-analytics/issues?utf8=%E2%9C%93=is%3Aissue+closed%3A2018-06-20..2018-09-15> >>>> >>>> - carbon-dashboards >>>> <https://github.com/wso2/carbon-dashboards/issues?utf8=%E2%9C%93=is%3Aissue+closed%3A2018-06-20..2018-09-15> >>>> >>>> - analytics-solutions >>>> <https://github.com/wso2/analytics-solutions/issues?utf8=%E2%9C%93=is%3Aissue+closed%3A2018-06-20..2018-09-15> >>>> >>>> - product-sp >>>> <https://github.com/wso2/product-sp/issues?utf8=%E2%9C%93=is%3Aissue+closed%3A2018-06-20..2018-09-15> >>>> >>>> >>>> You can download the product distribution from: >>>> https://github.com/wso2/product-sp/releases/download/v4.3.0-rc3/wso2sp-4.3.0-rc3.zip >>>> >>>> >>>> The tag to be voted upon: >>>> *https://github.com/wso2/product-sp/releases/tag/v4.3.0-rc3 >>>> <https://github.com/wso2/product-sp/releases/tag/v4.3.0-rc3>* >>>> >>>> >>>> Please download, test the product and vote. >>>> >>>> >>>> [+] Stable - go ahead and release >>>> >>>> [-] Broken - do not release (explain why) >>>> >>>> >>>> Thanks, >>>> >>>> - WSO2 Stream Processor Team - >>>> >>> >>> >>> >>> -- >>> Tuan Muraad Amith >>> Software Engineer Intern | WSO2 >>> >>> Email: t...@wso2.com >>> Mobile: +94766251372 >>> >> >> >> >> -- >> Ambujaa Satchithananthan >> Associate Software Engineer | WSO2 >> >> Email: ambu...@wso2.com >> Mobile: +94768462473 >> Web: http://Wso2.com >> >> >> >> > > -- > *Dileesha Rajapakse* > Software Engineer | WSO2 Inc. > Mobile: +94 772555933 > http://www.dilee.me > > -- *Tharindu Bandara* 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 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [Dev] [VOTE] Release WSO2 Identity Server 5.7.0 RC3
ution, >>>> >>>> >>>>Runtime - https://github.com/wso2/product-is/releases/v5.7.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 - >>>> -- >>>> >>>> *Senthalan Kanagalingam* >>>> *Software Engineer - WSO2 Inc.* >>>> *Mobile : +94 (0) 77 18 77 466* >>>> <http://wso2.com/signature> >>>> >>> ___ >>> Dev mailing list >>> d...@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >> >> >> -- >> Minoli Perera, >> Software Engineer, WSO2, Inc. >> E-mail : mino...@wso2.com >> Mobile : +94771567527 >> <http://wso2.com/signature> >> >> ___ >> Dev mailing list >> d...@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > > *Winma Heenatigala* > *Trainee Software Engineer | WSO2* > > *Mobile : +94719132444* > > > > ___ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > -- *Tharindu Bandara* 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 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [Dev] [VOTE] Release WSO2 Identity Server 5.7.0 RC2
gt;>>>>>>> >>>>>>>>>> >>>>>>>>>> This release fixes the following issues, >>>>>>>>>> >>>>>>>>>>- >>>>>>>>>> >>>>>>>>>>5.7.0-RC2 fixes >>>>>>>>>><https://github.com/wso2/product-is/milestone/58?closed=1> >>>>>>>>>>- >>>>>>>>>> >>>>>>>>>>5.7.0-RC1 fixes >>>>>>>>>><https://github.com/wso2/product-is/milestone/52?closed=1> >>>>>>>>>>- >>>>>>>>>> >>>>>>>>>>5.7.0-Beta2 fixes >>>>>>>>>><https://github.com/wso2/product-is/milestone/57?closed=1> >>>>>>>>>>- >>>>>>>>>> >>>>>>>>>>5.7.0-Beta fixes >>>>>>>>>><https://github.com/wso2/product-is/milestone/54?closed=1> >>>>>>>>>>- >>>>>>>>>> >>>>>>>>>>5.7.0-Alpha3 fixes >>>>>>>>>><https://github.com/wso2/product-is/milestone/53?closed=1> >>>>>>>>>>- >>>>>>>>>> >>>>>>>>>>5.7.0-Alpha2 fixes >>>>>>>>>><https://github.com/wso2/product-is/milestone/51?closed=1> >>>>>>>>>>- >>>>>>>>>> >>>>>>>>>>5.7.0-Alpha fixes >>>>>>>>>><https://github.com/wso2/product-is/milestone/50?closed=1> >>>>>>>>>>- >>>>>>>>>> >>>>>>>>>>5.7.0-M5 fixes >>>>>>>>>><https://github.com/wso2/product-is/milestone/49?closed=1> >>>>>>>>>>- >>>>>>>>>> >>>>>>>>>>5.7.0-M4 fixes >>>>>>>>>><https://github.com/wso2/product-is/milestone/48?closed=1> >>>>>>>>>>- >>>>>>>>>> >>>>>>>>>>5.7.0-M3 fixes >>>>>>>>>> <https://github.com/wso2/product-is/milestone/47?closed=1> >>>>>>>>>>- >>>>>>>>>> >>>>>>>>>>5.7.0-M2 fixes >>>>>>>>>><https://github.com/wso2/product-is/milestone/46?closed=1> >>>>>>>>>>- >>>>>>>>>> >>>>>>>>>>5.7.0-M1 fixes >>>>>>>>>><https://github.com/wso2/product-is/milestone/45?closed=1> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Source and distribution, >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>Runtime - >>>>>>>>>> https://github.com/wso2/product-is/releases/v5.7.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 - >>>>>>>>>> -- >>>>>>>>>> >>>>>>>>>> *Senthalan Kanagalingam* >>>>>>>>>> *Software Engineer - WSO2 Inc.* >>>>>>>>>> *Mobile : +94 (0) 77 18 77 466* >>>>>>>>>> <http://wso2.com/signature> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Maduranga Siriwardena >>>>>>>>> Associated Technical Lead >>>>>>>>> WSO2 Inc; http://wso2.com/ >>>>>>>>> >>>>>>>>> Email: madura...@wso2.com >>>>>>>>> Mobile: +94718990591 >>>>>>>>> Blog: *https://madurangasiriwardena.wordpress.com/ >>>>>>>>> <https://madurangasiriwardena.wordpress.com/>* >>>>>>>>> <http://wso2.com/signature> >>>>>>>>> ___ >>>>>>>>> Dev mailing list >>>>>>>>> d...@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 >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> <https://lk.linkedin.com/in/dinalidabarera> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> ___ >>>>>>>> Dev mailing list >>>>>>>> d...@wso2.org >>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> *Dinika Senarath* >>>>>>> *Intern Software Engineer* >>>>>>> *WSO2* >>>>>>> >>>>>>> ___ >>>>>>> Dev mailing list >>>>>>> d...@wso2.org >>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> *Winma Heenatigala* >>>>>> *Trainee Software Engineer | WSO2* >>>>>> >>>>>> *Mobile : +94719132444* >>>>>> >>>>>> >>>>>> >>>>>> ___ >>>>>> Dev mailing list >>>>>> d...@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> d...@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Janak Amarasena* >>>> >>>> Software Engineer >>>> >>>> Email: ja...@wso2.com >>>> >>>> Mobile: +9464144 >>>> >>>> Web: https://wso2.com >>>> >>>> >>>> <http://wso2.com/signature> >>>> ___ >>>> Dev mailing list >>>> d...@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>> >>> >>> -- >>> >>> Vihanga Liyanage >>> >>> Software Engineer | WS*O₂* Inc. >>> >>> M : +*94710124103* | http://wso2.com >>> >>> [image: http://wso2.com/signature] <http://wso2.com/signature> >>> ___ >>> Dev mailing list >>> d...@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >> >> >> -- >> >> *Dilin Dampahalage* >> Software Engineer | WSO2 >> >> Email : di...@wso2.com >> Mobile : +94 771 462939 >> web : http://wso2.com >> >> <http://wso2.com/signature> >> >> ___ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Mevan Karunanayake - Trainee Software Engineer | WSO2 > Email : me...@wso2.com > Mobile : +94 71 202 8954 > ___ > Dev mailing list > d...@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- *Tharindu Bandara* 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 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
