Re: [Dev] [IS] RESTful Fine Grained Authorization-as-a-Service (AZaaS)
Thank you Omindu! I'll check back for the review date and time Sanjeewa, the API definition can be found at [1] and it also has a swagger definition available at the url [2] once the service is running. So a client can use that. Thank You Manujith [1] https://manzzup.atlassian.net/wiki/display/WIRA/IS+REST+API+Guide [2] */Decision/api/swagger.json* On Tue, Aug 23, 2016 at 3:24 PM, Sanjeewa Malalgoda <sanje...@wso2.com> wrote: > First sorry about asking this in last minute. We can we find API > definition for this API? > Have we documented somewhere with all requests paths, payloads responses > etc? I > > Thanks, > sanjeewa. > > On Tue, Aug 23, 2016 at 3:05 PM, Omindu Rathnaweera <omi...@wso2.com> > wrote: > >> Great work Manujith! Let's schedule a demo and a code review within next >> week. >> >> Regards, >> Omindu. >> >> On Tue, Aug 23, 2016 at 2:27 PM, Manujith Pallewatte < >> manujith...@gmail.com> wrote: >> >>> Hi all, >>> >>> Coming to the conclusion of the project, here's the progress so far >>> The project description can be seen at [1]. The goal was to provide >>> RESTful access to the PDP of the IS >>> >>> Progress >>> >>> 1) REST implementation done using Apache CXF framework >>> 2) JSON compatibility added using Jackson jax-rs >>> 3) REST service supports consuming and producing JSON and XML >>> 4) REST API fully compliant with the XACML 3.0 REST profile [2] and >>> XACML 3.0 JSON profile [3] >>> 5) Using swagger to populate service method >>> 6) Integration tests and documentation done >>> >>> Deliverables >>> - >>> 1) REST implementation for the IS PDP [4] >>> 2) Developer[5] and User[6] documentation >>> 3) Integration tests >>> >>> In addition the following blog post covers the progress in detail [7] >>> and it was submitted as the work product submission link for student's >>> final evaluation form. >>> >>> Finally i would like to thank all my mentors for the immense support and >>> the community for their prompt assistance. >>> >>> [1] https://docs.wso2.com/display/GSoC/Project+Proposals+for >>> +2016#ProjectProposalsfor2016-Proposal22:[IS]RESTfulFineGrai >>> nedAuthorization-as-a-Service(AZaaS) >>> [2] http://docs.oasis-open.org/xacml/xacml-rest/v1.0/csprd03 >>> /xacml-rest-v1.0-csprd03.html >>> [3] http://docs.oasis-open.org/xacml/xacml-json-http/v1.0/xa >>> cml-json-http-v1.0.html >>> [4] https://github.com/ManZzup/identity-framework/tree/maste >>> r/components/entitlement/org.wso2.carbon.identity.entitlement.endpoint >>> [5] http://manzzup.github.io/wso2-entitlement-endpoint/devdoc/ >>> [6] https://manzzup.atlassian.net/wiki/display/WIRA/IS+REST+API+Guide >>> [7] http://manzzup.blogspot.com/2016/08/gsoc-2016-rest-imple >>> mentation-for-wso2.html >>> >>> Thank You >>> Manujith >>> >>> On Sun, Aug 14, 2016 at 1:39 PM, Manujith Pallewatte < >>> manujith...@gmail.com> wrote: >>> >>>> Hi Pushpalanka, >>>> >>>> Thank you for the comments >>>> >>>> 1) I added a list of required changes at [1] >>>> >>>> 2) The blog post will be link for now from the github readme, since I'm >>>> adding additional blog posts to support the content of the above post >>>> (mostly in depth implementation details for source), I thought of keeping >>>> the blogpost and linking from the repo. But I will have a markdown version >>>> of the blogpost as well. >>>> >>>> On other updates, >>>> >>>> 1) Swagger is now implemented >>>> 2) Integration tests are done using Jetty >>>> 3) Added the Jira ticket at [2], will add the PR as soon as the tests >>>> are done >>>> >>>> >>>> >>>> [1] https://github.com/ManZzup/identity-framework/blob/maste >>>> r/components/entitlement/org.wso2.carbon.identity.entitlemen >>>> t.endpoint/REQUIRED_CHANGES.md >>>> [2] https://wso2.org/jira/browse/IDENTITY-4985 >>>> >>>> Thank You >>>> Manujith >>>> >>>> On Fri, Aug 12, 2016 at 3:45 PM, Pushpalanka Jayawardhana < >>>> la...@wso2.com> wrote: >>>> >>>>> Hi Manujith, >>>>> >>>>> Good to see the project reaching final stages. >>>&
Re: [Dev] [IS] RESTful Fine Grained Authorization-as-a-Service (AZaaS)
Hi all, Coming to the conclusion of the project, here's the progress so far The project description can be seen at [1]. The goal was to provide RESTful access to the PDP of the IS Progress 1) REST implementation done using Apache CXF framework 2) JSON compatibility added using Jackson jax-rs 3) REST service supports consuming and producing JSON and XML 4) REST API fully compliant with the XACML 3.0 REST profile [2] and XACML 3.0 JSON profile [3] 5) Using swagger to populate service method 6) Integration tests and documentation done Deliverables - 1) REST implementation for the IS PDP [4] 2) Developer[5] and User[6] documentation 3) Integration tests In addition the following blog post covers the progress in detail [7] and it was submitted as the work product submission link for student's final evaluation form. Finally i would like to thank all my mentors for the immense support and the community for their prompt assistance. [1] https://docs.wso2.com/display/GSoC/Project+Proposals+for+2016#ProjectProposalsfor2016-Proposal22:[IS]RESTfulFineGrainedAuthorization-as-a-Service(AZaaS) [2] http://docs.oasis-open.org/xacml/xacml-rest/v1.0/csprd03/xacml-rest-v1.0-csprd03.html [3] http://docs.oasis-open.org/xacml/xacml-json-http/v1.0/xacml-json-http-v1.0.html [4] https://github.com/ManZzup/identity-framework/tree/master/components/entitlement/org.wso2.carbon.identity.entitlement.endpoint [5] http://manzzup.github.io/wso2-entitlement-endpoint/devdoc/ [6] https://manzzup.atlassian.net/wiki/display/WIRA/IS+REST+API+Guide [7] http://manzzup.blogspot.com/2016/08/gsoc-2016-rest-implementation-for-wso2.html Thank You Manujith On Sun, Aug 14, 2016 at 1:39 PM, Manujith Pallewatte <manujith...@gmail.com> wrote: > Hi Pushpalanka, > > Thank you for the comments > > 1) I added a list of required changes at [1] > > 2) The blog post will be link for now from the github readme, since I'm > adding additional blog posts to support the content of the above post > (mostly in depth implementation details for source), I thought of keeping > the blogpost and linking from the repo. But I will have a markdown version > of the blogpost as well. > > On other updates, > > 1) Swagger is now implemented > 2) Integration tests are done using Jetty > 3) Added the Jira ticket at [2], will add the PR as soon as the tests are > done > > > > [1] https://github.com/ManZzup/identity-framework/blob/master/components/ > entitlement/org.wso2.carbon.identity.entitlement.endpoint/ > REQUIRED_CHANGES.md > [2] https://wso2.org/jira/browse/IDENTITY-4985 > > Thank You > Manujith > > On Fri, Aug 12, 2016 at 3:45 PM, Pushpalanka Jayawardhana <la...@wso2.com> > wrote: > >> Hi Manujith, >> >> Good to see the project reaching final stages. >> Please find the comments inline. >> >> Thanks, >> Pushpalanka >> >> On Thu, Aug 11, 2016 at 1:23 PM, Manujith Pallewatte < >> manujith...@gmail.com> wrote: >> >>> UPDATE >>> >>> Adding missing links >>> [1] http://docs.oasis-open.org/xacml/xacml-rest/v1.0/csprd03 >>> /xacml-rest-v1.0-csprd03.html >>> [2] http://docs.oasis-open.org/xacml/xacml-json-http/v1.0/xa >>> cml-json-http-v1.0.html >>> [3] http://manzzup.github.io/wso2-entitlement-endpoint/devdoc >>> >>> On Thu, Aug 11, 2016 at 1:22 PM, Manujith Pallewatte < >>> manujith...@gmail.com> wrote: >>> >>>> Hi all, >>>> >>>> To update on the current status >>>> 1) The endpoint is fully compliant with the XACML REST profile as >>>> stated here [1] >>>> 2) It is also in accordance with the JSON XACML request/response >>>> profile as stated in [2], except few things that require changes to balana >>>> >>> Can you please list down these things and the changes required in >> Balana, so that we can address them at least later. >> >>> 3) Developer documentation was generated after fully commenting the >>>> important codes and available for now at [3] >>>> >>> Additionally would be good to have the design details at github it self >> as well or linked to your blog at http://manzzup.blogspot.com/20 >> 16/08/gsoc-2016-rest-implementation-for-wso2.html. >> >>> >>>> Hoping to work on user documentation and integration tests and submit a >>>> new PR within next week >>>> Any ideas for improvements / ideas / changes to be done prior to the PR? >>>> >>>> Thank You >>>> Manujith >>>> >>>> >>>> >>>> On Wed, Jul 13, 2016 at 2:49 PM, Manujith Pallewatte
Re: [Dev] [IS] RESTful Fine Grained Authorization-as-a-Service (AZaaS)
Hi Pushpalanka, Thank you for the comments 1) I added a list of required changes at [1] 2) The blog post will be link for now from the github readme, since I'm adding additional blog posts to support the content of the above post (mostly in depth implementation details for source), I thought of keeping the blogpost and linking from the repo. But I will have a markdown version of the blogpost as well. On other updates, 1) Swagger is now implemented 2) Integration tests are done using Jetty 3) Added the Jira ticket at [2], will add the PR as soon as the tests are done [1] https://github.com/ManZzup/identity-framework/blob/master/components/entitlement/org.wso2.carbon.identity.entitlement.endpoint/REQUIRED_CHANGES.md [2] https://wso2.org/jira/browse/IDENTITY-4985 Thank You Manujith On Fri, Aug 12, 2016 at 3:45 PM, Pushpalanka Jayawardhana <la...@wso2.com> wrote: > Hi Manujith, > > Good to see the project reaching final stages. > Please find the comments inline. > > Thanks, > Pushpalanka > > On Thu, Aug 11, 2016 at 1:23 PM, Manujith Pallewatte < > manujith...@gmail.com> wrote: > >> UPDATE >> >> Adding missing links >> [1] http://docs.oasis-open.org/xacml/xacml-rest/v1.0/csprd03 >> /xacml-rest-v1.0-csprd03.html >> [2] http://docs.oasis-open.org/xacml/xacml-json-http/v1.0/xa >> cml-json-http-v1.0.html >> [3] http://manzzup.github.io/wso2-entitlement-endpoint/devdoc >> >> On Thu, Aug 11, 2016 at 1:22 PM, Manujith Pallewatte < >> manujith...@gmail.com> wrote: >> >>> Hi all, >>> >>> To update on the current status >>> 1) The endpoint is fully compliant with the XACML REST profile as stated >>> here [1] >>> 2) It is also in accordance with the JSON XACML request/response profile >>> as stated in [2], except few things that require changes to balana >>> >> Can you please list down these things and the changes required in Balana, > so that we can address them at least later. > >> 3) Developer documentation was generated after fully commenting the >>> important codes and available for now at [3] >>> >> Additionally would be good to have the design details at github it self > as well or linked to your blog at http://manzzup.blogspot.com/ > 2016/08/gsoc-2016-rest-implementation-for-wso2.html. > >> >>> Hoping to work on user documentation and integration tests and submit a >>> new PR within next week >>> Any ideas for improvements / ideas / changes to be done prior to the PR? >>> >>> Thank You >>> Manujith >>> >>> >>> >>> On Wed, Jul 13, 2016 at 2:49 PM, Manujith Pallewatte < >>> manujith...@gmail.com> wrote: >>> >>>> Hi all, >>>> >>>> With the previous suggestions i'm currently working on having Swagger >>>> integrated to the service. According to the Apache CXF documentation [1] >>>> Swagger can be implemented easily by using its Swagger2Feature library. But >>>> their documentation provides no integration details. >>>> >>>> So i integrated the library using some other docs [2], which now shows >>>> no errors in integration, but when I try to access the api-docs usrl (ex: >>>> https://localhost:9443/wso2-entitlement/api-docs) it simply shows >>>> >>>> *"No service was found." * in the browser and gives [3] in the console >>>> as a warning. >>>> Please let me know if there's any solutions or any idea why this might >>>> be occurring. >>>> >>>> Thank You >>>> Manujith >>>> >>>> [1] https://cwiki.apache.org/confluence/pages/viewpage.actio >>>> n?pageId=61318164 >>>> [2] http://stackoverflow.com/questions/36035393/how-to-integ >>>> rate-swagger-tool-with-apache-cxf-rest-web-service-using-cxfnonsprin >>>> [3] >>>> [http-nio-9443-exec-31] WARN >>>> org.apache.cxf.transport.servlet.ServletController >>>> - Can't find the the request forhttps://localhost:9443/wso2 >>>> -entitlement/entitlement/api-docs's >>>> <https://www.google.com/url?q=https%3A%2F%2Flocalhost%3A9443%2Fwso2-entitlement%2Fentitlement%2Fapi-docs%27s=D=1=AFQjCNF1VqSODX6CxpcxwdMMPvQb_6OE9Q> >>>> Observer >>>> >>>> On Wed, Jul 6, 2016 at 6:24 PM, Manujith Pallewatte < >>>> manujith...@gmail.com> wrote: >>>> >>>>> Hi Pushpalanka, >>>>> >>>>> Thank you for the comments, I'm currently looking into Swagger >>&
Re: [Dev] [IS] RESTful Fine Grained Authorization-as-a-Service (AZaaS)
UPDATE Adding missing links [1] http://docs.oasis-open.org/xacml/xacml-rest/v1.0/csprd03/xacml-rest-v1.0-csprd03.html [2] http://docs.oasis-open.org/xacml/xacml-json-http/v1.0/xacml-json-http-v1.0.html [3] http://manzzup.github.io/wso2-entitlement-endpoint/devdoc On Thu, Aug 11, 2016 at 1:22 PM, Manujith Pallewatte <manujith...@gmail.com> wrote: > Hi all, > > To update on the current status > 1) The endpoint is fully compliant with the XACML REST profile as stated > here [1] > 2) It is also in accordance with the JSON XACML request/response profile > as stated in [2], except few things that require changes to balana > 3) Developer documentation was generated after fully commenting the > important codes and available for now at [3] > > Hoping to work on user documentation and integration tests and submit a > new PR within next week > Any ideas for improvements / ideas / changes to be done prior to the PR? > > Thank You > Manujith > > > > On Wed, Jul 13, 2016 at 2:49 PM, Manujith Pallewatte < > manujith...@gmail.com> wrote: > >> Hi all, >> >> With the previous suggestions i'm currently working on having Swagger >> integrated to the service. According to the Apache CXF documentation [1] >> Swagger can be implemented easily by using its Swagger2Feature library. But >> their documentation provides no integration details. >> >> So i integrated the library using some other docs [2], which now shows no >> errors in integration, but when I try to access the api-docs usrl (ex: >> https://localhost:9443/wso2-entitlement/api-docs) it simply shows >> >> *"No service was found." * in the browser and gives [3] in the console >> as a warning. >> Please let me know if there's any solutions or any idea why this might >> be occurring. >> >> Thank You >> Manujith >> >> [1] https://cwiki.apache.org/confluence/pages/viewpage.actio >> n?pageId=61318164 >> [2] http://stackoverflow.com/questions/36035393/how-to-integ >> rate-swagger-tool-with-apache-cxf-rest-web-service-using-cxfnonsprin >> [3] >> [http-nio-9443-exec-31] WARN >> org.apache.cxf.transport.servlet.ServletController >> - Can't find the the request forhttps://localhost:9443/wso2 >> -entitlement/entitlement/api-docs's >> <https://www.google.com/url?q=https%3A%2F%2Flocalhost%3A9443%2Fwso2-entitlement%2Fentitlement%2Fapi-docs%27s=D=1=AFQjCNF1VqSODX6CxpcxwdMMPvQb_6OE9Q> >> Observer >> >> On Wed, Jul 6, 2016 at 6:24 PM, Manujith Pallewatte < >> manujith...@gmail.com> wrote: >> >>> Hi Pushpalanka, >>> >>> Thank you for the comments, I'm currently looking into Swagger >>> Since it's already used in WSO2 API Manager, can i know if it's built on >>> CXF as well? In that case I can use existing swagger libraries than >>> introducing new ones. I found Swagger2Feature [1] library as in the Apache >>> CXF documentation. >>> >>> Hi Prabath, >>> Sorry i'm not familiar with those mentioned, can you clarify a bit more, >>> I would like to help in making any improvements >>> >>> Thank You >>> Manujith >>> >>> [1] http://cxf.apache.org/docs/swagger2feature.html >>> >>> On Tue, Jul 5, 2016 at 8:42 PM, Prabath Siriwardana <prab...@wso2.com> >>> wrote: >>> >>>> When we are implementing the REST profile XACML - can we implement it >>>> as a microservice on MSF4J? It needs to be an independent deployable unit - >>>> which should function with a set of policies loaded from the filesystem... >>>> Can we do this..? >>>> >>>> Thanks & regards, >>>> -Prbath >>>> >>>> On Mon, Jul 4, 2016 at 11:44 PM, Pushpalanka Jayawardhana < >>>> la...@wso2.com> wrote: >>>> >>>>> Hi Manujith, >>>>> >>>>> Please find the comments in line. >>>>> >>>>> On Mon, Jul 4, 2016 at 8:11 PM, Manujith Pallewatte < >>>>> manujith...@gmail.com> wrote: >>>>> >>>>>> Hi all, >>>>>> >>>>>> So to start working on the points discussed in the mid evaluation, >>>>>> first is to align the service with the REST profile of XACML 3.0 [1] >>>>>> But according to the spec only the following 2 resources are defined >>>>>> >>>>>> 1) home - entry point for REST service, returns links to other >>>>>> resources >>>>>> 2) pdp - resource that given a
Re: [Dev] [IS] RESTful Fine Grained Authorization-as-a-Service (AZaaS)
Hi all, To update on the current status 1) The endpoint is fully compliant with the XACML REST profile as stated here [1] 2) It is also in accordance with the JSON XACML request/response profile as stated in [2], except few things that require changes to balana 3) Developer documentation was generated after fully commenting the important codes and available for now at [3] Hoping to work on user documentation and integration tests and submit a new PR within next week Any ideas for improvements / ideas / changes to be done prior to the PR? Thank You Manujith On Wed, Jul 13, 2016 at 2:49 PM, Manujith Pallewatte <manujith...@gmail.com> wrote: > Hi all, > > With the previous suggestions i'm currently working on having Swagger > integrated to the service. According to the Apache CXF documentation [1] > Swagger can be implemented easily by using its Swagger2Feature library. But > their documentation provides no integration details. > > So i integrated the library using some other docs [2], which now shows no > errors in integration, but when I try to access the api-docs usrl (ex: > https://localhost:9443/wso2-entitlement/api-docs) it simply shows > > *"No service was found." * in the browser and gives [3] in the console as > a warning. > Please let me know if there's any solutions or any idea why this might > be occurring. > > Thank You > Manujith > > [1] https://cwiki.apache.org/confluence/pages/viewpage. > action?pageId=61318164 > [2] http://stackoverflow.com/questions/36035393/how-to- > integrate-swagger-tool-with-apache-cxf-rest-web-service-using-cxfnonsprin > [3] > [http-nio-9443-exec-31] WARN > org.apache.cxf.transport.servlet.ServletController > - Can't find the the request forhttps://localhost:9443/ > wso2-entitlement/entitlement/api-docs's > <https://www.google.com/url?q=https%3A%2F%2Flocalhost%3A9443%2Fwso2-entitlement%2Fentitlement%2Fapi-docs%27s=D=1=AFQjCNF1VqSODX6CxpcxwdMMPvQb_6OE9Q> > Observer > > On Wed, Jul 6, 2016 at 6:24 PM, Manujith Pallewatte <manujith...@gmail.com > > wrote: > >> Hi Pushpalanka, >> >> Thank you for the comments, I'm currently looking into Swagger >> Since it's already used in WSO2 API Manager, can i know if it's built on >> CXF as well? In that case I can use existing swagger libraries than >> introducing new ones. I found Swagger2Feature [1] library as in the Apache >> CXF documentation. >> >> Hi Prabath, >> Sorry i'm not familiar with those mentioned, can you clarify a bit more, >> I would like to help in making any improvements >> >> Thank You >> Manujith >> >> [1] http://cxf.apache.org/docs/swagger2feature.html >> >> On Tue, Jul 5, 2016 at 8:42 PM, Prabath Siriwardana <prab...@wso2.com> >> wrote: >> >>> When we are implementing the REST profile XACML - can we implement it as >>> a microservice on MSF4J? It needs to be an independent deployable unit - >>> which should function with a set of policies loaded from the filesystem... >>> Can we do this..? >>> >>> Thanks & regards, >>> -Prbath >>> >>> On Mon, Jul 4, 2016 at 11:44 PM, Pushpalanka Jayawardhana < >>> la...@wso2.com> wrote: >>> >>>> Hi Manujith, >>>> >>>> Please find the comments in line. >>>> >>>> On Mon, Jul 4, 2016 at 8:11 PM, Manujith Pallewatte < >>>> manujith...@gmail.com> wrote: >>>> >>>>> Hi all, >>>>> >>>>> So to start working on the points discussed in the mid evaluation, >>>>> first is to align the service with the REST profile of XACML 3.0 [1] >>>>> But according to the spec only the following 2 resources are defined >>>>> >>>>> 1) home - entry point for REST service, returns links to other >>>>> resources >>>>> 2) pdp - resource that given a XACML request presents the XACML >>>>> response >>>>> >>>>> but since the existing SOAP entitlement service exposes additional >>>>> services such as >>>>> getBooleanDecision, getDecisionByAttributes etc. there arises 2 issues >>>>> >>>>> 1) how to name those additional resources? >>>>> >>>> Let's have some convincing names for you as of now. We can refine them >>>> later in review. Try to have inputs from the topic "5.1 PROPER NAMING" from >>>> the rest api guideline while paper we pointed before. >>>> >>>>> 2) how to let the clients accessing the service know of the required >>>
Re: [Dev] [Balana] No getter for ObligationId in Obligation
Hi Farasath, Yeah I will do that, also if I use the the local snapshot of Balana in the project, I would have to change my Balana version in the IS pom dependency right? so it will give a merge conflict when i try to PR the new entitlement service? Thank You Manujith On Tue, Aug 2, 2016 at 10:04 PM, Farasath Ahamed <farasa...@wso2.com> wrote: > Hi Manujith, > > It would be great if you could send a PR as well :). > For now, you can fix this locally and continue working. > > > Thanks, > Farasath Ahamed > Software Engineer, WSO2 Inc.; http://wso2.com > Mobile: +94777603866 > Blog: blog.farazath.com > Twitter: @farazath619 <https://twitter.com/farazath619> > <http://wso2.com/signature> > > > > On Tue, Aug 2, 2016 at 1:29 PM, Manujith Pallewatte <manujith...@gmail.com > > wrote: > >> Hi, >> >> Posted in JIRA [1], thanks for all the help >> >> [1] https://wso2.org/jira/browse/IDENTITY-4889 >> >> >> On Tue, Aug 2, 2016 at 1:17 PM, Harsha Thirimanna <hars...@wso2.com> >> wrote: >> >>> Hi, >>> >>> You can create a JIRA here[1]. Follow the other ticket to get an idea. >>> >>> [1] https://wso2.org/jira/browse/IDENTITY >>> >>> *Harsha Thirimanna* >>> Associate Tech Lead | WSO2 >>> >>> Email: hars...@wso2.com >>> Mob: +94715186770 >>> Blog: http://harshathirimanna.blogspot.com/ >>> Twitter: http://twitter.com/harshathirimann >>> Linked-In: linked-in: >>> http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122 >>> <http://wso2.com/signature> >>> >>> On Tue, Aug 2, 2016 at 1:02 PM, Manujith Pallewatte < >>> manujith...@gmail.com> wrote: >>> >>>> Hi Harsha, >>>> >>>> Sorry I'm new to JIRA, can you point me where I could post the issue? >>>> Also i found a previous open issue in balana github issue list [1], >>>> should I open a new one in JIRA as well? >>>> >>>> [1] https://github.com/wso2/balana/issues/12 >>>> >>>> On Tue, Aug 2, 2016 at 12:48 PM, Harsha Thirimanna <hars...@wso2.com> >>>> wrote: >>>> >>>>> Yes, can you create a public JIRA >>>>> >>>>> *Harsha Thirimanna* >>>>> Associate Tech Lead | WSO2 >>>>> >>>>> Email: hars...@wso2.com >>>>> Mob: +94715186770 >>>>> Blog: http://harshathirimanna.blogspot.com/ >>>>> Twitter: http://twitter.com/harshathirimann >>>>> Linked-In: linked-in: >>>>> http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122 >>>>> <http://wso2.com/signature> >>>>> >>>>> On Tue, Aug 2, 2016 at 12:41 PM, Manujith Pallewatte < >>>>> manujith...@gmail.com> wrote: >>>>> >>>>>> Hi Harsha, >>>>>> >>>>>> Okay thank you, so it would be safe to assume that it will be there >>>>>> in the next Balana release? since I really need to use it >>>>>> >>>>>> Manujith >>>>>> >>>>>> On Tue, Aug 2, 2016 at 11:43 AM, Harsha Thirimanna <hars...@wso2.com> >>>>>> wrote: >>>>>> >>>>>>> I think, if there are any usage for that, we have to implement that >>>>>>> get method. >>>>>>> >>>>>>> *Harsha Thirimanna* >>>>>>> Associate Tech Lead | WSO2 >>>>>>> >>>>>>> Email: hars...@wso2.com >>>>>>> Mob: +94715186770 >>>>>>> Blog: http://harshathirimanna.blogspot.com/ >>>>>>> Twitter: http://twitter.com/harshathirimann >>>>>>> Linked-In: linked-in: >>>>>>> http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122 >>>>>>> <http://wso2.com/signature> >>>>>>> >>>>>>> On Tue, Aug 2, 2016 at 10:57 AM, Manujith Pallewatte < >>>>>>> manujith...@gmail.com> wrote: >>>>>>> >>>>>>>> Hi all, >>>>>>>> >>>>>>>> I'm in the process of implementing the XACML 3.0 JSON profile for >>>>>>>> requests and responses and in writing the responses, I need to obtain >>>>>>>> the >>>>>>>> Obligation Id of each Obligation [1]. But as see
Re: [Dev] [Balana] No getter for ObligationId in Obligation
Hi, Posted in JIRA [1], thanks for all the help [1] https://wso2.org/jira/browse/IDENTITY-4889 On Tue, Aug 2, 2016 at 1:17 PM, Harsha Thirimanna <hars...@wso2.com> wrote: > Hi, > > You can create a JIRA here[1]. Follow the other ticket to get an idea. > > [1] https://wso2.org/jira/browse/IDENTITY > > *Harsha Thirimanna* > Associate Tech Lead | WSO2 > > Email: hars...@wso2.com > Mob: +94715186770 > Blog: http://harshathirimanna.blogspot.com/ > Twitter: http://twitter.com/harshathirimann > Linked-In: linked-in: > http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122 > <http://wso2.com/signature> > > On Tue, Aug 2, 2016 at 1:02 PM, Manujith Pallewatte <manujith...@gmail.com > > wrote: > >> Hi Harsha, >> >> Sorry I'm new to JIRA, can you point me where I could post the issue? >> Also i found a previous open issue in balana github issue list [1], >> should I open a new one in JIRA as well? >> >> [1] https://github.com/wso2/balana/issues/12 >> >> On Tue, Aug 2, 2016 at 12:48 PM, Harsha Thirimanna <hars...@wso2.com> >> wrote: >> >>> Yes, can you create a public JIRA >>> >>> *Harsha Thirimanna* >>> Associate Tech Lead | WSO2 >>> >>> Email: hars...@wso2.com >>> Mob: +94715186770 >>> Blog: http://harshathirimanna.blogspot.com/ >>> Twitter: http://twitter.com/harshathirimann >>> Linked-In: linked-in: >>> http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122 >>> <http://wso2.com/signature> >>> >>> On Tue, Aug 2, 2016 at 12:41 PM, Manujith Pallewatte < >>> manujith...@gmail.com> wrote: >>> >>>> Hi Harsha, >>>> >>>> Okay thank you, so it would be safe to assume that it will be there in >>>> the next Balana release? since I really need to use it >>>> >>>> Manujith >>>> >>>> On Tue, Aug 2, 2016 at 11:43 AM, Harsha Thirimanna <hars...@wso2.com> >>>> wrote: >>>> >>>>> I think, if there are any usage for that, we have to implement that >>>>> get method. >>>>> >>>>> *Harsha Thirimanna* >>>>> Associate Tech Lead | WSO2 >>>>> >>>>> Email: hars...@wso2.com >>>>> Mob: +94715186770 >>>>> Blog: http://harshathirimanna.blogspot.com/ >>>>> Twitter: http://twitter.com/harshathirimann >>>>> Linked-In: linked-in: >>>>> http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122 >>>>> <http://wso2.com/signature> >>>>> >>>>> On Tue, Aug 2, 2016 at 10:57 AM, Manujith Pallewatte < >>>>> manujith...@gmail.com> wrote: >>>>> >>>>>> Hi all, >>>>>> >>>>>> I'm in the process of implementing the XACML 3.0 JSON profile for >>>>>> requests and responses and in writing the responses, I need to obtain the >>>>>> Obligation Id of each Obligation [1]. But as seen in [1], there's no >>>>>> public >>>>>> getter method available to obtain the Id from the Obligation object. >>>>>> Is there a workaround or can a getter be added? >>>>>> >>>>>> >>>>>> [1] >>>>>> https://github.com/wso2/balana/blob/master/modules/balana-core/src/main/java/org/wso2/balana/xacml3/Obligation.java >>>>>> >>>>>> Thank You >>>>>> Manujith >>>>>> >>>>>> -- >>>>>> >>>>>> >>>>>> >>>>>> Manujith Pallewatte >>>>>> [image: https://]about.me/manzzup >>>>>> >>>>>> <https://about.me/manzzup?promo=email_sig_source=email_sig_medium=external_link_campaign=chrome_ext> >>>>>> >>>>>> ___ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>> >>>> >>>> -- >>>> >>>> >>>> >>>> Manujith Pallewatte >>>> [image: https://]about.me/manzzup >>>> >>>> <https://about.me/manzzup?promo=email_sig_source=email_sig_medium=external_link_campaign=chrome_ext> >>>> >>> >>> >> >> >> -- >> >> >> >> Manujith Pallewatte >> [image: https://]about.me/manzzup >> >> <https://about.me/manzzup?promo=email_sig_source=email_sig_medium=external_link_campaign=chrome_ext> >> > > -- Manujith Pallewatte [image: https://]about.me/manzzup <https://about.me/manzzup?promo=email_sig_source=email_sig_medium=external_link_campaign=chrome_ext> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Balana] No getter for ObligationId in Obligation
Hi Harsha, Sorry I'm new to JIRA, can you point me where I could post the issue? Also i found a previous open issue in balana github issue list [1], should I open a new one in JIRA as well? [1] https://github.com/wso2/balana/issues/12 On Tue, Aug 2, 2016 at 12:48 PM, Harsha Thirimanna <hars...@wso2.com> wrote: > Yes, can you create a public JIRA > > *Harsha Thirimanna* > Associate Tech Lead | WSO2 > > Email: hars...@wso2.com > Mob: +94715186770 > Blog: http://harshathirimanna.blogspot.com/ > Twitter: http://twitter.com/harshathirimann > Linked-In: linked-in: > http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122 > <http://wso2.com/signature> > > On Tue, Aug 2, 2016 at 12:41 PM, Manujith Pallewatte < > manujith...@gmail.com> wrote: > >> Hi Harsha, >> >> Okay thank you, so it would be safe to assume that it will be there in >> the next Balana release? since I really need to use it >> >> Manujith >> >> On Tue, Aug 2, 2016 at 11:43 AM, Harsha Thirimanna <hars...@wso2.com> >> wrote: >> >>> I think, if there are any usage for that, we have to implement that get >>> method. >>> >>> *Harsha Thirimanna* >>> Associate Tech Lead | WSO2 >>> >>> Email: hars...@wso2.com >>> Mob: +94715186770 >>> Blog: http://harshathirimanna.blogspot.com/ >>> Twitter: http://twitter.com/harshathirimann >>> Linked-In: linked-in: >>> http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122 >>> <http://wso2.com/signature> >>> >>> On Tue, Aug 2, 2016 at 10:57 AM, Manujith Pallewatte < >>> manujith...@gmail.com> wrote: >>> >>>> Hi all, >>>> >>>> I'm in the process of implementing the XACML 3.0 JSON profile for >>>> requests and responses and in writing the responses, I need to obtain the >>>> Obligation Id of each Obligation [1]. But as seen in [1], there's no public >>>> getter method available to obtain the Id from the Obligation object. >>>> Is there a workaround or can a getter be added? >>>> >>>> >>>> [1] >>>> https://github.com/wso2/balana/blob/master/modules/balana-core/src/main/java/org/wso2/balana/xacml3/Obligation.java >>>> >>>> Thank You >>>> Manujith >>>> >>>> -- >>>> >>>> >>>> >>>> Manujith Pallewatte >>>> [image: https://]about.me/manzzup >>>> >>>> <https://about.me/manzzup?promo=email_sig_source=email_sig_medium=external_link_campaign=chrome_ext> >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >> >> >> -- >> >> >> >> Manujith Pallewatte >> [image: https://]about.me/manzzup >> >> <https://about.me/manzzup?promo=email_sig_source=email_sig_medium=external_link_campaign=chrome_ext> >> > > -- Manujith Pallewatte [image: https://]about.me/manzzup <https://about.me/manzzup?promo=email_sig_source=email_sig_medium=external_link_campaign=chrome_ext> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Balana] No getter for ObligationId in Obligation
Hi Harsha, Okay thank you, so it would be safe to assume that it will be there in the next Balana release? since I really need to use it Manujith On Tue, Aug 2, 2016 at 11:43 AM, Harsha Thirimanna <hars...@wso2.com> wrote: > I think, if there are any usage for that, we have to implement that get > method. > > *Harsha Thirimanna* > Associate Tech Lead | WSO2 > > Email: hars...@wso2.com > Mob: +94715186770 > Blog: http://harshathirimanna.blogspot.com/ > Twitter: http://twitter.com/harshathirimann > Linked-In: linked-in: > http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122 > <http://wso2.com/signature> > > On Tue, Aug 2, 2016 at 10:57 AM, Manujith Pallewatte < > manujith...@gmail.com> wrote: > >> Hi all, >> >> I'm in the process of implementing the XACML 3.0 JSON profile for >> requests and responses and in writing the responses, I need to obtain the >> Obligation Id of each Obligation [1]. But as seen in [1], there's no public >> getter method available to obtain the Id from the Obligation object. >> Is there a workaround or can a getter be added? >> >> >> [1] >> https://github.com/wso2/balana/blob/master/modules/balana-core/src/main/java/org/wso2/balana/xacml3/Obligation.java >> >> Thank You >> Manujith >> >> -- >> >> >> >> Manujith Pallewatte >> [image: https://]about.me/manzzup >> >> <https://about.me/manzzup?promo=email_sig_source=email_sig_medium=external_link_campaign=chrome_ext> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > -- Manujith Pallewatte [image: https://]about.me/manzzup <https://about.me/manzzup?promo=email_sig_source=email_sig_medium=external_link_campaign=chrome_ext> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Balana] No getter for ObligationId in Obligation
Hi all, I'm in the process of implementing the XACML 3.0 JSON profile for requests and responses and in writing the responses, I need to obtain the Obligation Id of each Obligation [1]. But as seen in [1], there's no public getter method available to obtain the Id from the Obligation object. Is there a workaround or can a getter be added? [1] https://github.com/wso2/balana/blob/master/modules/balana-core/src/main/java/org/wso2/balana/xacml3/Obligation.java Thank You Manujith -- Manujith Pallewatte [image: https://]about.me/manzzup <https://about.me/manzzup?promo=email_sig_source=email_sig_medium=external_link_campaign=chrome_ext> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [IS] XML String to Balana Node conversion
Hi Farasath,
Above code works perfectly! Thankx alot for the help.
Manujith
On Tue, Jul 26, 2016 at 12:32 AM, Farasath Ahamed <farasa...@wso2.com>
wrote:
> HI Manujith,
>
> You can get the required Node/Element argument to be passed to
> Balana Attributes Object using a code segment like below,
>
> try {
> DocumentBuilderFactory documentBuilderFactory =
> IdentityUtil.getSecuredDocumentBuilderFactory();
>
> DocumentBuilder docBuilder = documentBuilderFactory.newDocumentBuilder();
> ByteArrayInputStream is = new
> ByteArrayInputStream(xacmlRequestString.getBytes());
>
> // parse and build the document.
>
> Document document = docBuilder.parse(is);
> Element element = document.getDocumentElement();
>
> // use the element in the Balana constructor
>
>
> } catch (ParserConfigurationException | UnmarshallingException | IOException
> | SAXException e) {
> throw new SAMLSSOException("Error in unmarshalling SAML Request from the
> encoded String", e);
>
> }
>
>
>
> Thanks,
>
>
> Farasath Ahamed
> Software Engineer, WSO2 Inc.; http://wso2.com
> Mobile: +94777603866
> Blog: blog.farazath.com
> Twitter: @farazath619 <https://twitter.com/farazath619>
> <http://wso2.com/signature>
>
>
>
> On Mon, Jul 25, 2016 at 10:40 PM, Manujith Pallewatte <
> manujith...@gmail.com> wrote:
>
>> Hi all,
>>
>> As a part of the REST API for IS AZaaS, i'm in the process of parsing
>> JSON XACML 3.0 requests into the Balana RequestCtx Objects [1], thus
>> allowing me to directly evaluate them using the engine. In that process,
>> according to the JSON profile of XACML 3.0 [2], it is stated that the
>> content section of request should be converted sent as either a Base64
>> string or escaped XML String.
>>
>> By that the XML String is obtained, yet the Balana Attributes object [3]
>> only accepts type 'Node' as content. Thus I'm in search for a way of
>> parsing a XML String to Balana Node object, hopefully using an existing
>> method in the engine.
>>
>> Please let me know if there's any or any pointers I can work on.
>>
>> Thank You
>> Best Regards,
>> Manujith
>>
>>
>> [1]
>> https://github.com/wso2/balana/blob/master/modules/balana-core/src/main/java/org/wso2/balana/ctx/xacml3/RequestCtx.java
>> [2]
>> http://docs.oasis-open.org/xacml/xacml-json-http/v1.0/xacml-json-http-v1.0.html
>> [3]
>> https://github.com/wso2/balana/blob/master/modules/balana-core/src/main/java/org/wso2/balana/xacml3/Attributes.java
>>
>> --
>>
>>
>>
>> Manujith Pallewatte
>> [image: https://]about.me/manzzup
>>
>> <https://about.me/manzzup?promo=email_sig_source=email_sig_medium=external_link_campaign=chrome_ext>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
--
Manujith Pallewatte
[image: https://]about.me/manzzup
<https://about.me/manzzup?promo=email_sig_source=email_sig_medium=external_link_campaign=chrome_ext>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Private constructor of Balana MultiRequests
Hi all, As a part of the ongoing REST API for IS AZaaS, I'm in need of creating MultiRequests objects [1] from a given JSON String. But when checked with source, MultiRequests class has only 1 constructor which is private. Please explain if it needs to be private and if so, any mechanism through which I can instantiate a MultiRequests object without using the getInstance method (Since it requires an XML node which I donot posses) Thank You Best Regards, Manujith -- Manujith Pallewatte [image: https://]about.me/manzzup <https://about.me/manzzup?promo=email_sig_source=email_sig_medium=external_link_campaign=chrome_ext> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [IS] XML String to Balana Node conversion
Hi all, As a part of the REST API for IS AZaaS, i'm in the process of parsing JSON XACML 3.0 requests into the Balana RequestCtx Objects [1], thus allowing me to directly evaluate them using the engine. In that process, according to the JSON profile of XACML 3.0 [2], it is stated that the content section of request should be converted sent as either a Base64 string or escaped XML String. By that the XML String is obtained, yet the Balana Attributes object [3] only accepts type 'Node' as content. Thus I'm in search for a way of parsing a XML String to Balana Node object, hopefully using an existing method in the engine. Please let me know if there's any or any pointers I can work on. Thank You Best Regards, Manujith [1] https://github.com/wso2/balana/blob/master/modules/balana-core/src/main/java/org/wso2/balana/ctx/xacml3/RequestCtx.java [2] http://docs.oasis-open.org/xacml/xacml-json-http/v1.0/xacml-json-http-v1.0.html [3] https://github.com/wso2/balana/blob/master/modules/balana-core/src/main/java/org/wso2/balana/xacml3/Attributes.java -- Manujith Pallewatte [image: https://]about.me/manzzup <https://about.me/manzzup?promo=email_sig_source=email_sig_medium=external_link_campaign=chrome_ext> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [IS] RESTful Fine Grained Authorization-as-a-Service (AZaaS)
Hi all, With the previous suggestions i'm currently working on having Swagger integrated to the service. According to the Apache CXF documentation [1] Swagger can be implemented easily by using its Swagger2Feature library. But their documentation provides no integration details. So i integrated the library using some other docs [2], which now shows no errors in integration, but when I try to access the api-docs usrl (ex: https://localhost:9443/wso2-entitlement/api-docs) it simply shows *"No service was found." * in the browser and gives [3] in the console as a warning. Please let me know if there's any solutions or any idea why this might be occurring. Thank You Manujith [1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61318164 [2] http://stackoverflow.com/questions/36035393/how-to-integrate-swagger-tool-with-apache-cxf-rest-web-service-using-cxfnonsprin [3] [http-nio-9443-exec-31] WARN org.apache.cxf.transport.servlet.ServletController - Can't find the the request forhttps://localhost:9443/wso2-entitlement/entitlement/api-docs's <https://www.google.com/url?q=https%3A%2F%2Flocalhost%3A9443%2Fwso2-entitlement%2Fentitlement%2Fapi-docs%27s=D=1=AFQjCNF1VqSODX6CxpcxwdMMPvQb_6OE9Q> Observer On Wed, Jul 6, 2016 at 6:24 PM, Manujith Pallewatte <manujith...@gmail.com> wrote: > Hi Pushpalanka, > > Thank you for the comments, I'm currently looking into Swagger > Since it's already used in WSO2 API Manager, can i know if it's built on > CXF as well? In that case I can use existing swagger libraries than > introducing new ones. I found Swagger2Feature [1] library as in the Apache > CXF documentation. > > Hi Prabath, > Sorry i'm not familiar with those mentioned, can you clarify a bit more, I > would like to help in making any improvements > > Thank You > Manujith > > [1] http://cxf.apache.org/docs/swagger2feature.html > > On Tue, Jul 5, 2016 at 8:42 PM, Prabath Siriwardana <prab...@wso2.com> > wrote: > >> When we are implementing the REST profile XACML - can we implement it as >> a microservice on MSF4J? It needs to be an independent deployable unit - >> which should function with a set of policies loaded from the filesystem... >> Can we do this..? >> >> Thanks & regards, >> -Prbath >> >> On Mon, Jul 4, 2016 at 11:44 PM, Pushpalanka Jayawardhana <la...@wso2.com >> > wrote: >> >>> Hi Manujith, >>> >>> Please find the comments in line. >>> >>> On Mon, Jul 4, 2016 at 8:11 PM, Manujith Pallewatte < >>> manujith...@gmail.com> wrote: >>> >>>> Hi all, >>>> >>>> So to start working on the points discussed in the mid evaluation, >>>> first is to align the service with the REST profile of XACML 3.0 [1] >>>> But according to the spec only the following 2 resources are defined >>>> >>>> 1) home - entry point for REST service, returns links to other resources >>>> 2) pdp - resource that given a XACML request presents the XACML response >>>> >>>> but since the existing SOAP entitlement service exposes additional >>>> services such as >>>> getBooleanDecision, getDecisionByAttributes etc. there arises 2 issues >>>> >>>> 1) how to name those additional resources? >>>> >>> Let's have some convincing names for you as of now. We can refine them >>> later in review. Try to have inputs from the topic "5.1 PROPER NAMING" from >>> the rest api guideline while paper we pointed before. >>> >>>> 2) how to let the clients accessing the service know of the required >>>> structure of each of these requests that are not defined in the XACML spec? >>>> >>> Please have a look at the possibility of using swagger for this. This is >>> already used in WSO2 Api Manager[1], but not yet in WSO2 IS. Would be great >>> if you can evaluate the possibility of using it. Basic idea is to >>> represent the REST API according to Swagger specification similar to WSDL >>> we have for SOAP. >>> >>> [1] - >>> https://docs.wso2.com/display/AM1100/Edit+an+API+Using+the+Swagger+UI >>> >>>> >>>> Please provide your suggestions on this >>>> >>>> Thank You >>>> Best Regards, >>>> Manujith >>>> >>>> [1] >>>> http://docs.oasis-open.org/xacml/xacml-rest/v1.0/csprd03/xacml-rest-v1.0-csprd03.html >>>> >>>> On Thu, Jun 23, 2016 at 3:42 PM, Omindu Rathnaweera <omi...@wso2.com> >>>> wrote: >>>> >>>>> Good Wo
Re: [Dev] [IS] RESTful Fine Grained Authorization-as-a-Service (AZaaS)
Hi Pushpalanka, Thank you for the comments, I'm currently looking into Swagger Since it's already used in WSO2 API Manager, can i know if it's built on CXF as well? In that case I can use existing swagger libraries than introducing new ones. I found Swagger2Feature [1] library as in the Apache CXF documentation. Hi Prabath, Sorry i'm not familiar with those mentioned, can you clarify a bit more, I would like to help in making any improvements Thank You Manujith [1] http://cxf.apache.org/docs/swagger2feature.html On Tue, Jul 5, 2016 at 8:42 PM, Prabath Siriwardana <prab...@wso2.com> wrote: > When we are implementing the REST profile XACML - can we implement it as a > microservice on MSF4J? It needs to be an independent deployable unit - > which should function with a set of policies loaded from the filesystem... > Can we do this..? > > Thanks & regards, > -Prbath > > On Mon, Jul 4, 2016 at 11:44 PM, Pushpalanka Jayawardhana <la...@wso2.com> > wrote: > >> Hi Manujith, >> >> Please find the comments in line. >> >> On Mon, Jul 4, 2016 at 8:11 PM, Manujith Pallewatte < >> manujith...@gmail.com> wrote: >> >>> Hi all, >>> >>> So to start working on the points discussed in the mid evaluation, first >>> is to align the service with the REST profile of XACML 3.0 [1] >>> But according to the spec only the following 2 resources are defined >>> >>> 1) home - entry point for REST service, returns links to other resources >>> 2) pdp - resource that given a XACML request presents the XACML response >>> >>> but since the existing SOAP entitlement service exposes additional >>> services such as >>> getBooleanDecision, getDecisionByAttributes etc. there arises 2 issues >>> >>> 1) how to name those additional resources? >>> >> Let's have some convincing names for you as of now. We can refine them >> later in review. Try to have inputs from the topic "5.1 PROPER NAMING" from >> the rest api guideline while paper we pointed before. >> >>> 2) how to let the clients accessing the service know of the required >>> structure of each of these requests that are not defined in the XACML spec? >>> >> Please have a look at the possibility of using swagger for this. This is >> already used in WSO2 Api Manager[1], but not yet in WSO2 IS. Would be great >> if you can evaluate the possibility of using it. Basic idea is to >> represent the REST API according to Swagger specification similar to WSDL >> we have for SOAP. >> >> [1] - >> https://docs.wso2.com/display/AM1100/Edit+an+API+Using+the+Swagger+UI >> >>> >>> Please provide your suggestions on this >>> >>> Thank You >>> Best Regards, >>> Manujith >>> >>> [1] >>> http://docs.oasis-open.org/xacml/xacml-rest/v1.0/csprd03/xacml-rest-v1.0-csprd03.html >>> >>> On Thu, Jun 23, 2016 at 3:42 PM, Omindu Rathnaweera <omi...@wso2.com> >>> wrote: >>> >>>> Good Work Manujith! >>>> >>>> Adding to this. Figure out a way to drop null values from the JSON >>>> response with Jackson level configurations. Also have a look at XACML JSON >>>> profile [1]. It will have guidelines on dealing with JSON inputs/outputs. >>>> >>>> [1] - >>>> http://docs.oasis-open.org/xacml/xacml-json-http/v1.0/xacml-json-http-v1.0.html >>>> >>>> Regards, >>>> Omindu. >>>> >>>> On Thu, Jun 23, 2016 at 3:31 PM, Manujith Pallewatte < >>>> manujith...@gmail.com> wrote: >>>> >>>>> Hi all, >>>>> >>>>> We had the mid-evaluation review, and I've summarized the key points >>>>> discussed here >>>>> >>>>> 1) Prioritize on the complete JSON implementation for all 5 services >>>>> methods >>>>> 2) Comply the service fully with XACML 3.0 REST specification (Read on >>>>> the spec and get a firm understanding on all key concepts) >>>>> 3) Leave the hard coded authenticators as it is for now >>>>> 4) Using custom client / server exception to be returned in a case of >>>>> an exception >>>>> 5) Follow the code quality guidelines (specially in the cases of >>>>> improper exception handling) >>>>> >>>>> Special thanks to everyone for their time in reviewing. >>>>> >>>>> Thank You, >>>>> Manujith >>>>>
Re: [Dev] [IS] RESTful Fine Grained Authorization-as-a-Service (AZaaS)
Hi all, So to start working on the points discussed in the mid evaluation, first is to align the service with the REST profile of XACML 3.0 [1] But according to the spec only the following 2 resources are defined 1) home - entry point for REST service, returns links to other resources 2) pdp - resource that given a XACML request presents the XACML response but since the existing SOAP entitlement service exposes additional services such as getBooleanDecision, getDecisionByAttributes etc. there arises 2 issues 1) how to name those additional resources? 2) how to let the clients accessing the service know of the required structure of each of these requests that are not defined in the XACML spec? Please provide your suggestions on this Thank You Best Regards, Manujith [1] http://docs.oasis-open.org/xacml/xacml-rest/v1.0/csprd03/xacml-rest-v1.0-csprd03.html On Thu, Jun 23, 2016 at 3:42 PM, Omindu Rathnaweera <omi...@wso2.com> wrote: > Good Work Manujith! > > Adding to this. Figure out a way to drop null values from the JSON > response with Jackson level configurations. Also have a look at XACML JSON > profile [1]. It will have guidelines on dealing with JSON inputs/outputs. > > [1] - > http://docs.oasis-open.org/xacml/xacml-json-http/v1.0/xacml-json-http-v1.0.html > > Regards, > Omindu. > > On Thu, Jun 23, 2016 at 3:31 PM, Manujith Pallewatte < > manujith...@gmail.com> wrote: > >> Hi all, >> >> We had the mid-evaluation review, and I've summarized the key points >> discussed here >> >> 1) Prioritize on the complete JSON implementation for all 5 services >> methods >> 2) Comply the service fully with XACML 3.0 REST specification (Read on >> the spec and get a firm understanding on all key concepts) >> 3) Leave the hard coded authenticators as it is for now >> 4) Using custom client / server exception to be returned in a case of an >> exception >> 5) Follow the code quality guidelines (specially in the cases of improper >> exception handling) >> >> Special thanks to everyone for their time in reviewing. >> >> Thank You, >> Manujith >> >> On Sun, Jun 12, 2016 at 10:43 PM, Manujith Pallewatte < >> manujith...@gmail.com> wrote: >> >>> Hi all, >>> >>> After refactoring and reviewing code using above suggestions, I added a >>> PR, which can be found at [1] >>> >>> Regards, >>> Manujith >>> >>> [1] https://github.com/wso2/carbon-identity-framework/pull/282 >>> >>> On Sat, Jun 11, 2016 at 12:52 PM, Manujith Pallewatte < >>> manujith...@gmail.com> wrote: >>> >>>> Hi Manuranga, >>>> >>>> I did referred to the guidelines, but was not successful in figuring >>>> out suitable end point names. So Pushpalanka suggested to take community's >>>> ideas in naming them. Any pointers as for which I can improve the names? >>>> According to the guide it says to identify the resources first >>>> Going on that, I identified the Policy Decision, Entitlement Attributes >>>> and Entitlements as resources, but since some resources have only one >>>> methods call in it, having a separate path seem redundant. And didnt follow >>>> much from there, please let me know your ideas on the resource >>>> identification >>>> >>>> Thank You >>>> Regards, >>>> Manujith >>>> >>>> On Sat, Jun 11, 2016 at 12:21 AM, Manuranga Perera <m...@wso2.com> >>>> wrote: >>>> >>>>> Hi Manujith, >>>>> >>>>> Please have a look at WSO2 REST API guideline [1]. This will help you >>>>> to improve the URL nameing. >>>>> >>>>> [1] http://wso2.com/whitepapers/wso2-rest-apis-design-guidelines/ >>>>> >>>>> On Thu, Jun 9, 2016 at 3:49 PM, Manujith Pallewatte < >>>>> manujith...@gmail.com> wrote: >>>>> >>>>>> Hi Pushpalanka, >>>>>> >>>>>> Was confused in the PR procedure, and figured that I forgot to >>>>>> initialize the github repo as you have mentioned in a previous message. >>>>>> So the new location of the codebase is at [1] >>>>>> Over the weekend, I'll fix any remaining issues and send the PR >>>>>> For now I have used the wso2-codestyle given by Omindu and >>>>>> reformatted the code >>>>>> and added Findbug as well. >>>>>> >>>>>> Thank You >>>>>>
Re: [Dev] [IS] RESTful Fine Grained Authorization-as-a-Service (AZaaS)
Hi all, We had the mid-evaluation review, and I've summarized the key points discussed here 1) Prioritize on the complete JSON implementation for all 5 services methods 2) Comply the service fully with XACML 3.0 REST specification (Read on the spec and get a firm understanding on all key concepts) 3) Leave the hard coded authenticators as it is for now 4) Using custom client / server exception to be returned in a case of an exception 5) Follow the code quality guidelines (specially in the cases of improper exception handling) Special thanks to everyone for their time in reviewing. Thank You, Manujith On Sun, Jun 12, 2016 at 10:43 PM, Manujith Pallewatte <manujith...@gmail.com > wrote: > Hi all, > > After refactoring and reviewing code using above suggestions, I added a > PR, which can be found at [1] > > Regards, > Manujith > > [1] https://github.com/wso2/carbon-identity-framework/pull/282 > > On Sat, Jun 11, 2016 at 12:52 PM, Manujith Pallewatte < > manujith...@gmail.com> wrote: > >> Hi Manuranga, >> >> I did referred to the guidelines, but was not successful in figuring out >> suitable end point names. So Pushpalanka suggested to take community's >> ideas in naming them. Any pointers as for which I can improve the names? >> According to the guide it says to identify the resources first >> Going on that, I identified the Policy Decision, Entitlement Attributes >> and Entitlements as resources, but since some resources have only one >> methods call in it, having a separate path seem redundant. And didnt follow >> much from there, please let me know your ideas on the resource >> identification >> >> Thank You >> Regards, >> Manujith >> >> On Sat, Jun 11, 2016 at 12:21 AM, Manuranga Perera <m...@wso2.com> wrote: >> >>> Hi Manujith, >>> >>> Please have a look at WSO2 REST API guideline [1]. This will help you to >>> improve the URL nameing. >>> >>> [1] http://wso2.com/whitepapers/wso2-rest-apis-design-guidelines/ >>> >>> On Thu, Jun 9, 2016 at 3:49 PM, Manujith Pallewatte < >>> manujith...@gmail.com> wrote: >>> >>>> Hi Pushpalanka, >>>> >>>> Was confused in the PR procedure, and figured that I forgot to >>>> initialize the github repo as you have mentioned in a previous message. >>>> So the new location of the codebase is at [1] >>>> Over the weekend, I'll fix any remaining issues and send the PR >>>> For now I have used the wso2-codestyle given by Omindu and reformatted >>>> the code >>>> and added Findbug as well. >>>> >>>> Thank You >>>> Manujith >>>> >>>> [1] >>>> https://github.com/ManZzup/identity-framework/tree/master/components/entitlement/org.wso2.carbon.identity.entitlement.endpoint >>>> >>>> On Wed, Jun 8, 2016 at 11:35 AM, Pushpalanka Jayawardhana < >>>> la...@wso2.com> wrote: >>>> >>>>> >>>>> >>>>> On Tue, Jun 7, 2016 at 11:01 AM, Manujith Pallewatte < >>>>> manujith...@gmail.com> wrote: >>>>> >>>>>> Hi all, >>>>>> >>>>>> Code is almost all refracted (apart from the part where >>>>>> authenticators are hard coded) and it' is available at [1] >>>>>> I have attached a readme so everyone can help with testing it. But >>>>>> there's still an issue remaining to debug with the *entitled-attribs >>>>>> *service call, that came up in preliminary testing by Omindu. >>>>>> >>>>>> Thank You Omindu, I will use the formatting configs and format the >>>>>> code asap. For now i added a gitignore as in the sample you sent, but I >>>>>> left *target *directory intact so that i can share the war file >>>>>> through the repo. >>>>>> >>>>>> Also for the PR, to which repo should I send the PR for? Or shall I >>>>>> wait for further testing of the code so that we can minimize any bugs? >>>>>> >>>>> If code refactoring, formatting, cleanup are done, you have run >>>>> Findbug plugin(This is a plugin that can integrate to IDE. If you already >>>>> haven't try it.) and fixed any issues reported against code and >>>>> functionality is working, we are OK to review the code. You can further >>>>> test the code and fix the bugs while integrating any review comments we >>>>> put &
Re: [Dev] [IS] RESTful Fine Grained Authorization-as-a-Service (AZaaS)
Hi all, After refactoring and reviewing code using above suggestions, I added a PR, which can be found at [1] Regards, Manujith [1] https://github.com/wso2/carbon-identity-framework/pull/282 On Sat, Jun 11, 2016 at 12:52 PM, Manujith Pallewatte <manujith...@gmail.com > wrote: > Hi Manuranga, > > I did referred to the guidelines, but was not successful in figuring out > suitable end point names. So Pushpalanka suggested to take community's > ideas in naming them. Any pointers as for which I can improve the names? > According to the guide it says to identify the resources first > Going on that, I identified the Policy Decision, Entitlement Attributes > and Entitlements as resources, but since some resources have only one > methods call in it, having a separate path seem redundant. And didnt follow > much from there, please let me know your ideas on the resource > identification > > Thank You > Regards, > Manujith > > On Sat, Jun 11, 2016 at 12:21 AM, Manuranga Perera <m...@wso2.com> wrote: > >> Hi Manujith, >> >> Please have a look at WSO2 REST API guideline [1]. This will help you to >> improve the URL nameing. >> >> [1] http://wso2.com/whitepapers/wso2-rest-apis-design-guidelines/ >> >> On Thu, Jun 9, 2016 at 3:49 PM, Manujith Pallewatte < >> manujith...@gmail.com> wrote: >> >>> Hi Pushpalanka, >>> >>> Was confused in the PR procedure, and figured that I forgot to >>> initialize the github repo as you have mentioned in a previous message. >>> So the new location of the codebase is at [1] >>> Over the weekend, I'll fix any remaining issues and send the PR >>> For now I have used the wso2-codestyle given by Omindu and reformatted >>> the code >>> and added Findbug as well. >>> >>> Thank You >>> Manujith >>> >>> [1] >>> https://github.com/ManZzup/identity-framework/tree/master/components/entitlement/org.wso2.carbon.identity.entitlement.endpoint >>> >>> On Wed, Jun 8, 2016 at 11:35 AM, Pushpalanka Jayawardhana < >>> la...@wso2.com> wrote: >>> >>>> >>>> >>>> On Tue, Jun 7, 2016 at 11:01 AM, Manujith Pallewatte < >>>> manujith...@gmail.com> wrote: >>>> >>>>> Hi all, >>>>> >>>>> Code is almost all refracted (apart from the part where authenticators >>>>> are hard coded) and it' is available at [1] >>>>> I have attached a readme so everyone can help with testing it. But >>>>> there's still an issue remaining to debug with the *entitled-attribs >>>>> *service >>>>> call, that came up in preliminary testing by Omindu. >>>>> >>>>> Thank You Omindu, I will use the formatting configs and format the >>>>> code asap. For now i added a gitignore as in the sample you sent, but I >>>>> left *target *directory intact so that i can share the war file >>>>> through the repo. >>>>> >>>>> Also for the PR, to which repo should I send the PR for? Or shall I >>>>> wait for further testing of the code so that we can minimize any bugs? >>>>> >>>> If code refactoring, formatting, cleanup are done, you have run Findbug >>>> plugin(This is a plugin that can integrate to IDE. If you already haven't >>>> try it.) and fixed any issues reported against code and functionality is >>>> working, we are OK to review the code. You can further test the code and >>>> fix the bugs while integrating any review comments we put on the PR. >>>> >>>> "Please share the code progress via Github, once you are satisfied >>>> with refactoring. >>>> Please fork [1] to your private repo, and at location [2], you may have >>>> a new component named 'org.wso2.carbon.identity.entitlement.endpoint' where >>>> the implementation can reside. >>>> >>>> [1] - https://github.com/wso2/carbon-identity-framework >>>> [2] - >>>> https://github.com/wso2/carbon-identity-framework/tree/master/components/entitlement >>>> " >>>> >>>>> >>>>> [1] https://github.com/ManZzup/identity-entitlement-endpoint >>>>> >>>>> Thank You, >>>>> Best Regards >>>>> Manujith >>>>> >>>>> On Tue, Jun 7, 2016 at 10:30 AM, Omindu Rathnaweera <omi...@wso2.com> >>>>> wrote: >>>>> >>>>>> Addi
Re: [Dev] [IS] RESTful Fine Grained Authorization-as-a-Service (AZaaS)
Hi Manuranga, I did referred to the guidelines, but was not successful in figuring out suitable end point names. So Pushpalanka suggested to take community's ideas in naming them. Any pointers as for which I can improve the names? According to the guide it says to identify the resources first Going on that, I identified the Policy Decision, Entitlement Attributes and Entitlements as resources, but since some resources have only one methods call in it, having a separate path seem redundant. And didnt follow much from there, please let me know your ideas on the resource identification Thank You Regards, Manujith On Sat, Jun 11, 2016 at 12:21 AM, Manuranga Perera <m...@wso2.com> wrote: > Hi Manujith, > > Please have a look at WSO2 REST API guideline [1]. This will help you to > improve the URL nameing. > > [1] http://wso2.com/whitepapers/wso2-rest-apis-design-guidelines/ > > On Thu, Jun 9, 2016 at 3:49 PM, Manujith Pallewatte <manujith...@gmail.com > > wrote: > >> Hi Pushpalanka, >> >> Was confused in the PR procedure, and figured that I forgot to initialize >> the github repo as you have mentioned in a previous message. >> So the new location of the codebase is at [1] >> Over the weekend, I'll fix any remaining issues and send the PR >> For now I have used the wso2-codestyle given by Omindu and reformatted >> the code >> and added Findbug as well. >> >> Thank You >> Manujith >> >> [1] >> https://github.com/ManZzup/identity-framework/tree/master/components/entitlement/org.wso2.carbon.identity.entitlement.endpoint >> >> On Wed, Jun 8, 2016 at 11:35 AM, Pushpalanka Jayawardhana <la...@wso2.com >> > wrote: >> >>> >>> >>> On Tue, Jun 7, 2016 at 11:01 AM, Manujith Pallewatte < >>> manujith...@gmail.com> wrote: >>> >>>> Hi all, >>>> >>>> Code is almost all refracted (apart from the part where authenticators >>>> are hard coded) and it' is available at [1] >>>> I have attached a readme so everyone can help with testing it. But >>>> there's still an issue remaining to debug with the *entitled-attribs >>>> *service >>>> call, that came up in preliminary testing by Omindu. >>>> >>>> Thank You Omindu, I will use the formatting configs and format the code >>>> asap. For now i added a gitignore as in the sample you sent, but I left >>>> *target >>>> *directory intact so that i can share the war file through the repo. >>>> >>>> Also for the PR, to which repo should I send the PR for? Or shall I >>>> wait for further testing of the code so that we can minimize any bugs? >>>> >>> If code refactoring, formatting, cleanup are done, you have run Findbug >>> plugin(This is a plugin that can integrate to IDE. If you already haven't >>> try it.) and fixed any issues reported against code and functionality is >>> working, we are OK to review the code. You can further test the code and >>> fix the bugs while integrating any review comments we put on the PR. >>> >>> "Please share the code progress via Github, once you are satisfied with >>> refactoring. >>> Please fork [1] to your private repo, and at location [2], you may have >>> a new component named 'org.wso2.carbon.identity.entitlement.endpoint' where >>> the implementation can reside. >>> >>> [1] - https://github.com/wso2/carbon-identity-framework >>> [2] - >>> https://github.com/wso2/carbon-identity-framework/tree/master/components/entitlement >>> " >>> >>>> >>>> [1] https://github.com/ManZzup/identity-entitlement-endpoint >>>> >>>> Thank You, >>>> Best Regards >>>> Manujith >>>> >>>> On Tue, Jun 7, 2016 at 10:30 AM, Omindu Rathnaweera <omi...@wso2.com> >>>> wrote: >>>> >>>>> Adding a .gitignore to the repo will be the easiest way to keep the >>>>> unwanted files away from the repo. See [1]. >>>>> >>>>> [1] - >>>>> https://github.com/wso2/carbon-identity-framework/blob/master/.gitignore >>>>> >>>>> Regards, >>>>> Omindu >>>>> >>>>> On Tue, Jun 7, 2016 at 10:26 AM, Pushpalanka Jayawardhana < >>>>> la...@wso2.com> wrote: >>>>> >>>>>> Hi Manujith, >>>>>> >>>>>> The IDE specific files(.iml) or code can be removed from the >>&g
Re: [Dev] [IS] RESTful Fine Grained Authorization-as-a-Service (AZaaS)
Hi Pushpalanka, Was confused in the PR procedure, and figured that I forgot to initialize the github repo as you have mentioned in a previous message. So the new location of the codebase is at [1] Over the weekend, I'll fix any remaining issues and send the PR For now I have used the wso2-codestyle given by Omindu and reformatted the code and added Findbug as well. Thank You Manujith [1] https://github.com/ManZzup/identity-framework/tree/master/components/entitlement/org.wso2.carbon.identity.entitlement.endpoint On Wed, Jun 8, 2016 at 11:35 AM, Pushpalanka Jayawardhana <la...@wso2.com> wrote: > > > On Tue, Jun 7, 2016 at 11:01 AM, Manujith Pallewatte < > manujith...@gmail.com> wrote: > >> Hi all, >> >> Code is almost all refracted (apart from the part where authenticators >> are hard coded) and it' is available at [1] >> I have attached a readme so everyone can help with testing it. But >> there's still an issue remaining to debug with the *entitled-attribs *service >> call, that came up in preliminary testing by Omindu. >> >> Thank You Omindu, I will use the formatting configs and format the code >> asap. For now i added a gitignore as in the sample you sent, but I left >> *target >> *directory intact so that i can share the war file through the repo. >> >> Also for the PR, to which repo should I send the PR for? Or shall I wait >> for further testing of the code so that we can minimize any bugs? >> > If code refactoring, formatting, cleanup are done, you have run Findbug > plugin(This is a plugin that can integrate to IDE. If you already haven't > try it.) and fixed any issues reported against code and functionality is > working, we are OK to review the code. You can further test the code and > fix the bugs while integrating any review comments we put on the PR. > > "Please share the code progress via Github, once you are satisfied with > refactoring. > Please fork [1] to your private repo, and at location [2], you may have a > new component named 'org.wso2.carbon.identity.entitlement.endpoint' where > the implementation can reside. > > [1] - https://github.com/wso2/carbon-identity-framework > [2] - > https://github.com/wso2/carbon-identity-framework/tree/master/components/entitlement > " > >> >> [1] https://github.com/ManZzup/identity-entitlement-endpoint >> >> Thank You, >> Best Regards >> Manujith >> >> On Tue, Jun 7, 2016 at 10:30 AM, Omindu Rathnaweera <omi...@wso2.com> >> wrote: >> >>> Adding a .gitignore to the repo will be the easiest way to keep the >>> unwanted files away from the repo. See [1]. >>> >>> [1] - >>> https://github.com/wso2/carbon-identity-framework/blob/master/.gitignore >>> >>> Regards, >>> Omindu >>> >>> On Tue, Jun 7, 2016 at 10:26 AM, Pushpalanka Jayawardhana < >>> la...@wso2.com> wrote: >>> >>>> Hi Manujith, >>>> >>>> The IDE specific files(.iml) or code can be removed from the repository. >>>> Once the code refactoring is done and code is cleaned please feel free >>>> to send the PR. Then we can easily comment on the code. >>>> >>>> Thanks, >>>> Pushpalanka >>>> >>>> >>>> On Tue, Jun 7, 2016 at 10:12 AM, Omindu Rathnaweera <omi...@wso2.com> >>>> wrote: >>>> >>>>> Hi Manujith, >>>>> >>>>> Better if you can clean up the unnecessary code and do some code >>>>> refactoring. We can do another round of testing once you fix the issues I >>>>> have mention. You can use the attached Idea Code Formatting Template [1]. >>>>> >>>>> To apply the template, follow the steps below. >>>>> >>>>> 1. In IDEA settings, goto Editor -> Code Style. >>>>> 2. Click 'Manage' then 'Save As...' an existing scheme with the name >>>>> 'wso2-codestyle' and Close the IDE. >>>>> 3. Goto ~/.IntelliJIdea16/config/codestyles directory and replace the >>>>> 'wso2-codestyle.xml' file with the attached one. >>>>> >>>>> [1] - >>>>> https://drive.google.com/file/d/0BzRDbfbIaYjCSzhGRUR1aGdlTXM/view?usp=sharing >>>>> >>>>> Regards, >>>>> Omindu. >>>>> >>>>> >>>>> On Mon, Jun 6, 2016 at 8:29 AM, Manujith Pallewatte < >>>>> manujith...@gmail.com> wrote: >>>>> >>>>>> Hi all, >>>>>> >>&g
Re: [Dev] [IS] RESTful Fine Grained Authorization-as-a-Service (AZaaS)
Hi all, Code is almost all refracted (apart from the part where authenticators are hard coded) and it' is available at [1] I have attached a readme so everyone can help with testing it. But there's still an issue remaining to debug with the *entitled-attribs *service call, that came up in preliminary testing by Omindu. Thank You Omindu, I will use the formatting configs and format the code asap. For now i added a gitignore as in the sample you sent, but I left *target *directory intact so that i can share the war file through the repo. Also for the PR, to which repo should I send the PR for? Or shall I wait for further testing of the code so that we can minimize any bugs? [1] https://github.com/ManZzup/identity-entitlement-endpoint Thank You, Best Regards Manujith On Tue, Jun 7, 2016 at 10:30 AM, Omindu Rathnaweera <omi...@wso2.com> wrote: > Adding a .gitignore to the repo will be the easiest way to keep the > unwanted files away from the repo. See [1]. > > [1] - > https://github.com/wso2/carbon-identity-framework/blob/master/.gitignore > > Regards, > Omindu > > On Tue, Jun 7, 2016 at 10:26 AM, Pushpalanka Jayawardhana <la...@wso2.com> > wrote: > >> Hi Manujith, >> >> The IDE specific files(.iml) or code can be removed from the repository. >> Once the code refactoring is done and code is cleaned please feel free to >> send the PR. Then we can easily comment on the code. >> >> Thanks, >> Pushpalanka >> >> >> On Tue, Jun 7, 2016 at 10:12 AM, Omindu Rathnaweera <omi...@wso2.com> >> wrote: >> >>> Hi Manujith, >>> >>> Better if you can clean up the unnecessary code and do some code >>> refactoring. We can do another round of testing once you fix the issues I >>> have mention. You can use the attached Idea Code Formatting Template [1]. >>> >>> To apply the template, follow the steps below. >>> >>> 1. In IDEA settings, goto Editor -> Code Style. >>> 2. Click 'Manage' then 'Save As...' an existing scheme with the name >>> 'wso2-codestyle' and Close the IDE. >>> 3. Goto ~/.IntelliJIdea16/config/codestyles directory and replace the >>> 'wso2-codestyle.xml' file with the attached one. >>> >>> [1] - >>> https://drive.google.com/file/d/0BzRDbfbIaYjCSzhGRUR1aGdlTXM/view?usp=sharing >>> >>> Regards, >>> Omindu. >>> >>> >>> On Mon, Jun 6, 2016 at 8:29 AM, Manujith Pallewatte < >>> manujith...@gmail.com> wrote: >>> >>>> Hi all, >>>> >>>> After a bit of refactoring I added the code to [1]. Please feel free to >>>> check the source and give your ideas to improve, specially on the service >>>> related code. All the service related code is available at [2] >>>> >>>> Also Omindu tested the initial war file and reported several issues >>>> with it, hoping to debug those within the week >>>> >>>> >>>> [1] https://github.com/ManZzup/identity-entitlement-endpoint >>>> [2] >>>> https://github.com/ManZzup/identity-entitlement-endpoint/blob/master/src/main/java/org/wso2/carbon/identity/entitlement/provider/resources/DecisionResource.java >>>> >>>> On Wed, Jun 1, 2016 at 10:21 AM, Pushpalanka Jayawardhana < >>>> la...@wso2.com> wrote: >>>> >>>>> Hi Manujith, >>>>> >>>>> Please share the code progress via Github, once you are satisfied with >>>>> refactoring. >>>>> Please fork [1] to your private repo, and at location [2], you may >>>>> have a new component named 'org.wso2.carbon.identity.entitlement.endpoint' >>>>> where the implementation can reside. >>>>> >>>>> [1] - https://github.com/wso2/carbon-identity-framework >>>>> [2] - >>>>> https://github.com/wso2/carbon-identity-framework/tree/master/components/entitlement >>>>> >>>>> Thanks, >>>>> Pushpalanka >>>>> >>>>> On Wed, Jun 1, 2016 at 10:00 AM, Manujith Pallewatte < >>>>> manujith...@gmail.com> wrote: >>>>> >>>>>> Hi all, >>>>>> >>>>>> So I have roughly finished up the following 5 services in REST >>>>>> getDecision >>>>>> getDecisionByAttibutes >>>>>> getBooleanDecision >>>>>> getEntitledAttributes >>>>>> getAllEntitlements >>>>>> >>>>>> The service is packed t
Re: [Dev] [IS] RESTful Fine Grained Authorization-as-a-Service (AZaaS)
Hi all, After a bit of refactoring I added the code to [1]. Please feel free to check the source and give your ideas to improve, specially on the service related code. All the service related code is available at [2] Also Omindu tested the initial war file and reported several issues with it, hoping to debug those within the week [1] https://github.com/ManZzup/identity-entitlement-endpoint [2] https://github.com/ManZzup/identity-entitlement-endpoint/blob/master/src/main/java/org/wso2/carbon/identity/entitlement/provider/resources/DecisionResource.java On Wed, Jun 1, 2016 at 10:21 AM, Pushpalanka Jayawardhana <la...@wso2.com> wrote: > Hi Manujith, > > Please share the code progress via Github, once you are satisfied with > refactoring. > Please fork [1] to your private repo, and at location [2], you may have a > new component named 'org.wso2.carbon.identity.entitlement.endpoint' where > the implementation can reside. > > [1] - https://github.com/wso2/carbon-identity-framework > [2] - > https://github.com/wso2/carbon-identity-framework/tree/master/components/entitlement > > Thanks, > Pushpalanka > > On Wed, Jun 1, 2016 at 10:00 AM, Manujith Pallewatte < > manujith...@gmail.com> wrote: > >> Hi all, >> >> So I have roughly finished up the following 5 services in REST >> getDecision >> getDecisionByAttibutes >> getBooleanDecision >> getEntitledAttributes >> getAllEntitlements >> >> The service is packed to a war file deployable to IS 5.2.0 >> It's still in primary testing, so once it's confirmed working it will be >> released to the community to get their ideas >> the URIs and methods should be adjusted with the community suggestions >> >> Hoping to release the war file in coming week as well as the code. The >> code have to be refracted first. >> >> Thank You >> >> On Mon, May 23, 2016 at 2:05 PM, Manujith Pallewatte < >> manujith...@gmail.com> wrote: >> >>> Hi all, >>> >>> To update on the progress so far, after having a chat with Pushpalanka, >>> I started with the project code. Basic setups are done. >>> Necessary entry points for the service was identified and now I'm >>> familiar with the process of deploying the REST service as a Web app to the >>> IS. >>> >>> Right now, the getDecision method is implemented in a RESTful manner, >>> using Apache cxf (following the guidelines of SCIM implementation as >>> suggested by Pushpalanka and Omindu). The implementation works, yet it's >>> only a test implementation. >>> >>> We are expecting to consult the community on the actual implementation >>> of the service, focusing on points like >>> 1) End point URLs >>> 2) Resource identification >>> 3) Service method definitions >>> >>> At the moment I'm struggling with implementations of some methods using >>> the current CXF version, hoping to resolve it ASAP. >>> >>> Thanks, >>> Manujith >>> >>> On Mon, May 16, 2016 at 11:18 AM, Pushpalanka Jayawardhana < >>> la...@wso2.com> wrote: >>> >>>> Hi Manujith, >>>> >>>> Good progress in getting familiar with the environment. >>>> So let's try to start with the scope of the project too. >>>> >>>> Since we are to work on implementing REST service, it is better to go >>>> through WSO2 guidelines for REST service implementation. Please find the >>>> white paper at[1] and the relevant discussion can be found at architecture >>>> mailing list under "REST API Guidelines". Then we can work on defining the >>>> API definition for the endpoint. >>>> >>>> You can also have a look at the existing WSO2 REST implementation to >>>> capture the followed patterns referring the SCIM[2] and OAuth endpoints[3]. >>>> >>>> >>>> [1] - http://wso2.com/whitepapers/wso2-rest-apis-design-guidelines/ >>>> [2] - >>>> https://github.com/wso2-extensions/identity-inbound-provisioning-scim/tree/master/components/org.wso2.carbon.identity.scim.provider >>>> [3] - >>>> https://github.com/wso2-extensions/identity-inbound-auth-oauth/tree/master/components/org.wso2.carbon.identity.oauth.endpoint >>>> >>>> Thanks, >>>> Pushpalanka >>>> >>>> On Wed, May 11, 2016 at 3:23 PM, Manujith Pallewatte < >>>> manujith...@gmail.com> wrote: >>>> >>>>> Hi Pushpalanka, >>>>> >>>>> I ma
Re: [Dev] [IS] RESTful Fine Grained Authorization-as-a-Service (AZaaS)
Hi all, So I have roughly finished up the following 5 services in REST getDecision getDecisionByAttibutes getBooleanDecision getEntitledAttributes getAllEntitlements The service is packed to a war file deployable to IS 5.2.0 It's still in primary testing, so once it's confirmed working it will be released to the community to get their ideas the URIs and methods should be adjusted with the community suggestions Hoping to release the war file in coming week as well as the code. The code have to be refracted first. Thank You On Mon, May 23, 2016 at 2:05 PM, Manujith Pallewatte <manujith...@gmail.com> wrote: > Hi all, > > To update on the progress so far, after having a chat with Pushpalanka, I > started with the project code. Basic setups are done. > Necessary entry points for the service was identified and now I'm familiar > with the process of deploying the REST service as a Web app to the IS. > > Right now, the getDecision method is implemented in a RESTful manner, > using Apache cxf (following the guidelines of SCIM implementation as > suggested by Pushpalanka and Omindu). The implementation works, yet it's > only a test implementation. > > We are expecting to consult the community on the actual implementation of > the service, focusing on points like > 1) End point URLs > 2) Resource identification > 3) Service method definitions > > At the moment I'm struggling with implementations of some methods using > the current CXF version, hoping to resolve it ASAP. > > Thanks, > Manujith > > On Mon, May 16, 2016 at 11:18 AM, Pushpalanka Jayawardhana <la...@wso2.com > > wrote: > >> Hi Manujith, >> >> Good progress in getting familiar with the environment. >> So let's try to start with the scope of the project too. >> >> Since we are to work on implementing REST service, it is better to go >> through WSO2 guidelines for REST service implementation. Please find the >> white paper at[1] and the relevant discussion can be found at architecture >> mailing list under "REST API Guidelines". Then we can work on defining the >> API definition for the endpoint. >> >> You can also have a look at the existing WSO2 REST implementation to >> capture the followed patterns referring the SCIM[2] and OAuth endpoints[3]. >> >> >> [1] - http://wso2.com/whitepapers/wso2-rest-apis-design-guidelines/ >> [2] - >> https://github.com/wso2-extensions/identity-inbound-provisioning-scim/tree/master/components/org.wso2.carbon.identity.scim.provider >> [3] - >> https://github.com/wso2-extensions/identity-inbound-auth-oauth/tree/master/components/org.wso2.carbon.identity.oauth.endpoint >> >> Thanks, >> Pushpalanka >> >> On Wed, May 11, 2016 at 3:23 PM, Manujith Pallewatte < >> manujith...@gmail.com> wrote: >> >>> Hi Pushpalanka, >>> >>> I managed to setup the development environment and build all the sources >>> (thanks to Omindu :)) >>> Then I made the PEP client using the entitlement stubs as you have >>> mentioned in a previous thread. It's working in an accepted state. But I >>> encountered some questions during the process, so I'm currently building a >>> doc with all the questions so I can document them and their answers for >>> future reference. >>> Other than that I'm trying to write different policies using XACML >>> >>> Also please let me know of any other steps i can follow to get familiar >>> with the components, specially the code since I'm only focusing on >>> Entitlement service right now >>> >>> Thank You >>> Manujith >>> -- >>> >>> >>> >>> [image: Manujith Pallewatte on about.me] >>> >>> Manujith Pallewatte >>> about.me/manzzup >>> <http://about.me/manzzup> >>> >> >> >> >> -- >> Pushpalanka. >> -- >> Pushpalanka Jayawardhana, B.Sc.Eng.(Hons). >> Senior Software Engineer, WSO2 Lanka (pvt) Ltd; wso2.com/ >> Mobile: +94779716248 >> Blog: pushpalankajaya.blogspot.com/ | LinkedIn: >> lk.linkedin.com/in/pushpalanka/ | Twitter: @pushpalanka >> >> > > > -- > > > > [image: Manujith Pallewatte on about.me] > > Manujith Pallewatte > about.me/manzzup > <http://about.me/manzzup> > -- [image: Manujith Pallewatte on about.me] Manujith Pallewatte about.me/manzzup <http://about.me/manzzup> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [IS] RESTful Fine Grained Authorization-as-a-Service (AZaaS)
Hi all, To update on the progress so far, after having a chat with Pushpalanka, I started with the project code. Basic setups are done. Necessary entry points for the service was identified and now I'm familiar with the process of deploying the REST service as a Web app to the IS. Right now, the getDecision method is implemented in a RESTful manner, using Apache cxf (following the guidelines of SCIM implementation as suggested by Pushpalanka and Omindu). The implementation works, yet it's only a test implementation. We are expecting to consult the community on the actual implementation of the service, focusing on points like 1) End point URLs 2) Resource identification 3) Service method definitions At the moment I'm struggling with implementations of some methods using the current CXF version, hoping to resolve it ASAP. Thanks, Manujith On Mon, May 16, 2016 at 11:18 AM, Pushpalanka Jayawardhana <la...@wso2.com> wrote: > Hi Manujith, > > Good progress in getting familiar with the environment. > So let's try to start with the scope of the project too. > > Since we are to work on implementing REST service, it is better to go > through WSO2 guidelines for REST service implementation. Please find the > white paper at[1] and the relevant discussion can be found at architecture > mailing list under "REST API Guidelines". Then we can work on defining the > API definition for the endpoint. > > You can also have a look at the existing WSO2 REST implementation to > capture the followed patterns referring the SCIM[2] and OAuth endpoints[3]. > > > [1] - http://wso2.com/whitepapers/wso2-rest-apis-design-guidelines/ > [2] - > https://github.com/wso2-extensions/identity-inbound-provisioning-scim/tree/master/components/org.wso2.carbon.identity.scim.provider > [3] - > https://github.com/wso2-extensions/identity-inbound-auth-oauth/tree/master/components/org.wso2.carbon.identity.oauth.endpoint > > Thanks, > Pushpalanka > > On Wed, May 11, 2016 at 3:23 PM, Manujith Pallewatte < > manujith...@gmail.com> wrote: > >> Hi Pushpalanka, >> >> I managed to setup the development environment and build all the sources >> (thanks to Omindu :)) >> Then I made the PEP client using the entitlement stubs as you have >> mentioned in a previous thread. It's working in an accepted state. But I >> encountered some questions during the process, so I'm currently building a >> doc with all the questions so I can document them and their answers for >> future reference. >> Other than that I'm trying to write different policies using XACML >> >> Also please let me know of any other steps i can follow to get familiar >> with the components, specially the code since I'm only focusing on >> Entitlement service right now >> >> Thank You >> Manujith >> -- >> >> >> >> [image: Manujith Pallewatte on about.me] >> >> Manujith Pallewatte >> about.me/manzzup >> <http://about.me/manzzup> >> > > > > -- > Pushpalanka. > -- > Pushpalanka Jayawardhana, B.Sc.Eng.(Hons). > Senior Software Engineer, WSO2 Lanka (pvt) Ltd; wso2.com/ > Mobile: +94779716248 > Blog: pushpalankajaya.blogspot.com/ | LinkedIn: > lk.linkedin.com/in/pushpalanka/ | Twitter: @pushpalanka > > -- [image: Manujith Pallewatte on about.me] Manujith Pallewatte about.me/manzzup <http://about.me/manzzup> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [IS] RESTful Fine Grained Authorization-as-a-Service (AZaaS)
Hi Pushpalanka, I managed to setup the development environment and build all the sources (thanks to Omindu :)) Then I made the PEP client using the entitlement stubs as you have mentioned in a previous thread. It's working in an accepted state. But I encountered some questions during the process, so I'm currently building a doc with all the questions so I can document them and their answers for future reference. Other than that I'm trying to write different policies using XACML Also please let me know of any other steps i can follow to get familiar with the components, specially the code since I'm only focusing on Entitlement service right now Thank You Manujith -- [image: Manujith Pallewatte on about.me] Manujith Pallewatte about.me/manzzup <http://about.me/manzzup> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Fwd: [IS] Missing requirement in building product-is from source
Hi Chamila, I tried with maven 3.3 also with maven 3.0.5 as mentioned in the requirements I build product-is only before in a windows environment, with no issues, but it didn't work in the current (ubuntu 16.04) environment >From the link above[1] i have all prerequisites other than svn, since I clone from git i believe svn is of no use [1]. https://docs.wso2.com/display/IS510/Installation+Prerequisites On Wed, Apr 27, 2016 at 9:06 PM, Chamila Wijayarathna <cham...@wso2.com> wrote: > [adding dev] > > identity-framework should build without any issues, what is the maven > version you are using? Can you check if you have all the requirement > mentioned at [1] for building the identity server from source code. Was > this building successfully previously? > > [1]. https://docs.wso2.com/display/IS510/Installation+Prerequisites > > -- Forwarded message -- > From: Manujith Pallewatte <manujith...@gmail.com> > Date: Wed, Apr 27, 2016 at 7:49 PM > Subject: Re: [IS] Missing requirement in building product-is from source > To: Chamila Wijayarathna <cham...@wso2.com> > > > Hi Chamila, > > Apparently identity framework didnt have the latest commits, I forked it > today and pulled but It must have missed some commits > Anyway I updated the local repo to all changes, but now identity framework > gives an error in building > > "[ERROR] Failed to execute goal > org.apache.felix:maven-scr-plugin:1.7.2:scr (generate-scr-scrdescriptor) on > project org.wso2.carbon.identity.application.authentication.framework: > Execution generate-scr-scrdescriptor of goal > org.apache.felix:maven-scr-plugin:1.7.2:scr failed: Comparison method > violates its general contract! -> [Help 1]" > > I google and found that this is a known bug of apache felix, but it didn't > provide and solid way to solve other than to change jdk version > I tried changing version with no luck, any ideas? > > Also found similar error in dev list > http://mail.wso2.org/mailarchive/dev/2015-June/049912.html > > Thank You > > On Wed, Apr 27, 2016 at 4:46 PM, Chamila Wijayarathna <cham...@wso2.com> > wrote: > >> Hi Manujith, >> >> It seems like your identity-framework or product-is is not upto date. >> >> Can you check what are the latest commits in both repos using git log and >> check if commits merged within last few days are there in your local repo? >> >> Thank You! >> >> On Wed, Apr 27, 2016 at 3:56 PM, Manujith Pallewatte < >> manujith...@gmail.com> wrote: >> >>> Hi all, >>> >>> I'm trying to setup the development environment to start working for >>> GSOC on the identity server, and I already downloaded and build the >>> carbon-identity-framework repo along with the extensions as mentioned in [1] >>> >>> Now I'm trying to build product-is from source as well, to make sure I >>> have all the dependencies before doing in changes to the source, but >>> running maven install in product is gives the following error >>> >>> "Missing requirement: Application Authentication Framework Server >>> Feature 5.0.9.SNAPSHOT >>> (org.wso2.carbon.identity.application.authentication.framework.server.feature.group >>> 5.0.9.SNAPSHOT) requires >>> 'org.wso2.carbon.tenant.mgt.common.server.feature.group [4.4.8,4.5.0)' but >>> it could not be found" >>> >>> I check the local maven repo and this package isnt available in it, so >>> why is maven not downloading this from the remote repository? >>> >>> Thank You >>> >>> >>> [1] https://gist.github.com/pulasthi7/3d365a3345371fd63f74 >>> >>> -- >>> >>> >>> >>> [image: Manujith Pallewatte on about.me] >>> >>> Manujith Pallewatte >>> about.me/manzzup >>> <http://about.me/manzzup> >>> >> >> >> >> -- >> *Chamila Dilshan Wijayarathna,* >> Software Engineer >> Mobile:(+94)788193620 >> WSO2 Inc., http://wso2.com/ >> > > > > -- > > > > [image: Manujith Pallewatte on about.me] > > Manujith Pallewatte > about.me/manzzup > <http://about.me/manzzup> > > > > -- > *Chamila Dilshan Wijayarathna,* > Software Engineer > Mobile:(+94)788193620 > WSO2 Inc., http://wso2.com/ > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- [image: Manujith Pallewatte on about.me] Manujith Pallewatte about.me/manzzup <http://about.me/manzzup> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [IS] Missing requirement in building product-is from source
Hi all, I'm trying to setup the development environment to start working for GSOC on the identity server, and I already downloaded and build the carbon-identity-framework repo along with the extensions as mentioned in [1] Now I'm trying to build product-is from source as well, to make sure I have all the dependencies before doing in changes to the source, but running maven install in product is gives the following error "Missing requirement: Application Authentication Framework Server Feature 5.0.9.SNAPSHOT (org.wso2.carbon.identity.application.authentication.framework.server.feature.group 5.0.9.SNAPSHOT) requires 'org.wso2.carbon.tenant.mgt.common.server.feature.group [4.4.8,4.5.0)' but it could not be found" I check the local maven repo and this package isnt available in it, so why is maven not downloading this from the remote repository? Thank You [1] https://gist.github.com/pulasthi7/3d365a3345371fd63f74 -- [image: Manujith Pallewatte on about.me] Manujith Pallewatte about.me/manzzup <http://about.me/manzzup> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Fwd: [GSoC 16'] Proposal 20: [IS] SCIM 2.0 Support to WSO2 Identity Server
Hi all, I added the final proposal to the gsoc site, thank you all for the support and guidance. On Fri, Mar 25, 2016 at 11:26 AM, Manujith Pallewatte <manujith...@gmail.com > wrote: > Hi Chamila, > > I added the draft to GSoC site and selected the share draft option as well > But didn't upload the FInal PDF still, since there's still 13 hours > remaining > > Thanks > > On Fri, Mar 25, 2016 at 11:23 AM, Chamila Wijayarathna <cham...@wso2.com> > wrote: > >> Hi Manujith, >> >> I strongly suggest you to submit your proposal to GSoC site with current >> progress. You can update it until the deadline. >> >> Thank You! >> >> On Fri, Mar 25, 2016 at 11:17 AM, Manujith Pallewatte < >> manujith...@gmail.com> wrote: >> >>> Hi all, >>> >>> I added the automated unit test and integration tests under the >>> implementation phase. Since I'm still in process of doing the PEP client >>> simulation, I couldn't enter it in the blog, so I didn't mention in it the >>> proposal. If I'm to find it before the deadline I will blog and insert it. >>> Thank you all again for the many support and guidance! >>> >>> On Thu, Mar 24, 2016 at 3:12 PM, Omindu Rathnaweera <omi...@wso2.com> >>> wrote: >>> >>>> Hi Manujith, >>>> >>>> It's better to include implementation of automation tests in your >>>> proposal. The automation tests include unit & integration tests and if >>>> needed, UI tests. Also you can start blogging about your findings so far >>>> and add them in your proposal. >>>> >>>> Regards, >>>> Omindu. >>>> >>>> On Thu, Mar 24, 2016 at 2:27 AM, Manujith Pallewatte < >>>> manujith...@gmail.com> wrote: >>>> >>>>> Hi all, >>>>> >>>>> Thank you very much for the comments, I revised and changed as much as >>>>> possible. >>>>> About the confusion by Entitlement Engine I wanted to refer to the >>>>> EntitlementEngine.java class in src since it has the main entry points to >>>>> the service >>>>> But it is really a confusing detail and i changed it to Identity >>>>> Server instead >>>>> Also i added a few illustrations to make some points clear >>>>> Please give me feedback on the revised proposal >>>>> >>>>> >>>>> https://docs.google.com/document/d/1dz8FcqUHargRM1q0UG0Ln4FHo_zHH-ENz6oc1hjeLYY/edit?usp=sharing >>>>> >>>>> Thankx alot again! >>>>> >>>>> On Wed, Mar 23, 2016 at 3:41 PM, Pushpalanka Jayawardhana < >>>>> la...@wso2.com> wrote: >>>>> >>>>>> Hi Manujith, >>>>>> >>>>>> Added the comments and suggestions. Please have a look and correct. >>>>>> Please also note that the entitlement engine we have in PDP component >>>>>> is the Balana engine and there is no seperate entitlelment engine within >>>>>> IS. >>>>>> IS provides XACML support on top of Balana engine, with other >>>>>> required functionality for PEP, PAP and PIP. >>>>>> >>>>>> Thanks, >>>>>> Pushpalanka >>>>>> >>>>>> On Wed, Mar 23, 2016 at 3:13 PM, Manujith Pallewatte < >>>>>> manujith...@gmail.com> wrote: >>>>>> >>>>>>> Hi all, >>>>>>> >>>>>>> Thankx alot for the input and I added them in the proposal so far >>>>>>> I have attached the proposal with the mail >>>>>>> Please review it and let me know points of improvement and any >>>>>>> additional details I'm missing in it >>>>>>> >>>>>>> Thank You >>>>>>> >>>>>>> On Wed, Mar 23, 2016 at 12:05 PM, Pushpalanka Jayawardhana < >>>>>>> la...@wso2.com> wrote: >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Pushpalanka. >>>>>>>> -- >>>>>>>> Pushpalanka Jayawardhana, B.Sc.Eng.(Hons). >>>>>>>> Senior Software Engineer, WSO2 Lanka (pvt) Ltd; wso2.com/ >>>>>>>> Mobile: +94779716248 >>>>>>>> Blog: pushpalankajaya.blogspot.com/ | LinkedIn: >>&
Re: [Dev] Fwd: [GSoC 16'] Proposal 20: [IS] SCIM 2.0 Support to WSO2 Identity Server
Hi Chamila, I added the draft to GSoC site and selected the share draft option as well But didn't upload the FInal PDF still, since there's still 13 hours remaining Thanks On Fri, Mar 25, 2016 at 11:23 AM, Chamila Wijayarathna <cham...@wso2.com> wrote: > Hi Manujith, > > I strongly suggest you to submit your proposal to GSoC site with current > progress. You can update it until the deadline. > > Thank You! > > On Fri, Mar 25, 2016 at 11:17 AM, Manujith Pallewatte < > manujith...@gmail.com> wrote: > >> Hi all, >> >> I added the automated unit test and integration tests under the >> implementation phase. Since I'm still in process of doing the PEP client >> simulation, I couldn't enter it in the blog, so I didn't mention in it the >> proposal. If I'm to find it before the deadline I will blog and insert it. >> Thank you all again for the many support and guidance! >> >> On Thu, Mar 24, 2016 at 3:12 PM, Omindu Rathnaweera <omi...@wso2.com> >> wrote: >> >>> Hi Manujith, >>> >>> It's better to include implementation of automation tests in your >>> proposal. The automation tests include unit & integration tests and if >>> needed, UI tests. Also you can start blogging about your findings so far >>> and add them in your proposal. >>> >>> Regards, >>> Omindu. >>> >>> On Thu, Mar 24, 2016 at 2:27 AM, Manujith Pallewatte < >>> manujith...@gmail.com> wrote: >>> >>>> Hi all, >>>> >>>> Thank you very much for the comments, I revised and changed as much as >>>> possible. >>>> About the confusion by Entitlement Engine I wanted to refer to the >>>> EntitlementEngine.java class in src since it has the main entry points to >>>> the service >>>> But it is really a confusing detail and i changed it to Identity Server >>>> instead >>>> Also i added a few illustrations to make some points clear >>>> Please give me feedback on the revised proposal >>>> >>>> >>>> https://docs.google.com/document/d/1dz8FcqUHargRM1q0UG0Ln4FHo_zHH-ENz6oc1hjeLYY/edit?usp=sharing >>>> >>>> Thankx alot again! >>>> >>>> On Wed, Mar 23, 2016 at 3:41 PM, Pushpalanka Jayawardhana < >>>> la...@wso2.com> wrote: >>>> >>>>> Hi Manujith, >>>>> >>>>> Added the comments and suggestions. Please have a look and correct. >>>>> Please also note that the entitlement engine we have in PDP component >>>>> is the Balana engine and there is no seperate entitlelment engine within >>>>> IS. >>>>> IS provides XACML support on top of Balana engine, with other required >>>>> functionality for PEP, PAP and PIP. >>>>> >>>>> Thanks, >>>>> Pushpalanka >>>>> >>>>> On Wed, Mar 23, 2016 at 3:13 PM, Manujith Pallewatte < >>>>> manujith...@gmail.com> wrote: >>>>> >>>>>> Hi all, >>>>>> >>>>>> Thankx alot for the input and I added them in the proposal so far >>>>>> I have attached the proposal with the mail >>>>>> Please review it and let me know points of improvement and any >>>>>> additional details I'm missing in it >>>>>> >>>>>> Thank You >>>>>> >>>>>> On Wed, Mar 23, 2016 at 12:05 PM, Pushpalanka Jayawardhana < >>>>>> la...@wso2.com> wrote: >>>>>> >>>>>>> >>>>>>> >>>>>>> Pushpalanka. >>>>>>> -- >>>>>>> Pushpalanka Jayawardhana, B.Sc.Eng.(Hons). >>>>>>> Senior Software Engineer, WSO2 Lanka (pvt) Ltd; wso2.com/ >>>>>>> Mobile: +94779716248 >>>>>>> Blog: pushpalankajaya.blogspot.com/ | LinkedIn: >>>>>>> lk.linkedin.com/in/pushpalanka/ | Twitter: @pushpalanka >>>>>>> >>>>>>> >>>>>>> On Wed, Mar 23, 2016 at 11:58 AM, Manujith Pallewatte < >>>>>>> manujith...@gmail.com> wrote: >>>>>>> >>>>>>>> Hi all, >>>>>>>> >>>>>>>> I will certainly start off with the client, would be a good >>>>>>>> starting point to observer the responses I think. >>>>>>>> Tha
Re: [Dev] Fwd: [GSoC 16'] Proposal 20: [IS] SCIM 2.0 Support to WSO2 Identity Server
Hi all, I added the automated unit test and integration tests under the implementation phase. Since I'm still in process of doing the PEP client simulation, I couldn't enter it in the blog, so I didn't mention in it the proposal. If I'm to find it before the deadline I will blog and insert it. Thank you all again for the many support and guidance! On Thu, Mar 24, 2016 at 3:12 PM, Omindu Rathnaweera <omi...@wso2.com> wrote: > Hi Manujith, > > It's better to include implementation of automation tests in your > proposal. The automation tests include unit & integration tests and if > needed, UI tests. Also you can start blogging about your findings so far > and add them in your proposal. > > Regards, > Omindu. > > On Thu, Mar 24, 2016 at 2:27 AM, Manujith Pallewatte < > manujith...@gmail.com> wrote: > >> Hi all, >> >> Thank you very much for the comments, I revised and changed as much as >> possible. >> About the confusion by Entitlement Engine I wanted to refer to the >> EntitlementEngine.java class in src since it has the main entry points to >> the service >> But it is really a confusing detail and i changed it to Identity Server >> instead >> Also i added a few illustrations to make some points clear >> Please give me feedback on the revised proposal >> >> >> https://docs.google.com/document/d/1dz8FcqUHargRM1q0UG0Ln4FHo_zHH-ENz6oc1hjeLYY/edit?usp=sharing >> >> Thankx alot again! >> >> On Wed, Mar 23, 2016 at 3:41 PM, Pushpalanka Jayawardhana <la...@wso2.com >> > wrote: >> >>> Hi Manujith, >>> >>> Added the comments and suggestions. Please have a look and correct. >>> Please also note that the entitlement engine we have in PDP component is >>> the Balana engine and there is no seperate entitlelment engine within IS. >>> IS provides XACML support on top of Balana engine, with other required >>> functionality for PEP, PAP and PIP. >>> >>> Thanks, >>> Pushpalanka >>> >>> On Wed, Mar 23, 2016 at 3:13 PM, Manujith Pallewatte < >>> manujith...@gmail.com> wrote: >>> >>>> Hi all, >>>> >>>> Thankx alot for the input and I added them in the proposal so far >>>> I have attached the proposal with the mail >>>> Please review it and let me know points of improvement and any >>>> additional details I'm missing in it >>>> >>>> Thank You >>>> >>>> On Wed, Mar 23, 2016 at 12:05 PM, Pushpalanka Jayawardhana < >>>> la...@wso2.com> wrote: >>>> >>>>> >>>>> >>>>> Pushpalanka. >>>>> -- >>>>> Pushpalanka Jayawardhana, B.Sc.Eng.(Hons). >>>>> Senior Software Engineer, WSO2 Lanka (pvt) Ltd; wso2.com/ >>>>> Mobile: +94779716248 >>>>> Blog: pushpalankajaya.blogspot.com/ | LinkedIn: >>>>> lk.linkedin.com/in/pushpalanka/ | Twitter: @pushpalanka >>>>> >>>>> >>>>> On Wed, Mar 23, 2016 at 11:58 AM, Manujith Pallewatte < >>>>> manujith...@gmail.com> wrote: >>>>> >>>>>> Hi all, >>>>>> >>>>>> I will certainly start off with the client, would be a good starting >>>>>> point to observer the responses I think. >>>>>> Thank to Omindu I was able to use SoapUI to simulate a request for >>>>>> now, I'm trying to develop on that as well. Should those things go in the >>>>>> proposal as well? >>>>>> I have a drafted a basic proposal which I will send asap for your >>>>>> feedback, then once I complete task 1, I can document it too >>>>>> >>>>> This is good progress. It is better to mention what you have tried >>>>> upto now regarding the project in brief, in the proposal. >>>>> >>>>>> >>>>>> Thank You >>>>>> >>>>>> On Wed, Mar 23, 2016 at 11:35 AM, Pushpalanka Jayawardhana < >>>>>> la...@wso2.com> wrote: >>>>>> >>>>>>> >>>>>>> >>>>>>> Pushpalanka. >>>>>>> -- >>>>>>> Pushpalanka Jayawardhana, B.Sc.Eng.(Hons). >>>>>>> Senior Software Engineer, WSO2 Lanka (pvt) Ltd; wso2.com/ >>>>>>> Mobile: +94779716248 >>>>>>> Blog: pushpalankajaya.blogspot.com/ | LinkedIn: >>>>>>&
Re: [Dev] Fwd: [GSoC 16'] Proposal 20: [IS] SCIM 2.0 Support to WSO2 Identity Server
Hi all, Thank you very much for the comments, I revised and changed as much as possible. About the confusion by Entitlement Engine I wanted to refer to the EntitlementEngine.java class in src since it has the main entry points to the service But it is really a confusing detail and i changed it to Identity Server instead Also i added a few illustrations to make some points clear Please give me feedback on the revised proposal https://docs.google.com/document/d/1dz8FcqUHargRM1q0UG0Ln4FHo_zHH-ENz6oc1hjeLYY/edit?usp=sharing Thankx alot again! On Wed, Mar 23, 2016 at 3:41 PM, Pushpalanka Jayawardhana <la...@wso2.com> wrote: > Hi Manujith, > > Added the comments and suggestions. Please have a look and correct. > Please also note that the entitlement engine we have in PDP component is > the Balana engine and there is no seperate entitlelment engine within IS. > IS provides XACML support on top of Balana engine, with other required > functionality for PEP, PAP and PIP. > > Thanks, > Pushpalanka > > On Wed, Mar 23, 2016 at 3:13 PM, Manujith Pallewatte < > manujith...@gmail.com> wrote: > >> Hi all, >> >> Thankx alot for the input and I added them in the proposal so far >> I have attached the proposal with the mail >> Please review it and let me know points of improvement and any additional >> details I'm missing in it >> >> Thank You >> >> On Wed, Mar 23, 2016 at 12:05 PM, Pushpalanka Jayawardhana < >> la...@wso2.com> wrote: >> >>> >>> >>> Pushpalanka. >>> -- >>> Pushpalanka Jayawardhana, B.Sc.Eng.(Hons). >>> Senior Software Engineer, WSO2 Lanka (pvt) Ltd; wso2.com/ >>> Mobile: +94779716248 >>> Blog: pushpalankajaya.blogspot.com/ | LinkedIn: >>> lk.linkedin.com/in/pushpalanka/ | Twitter: @pushpalanka >>> >>> >>> On Wed, Mar 23, 2016 at 11:58 AM, Manujith Pallewatte < >>> manujith...@gmail.com> wrote: >>> >>>> Hi all, >>>> >>>> I will certainly start off with the client, would be a good starting >>>> point to observer the responses I think. >>>> Thank to Omindu I was able to use SoapUI to simulate a request for now, >>>> I'm trying to develop on that as well. Should those things go in the >>>> proposal as well? >>>> I have a drafted a basic proposal which I will send asap for your >>>> feedback, then once I complete task 1, I can document it too >>>> >>> This is good progress. It is better to mention what you have tried upto >>> now regarding the project in brief, in the proposal. >>> >>>> >>>> Thank You >>>> >>>> On Wed, Mar 23, 2016 at 11:35 AM, Pushpalanka Jayawardhana < >>>> la...@wso2.com> wrote: >>>> >>>>> >>>>> >>>>> Pushpalanka. >>>>> -- >>>>> Pushpalanka Jayawardhana, B.Sc.Eng.(Hons). >>>>> Senior Software Engineer, WSO2 Lanka (pvt) Ltd; wso2.com/ >>>>> Mobile: +94779716248 >>>>> Blog: pushpalankajaya.blogspot.com/ | LinkedIn: >>>>> lk.linkedin.com/in/pushpalanka/ | Twitter: @pushpalanka >>>>> >>>>> >>>>> On Wed, Mar 23, 2016 at 2:05 AM, Manujith Pallewatte < >>>>> manujith...@gmail.com> wrote: >>>>> >>>>>> Hi Pushpalanka, >>>>>> >>>>>> Sorry for spamming the inbox like this, but since I'm already behind >>>>>> the schedule I have to get things resolved as fast as possible. Please >>>>>> don't mind it. >>>>>> One more thing as I finally got to the conclusion, the objective is >>>>>> to implement RESTful service to the PDP of IS so that any PEP can access >>>>>> them >>>>>> in a RESTful manner? In other words the REST service should be >>>>>> implemented to facilitate the information exchange between the PEP and >>>>>> PDP >>>>>> Is that correct? please correct me if i'm wrong >>>>>> >>>>> >>>>> >>>>> >>>>>> Thanks alot >>>>>> >>>>>> On Wed, Mar 23, 2016 at 1:39 AM, Manujith Pallewatte < >>>>>> manujith...@gmail.com> wrote: >>>>>> >>>>>>> Hi Pushpalanka, >>>>>>> >>>>>>> I tried examining the PDP and PAP of IS to get an idea of how things >>>>>>>
Re: [Dev] Fwd: [GSoC 16'] Proposal 20: [IS] SCIM 2.0 Support to WSO2 Identity Server
Hi all, Thankx alot for the input and I added them in the proposal so far I have attached the proposal with the mail Please review it and let me know points of improvement and any additional details I'm missing in it Thank You On Wed, Mar 23, 2016 at 12:05 PM, Pushpalanka Jayawardhana <la...@wso2.com> wrote: > > > Pushpalanka. > -- > Pushpalanka Jayawardhana, B.Sc.Eng.(Hons). > Senior Software Engineer, WSO2 Lanka (pvt) Ltd; wso2.com/ > Mobile: +94779716248 > Blog: pushpalankajaya.blogspot.com/ | LinkedIn: > lk.linkedin.com/in/pushpalanka/ | Twitter: @pushpalanka > > > On Wed, Mar 23, 2016 at 11:58 AM, Manujith Pallewatte < > manujith...@gmail.com> wrote: > >> Hi all, >> >> I will certainly start off with the client, would be a good starting >> point to observer the responses I think. >> Thank to Omindu I was able to use SoapUI to simulate a request for now, >> I'm trying to develop on that as well. Should those things go in the >> proposal as well? >> I have a drafted a basic proposal which I will send asap for your >> feedback, then once I complete task 1, I can document it too >> > This is good progress. It is better to mention what you have tried upto > now regarding the project in brief, in the proposal. > >> >> Thank You >> >> On Wed, Mar 23, 2016 at 11:35 AM, Pushpalanka Jayawardhana < >> la...@wso2.com> wrote: >> >>> >>> >>> Pushpalanka. >>> -- >>> Pushpalanka Jayawardhana, B.Sc.Eng.(Hons). >>> Senior Software Engineer, WSO2 Lanka (pvt) Ltd; wso2.com/ >>> Mobile: +94779716248 >>> Blog: pushpalankajaya.blogspot.com/ | LinkedIn: >>> lk.linkedin.com/in/pushpalanka/ | Twitter: @pushpalanka >>> >>> >>> On Wed, Mar 23, 2016 at 2:05 AM, Manujith Pallewatte < >>> manujith...@gmail.com> wrote: >>> >>>> Hi Pushpalanka, >>>> >>>> Sorry for spamming the inbox like this, but since I'm already behind >>>> the schedule I have to get things resolved as fast as possible. Please >>>> don't mind it. >>>> One more thing as I finally got to the conclusion, the objective is to >>>> implement RESTful service to the PDP of IS so that any PEP can access them >>>> in a RESTful manner? In other words the REST service should be >>>> implemented to facilitate the information exchange between the PEP and PDP >>>> Is that correct? please correct me if i'm wrong >>>> >>> >>> >>> >>>> Thanks alot >>>> >>>> On Wed, Mar 23, 2016 at 1:39 AM, Manujith Pallewatte < >>>> manujith...@gmail.com> wrote: >>>> >>>>> Hi Pushpalanka, >>>>> >>>>> I tried examining the PDP and PAP of IS to get an idea of how things >>>>> work and i followed the blog article [ >>>>> http://pushpalankajaya.blogspot.com/2013/06/working-with-xacml-30-policies-for-fine.html]. >>>>> I tested out few policies and all seems fine. Now I want to test the >>>>> policies using a PEP >>>>> Is there any way to simulate a authorization request? (may be using >>>>> curl as we use to test RESP APIs) >>>>> If there's any such way, where should I point the requests at? >>>>> ex: I added a policy for the resource url >>>>> http://localhost/services/secret >>>>> and the IS server is hosted at http://localhost:9443/ >>>>> now i want to do a authorized requests to the 1st mentioned service >>>>> through the IS server, i sense i'm missing a piece here. Please help me to >>>>> clarify this point >>>>> >>>> >>> Hi Manujith, >>> >>> There are no cURL commands available as we do not have REST >>> implementation as of now. >>> In order to get familiar with the code base and development environment >>> and to try out the scenario you suggested follow the below steps. >>> >>> 1 - Try to write a Java client for EntitlementService (SOAP service) [1] >>> >>> Please find the relevant service at [1]. This is the service that needs >>> to be cosumed in order to get the XACML policy decision from PDP for a >>> given XACML request. >>> >>> Specific method to call is "public String getDecision(String request) >>> throws EntitlementException " giving the XACML request as a String. The >>> relevant stub classes can be found at [2] that can be used at client side. &g
Re: [Dev] Fwd: [GSoC 16'] Proposal 20: [IS] SCIM 2.0 Support to WSO2 Identity Server
Hi all, Also since REST has no restriction on the media type it should use, is it okay to have a JSON implementation as well? Should it be strictly XML? On Wed, Mar 23, 2016 at 11:58 AM, Manujith Pallewatte <manujith...@gmail.com > wrote: > Hi all, > > I will certainly start off with the client, would be a good starting point > to observer the responses I think. > Thank to Omindu I was able to use SoapUI to simulate a request for now, > I'm trying to develop on that as well. Should those things go in the > proposal as well? > I have a drafted a basic proposal which I will send asap for your > feedback, then once I complete task 1, I can document it too > > Thank You > > On Wed, Mar 23, 2016 at 11:35 AM, Pushpalanka Jayawardhana <la...@wso2.com > > wrote: > >> >> >> Pushpalanka. >> -- >> Pushpalanka Jayawardhana, B.Sc.Eng.(Hons). >> Senior Software Engineer, WSO2 Lanka (pvt) Ltd; wso2.com/ >> Mobile: +94779716248 >> Blog: pushpalankajaya.blogspot.com/ | LinkedIn: >> lk.linkedin.com/in/pushpalanka/ | Twitter: @pushpalanka >> >> >> On Wed, Mar 23, 2016 at 2:05 AM, Manujith Pallewatte < >> manujith...@gmail.com> wrote: >> >>> Hi Pushpalanka, >>> >>> Sorry for spamming the inbox like this, but since I'm already behind the >>> schedule I have to get things resolved as fast as possible. Please don't >>> mind it. >>> One more thing as I finally got to the conclusion, the objective is to >>> implement RESTful service to the PDP of IS so that any PEP can access them >>> in a RESTful manner? In other words the REST service should be >>> implemented to facilitate the information exchange between the PEP and PDP >>> Is that correct? please correct me if i'm wrong >>> >> >> >> >>> Thanks alot >>> >>> On Wed, Mar 23, 2016 at 1:39 AM, Manujith Pallewatte < >>> manujith...@gmail.com> wrote: >>> >>>> Hi Pushpalanka, >>>> >>>> I tried examining the PDP and PAP of IS to get an idea of how things >>>> work and i followed the blog article [ >>>> http://pushpalankajaya.blogspot.com/2013/06/working-with-xacml-30-policies-for-fine.html]. >>>> I tested out few policies and all seems fine. Now I want to test the >>>> policies using a PEP >>>> Is there any way to simulate a authorization request? (may be using >>>> curl as we use to test RESP APIs) >>>> If there's any such way, where should I point the requests at? >>>> ex: I added a policy for the resource url >>>> http://localhost/services/secret >>>> and the IS server is hosted at http://localhost:9443/ >>>> now i want to do a authorized requests to the 1st mentioned service >>>> through the IS server, i sense i'm missing a piece here. Please help me to >>>> clarify this point >>>> >>> >> Hi Manujith, >> >> There are no cURL commands available as we do not have REST >> implementation as of now. >> In order to get familiar with the code base and development environment >> and to try out the scenario you suggested follow the below steps. >> >> 1 - Try to write a Java client for EntitlementService (SOAP service) [1] >> >> Please find the relevant service at [1]. This is the service that needs >> to be cosumed in order to get the XACML policy decision from PDP for a >> given XACML request. >> >> Specific method to call is "public String getDecision(String request) >> throws EntitlementException " giving the XACML request as a String. The >> relevant stub classes can be found at [2] that can be used at client side. >> Try to get client code written for this which can be placed in PEP when >> required. You can further publish a blogpost with this client code which >> can strengthen your proposal further. >> >> 2 - In production scenarioes usually ESB acts as the PEP creating the >> XACML request and calling the PDP via code similar to client code you would >> develop in the above point. >> >> The article at [3], describes this use case, but it has older content. >> You can try out same things with latest product versions. If you encounter >> any issues get back to us. We will try to find a solution. >> >> >> I think you would be in a good position to start with the proposal once >> the first point is done as 2nd is a extended version of that. >> Do get back with any problems you face. We will try our best to get back >> as soon as possible. >> >>
Re: [Dev] Fwd: [GSoC 16'] Proposal 20: [IS] SCIM 2.0 Support to WSO2 Identity Server
Hi all, I will certainly start off with the client, would be a good starting point to observer the responses I think. Thank to Omindu I was able to use SoapUI to simulate a request for now, I'm trying to develop on that as well. Should those things go in the proposal as well? I have a drafted a basic proposal which I will send asap for your feedback, then once I complete task 1, I can document it too Thank You On Wed, Mar 23, 2016 at 11:35 AM, Pushpalanka Jayawardhana <la...@wso2.com> wrote: > > > Pushpalanka. > -- > Pushpalanka Jayawardhana, B.Sc.Eng.(Hons). > Senior Software Engineer, WSO2 Lanka (pvt) Ltd; wso2.com/ > Mobile: +94779716248 > Blog: pushpalankajaya.blogspot.com/ | LinkedIn: > lk.linkedin.com/in/pushpalanka/ | Twitter: @pushpalanka > > > On Wed, Mar 23, 2016 at 2:05 AM, Manujith Pallewatte < > manujith...@gmail.com> wrote: > >> Hi Pushpalanka, >> >> Sorry for spamming the inbox like this, but since I'm already behind the >> schedule I have to get things resolved as fast as possible. Please don't >> mind it. >> One more thing as I finally got to the conclusion, the objective is to >> implement RESTful service to the PDP of IS so that any PEP can access them >> in a RESTful manner? In other words the REST service should be >> implemented to facilitate the information exchange between the PEP and PDP >> Is that correct? please correct me if i'm wrong >> > > > >> Thanks alot >> >> On Wed, Mar 23, 2016 at 1:39 AM, Manujith Pallewatte < >> manujith...@gmail.com> wrote: >> >>> Hi Pushpalanka, >>> >>> I tried examining the PDP and PAP of IS to get an idea of how things >>> work and i followed the blog article [ >>> http://pushpalankajaya.blogspot.com/2013/06/working-with-xacml-30-policies-for-fine.html]. >>> I tested out few policies and all seems fine. Now I want to test the >>> policies using a PEP >>> Is there any way to simulate a authorization request? (may be using curl >>> as we use to test RESP APIs) >>> If there's any such way, where should I point the requests at? >>> ex: I added a policy for the resource url >>> http://localhost/services/secret >>> and the IS server is hosted at http://localhost:9443/ >>> now i want to do a authorized requests to the 1st mentioned service >>> through the IS server, i sense i'm missing a piece here. Please help me to >>> clarify this point >>> >> > Hi Manujith, > > There are no cURL commands available as we do not have REST implementation > as of now. > In order to get familiar with the code base and development environment > and to try out the scenario you suggested follow the below steps. > > 1 - Try to write a Java client for EntitlementService (SOAP service) [1] > > Please find the relevant service at [1]. This is the service that needs to > be cosumed in order to get the XACML policy decision from PDP for a given > XACML request. > > Specific method to call is "public String getDecision(String request) > throws EntitlementException " giving the XACML request as a String. The > relevant stub classes can be found at [2] that can be used at client side. > Try to get client code written for this which can be placed in PEP when > required. You can further publish a blogpost with this client code which > can strengthen your proposal further. > > 2 - In production scenarioes usually ESB acts as the PEP creating the > XACML request and calling the PDP via code similar to client code you would > develop in the above point. > > The article at [3], describes this use case, but it has older content. You > can try out same things with latest product versions. If you encounter any > issues get back to us. We will try to find a solution. > > > I think you would be in a good position to start with the proposal once > the first point is done as 2nd is a extended version of that. > Do get back with any problems you face. We will try our best to get back > as soon as possible. > > > [1] - > https://github.com/wso2/identity-framework/blob/master/components/entitlement/org.wso2.carbon.identity.entitlement/src/main/java/org/wso2/carbon/identity/entitlement/EntitlementService.java > [2] - > https://github.com/wso2/identity-framework/tree/master/service-stubs/identity/org.wso2.carbon.identity.entitlement.stub > [3] - > http://wso2.com/library/articles/2010/10/using-xacml-fine-grained-authorization-wso2-platform/ > [4] - > http://wso2.com/library/tutorials/2012/12/providing-xacml-fine-grained-authorization-webapps/ > > Thanks, > Pushpalanka > >> >>> Thank You >>> >
Re: [Dev] Fwd: [GSoC 16'] Proposal 20: [IS] SCIM 2.0 Support to WSO2 Identity Server
Hi Pushpalanka, Sorry for spamming the inbox like this, but since I'm already behind the schedule I have to get things resolved as fast as possible. Please don't mind it. One more thing as I finally got to the conclusion, the objective is to implement RESTful service to the PDP of IS so that any PEP can access them in a RESTful manner? In other words the REST service should be implemented to facilitate the information exchange between the PEP and PDP Is that correct? please correct me if i'm wrong Thanks alot On Wed, Mar 23, 2016 at 1:39 AM, Manujith Pallewatte <manujith...@gmail.com> wrote: > Hi Pushpalanka, > > I tried examining the PDP and PAP of IS to get an idea of how things work > and i followed the blog article [ > http://pushpalankajaya.blogspot.com/2013/06/working-with-xacml-30-policies-for-fine.html]. > I tested out few policies and all seems fine. Now I want to test the > policies using a PEP > Is there any way to simulate a authorization request? (may be using curl > as we use to test RESP APIs) > If there's any such way, where should I point the requests at? > ex: I added a policy for the resource url http://localhost/services/secret > and the IS server is hosted at http://localhost:9443/ > now i want to do a authorized requests to the 1st mentioned service > through the IS server, i sense i'm missing a piece here. Please help me to > clarify this point > > Thank You > > > On Tue, Mar 22, 2016 at 10:47 PM, Manujith Pallewatte < > manujith...@gmail.com> wrote: > >> Hi Pushpalanka, >> >> Thank you for the resources, I will for sure start working on the >> proposal. I was trying to get the basic implementation details straight >> before jumping into the proposal >> so I could include a better plan in the proposal. But it seems with the >> time constraints I would have to speed it up. Trying my best to deliver the >> proposal by >> tomorrow. >> >> Thank you >> >> On Tue, Mar 22, 2016 at 10:32 PM, Pushpalanka Jayawardhana < >> la...@wso2.com> wrote: >> >>> Hi Manujith, >>> >>> If you haven't already try go through instructions provided at Dev list >>> under the thread "GSoC project proposal questions" for this proposal as >>> well. >>> >>> Hope you are getting up with the pace as the proposal deadline is >>> falling on 25th March(this Friday). While you try get familiar with the >>> development procedure and other resources, please try to go ahead with >>> drafting the proposal as well. This will allow us to give some early feed >>> back and time for you to adjust. Following resources might help you. >>> >>> [1] - >>> http://cdwijayarathna.blogspot.com/2016/02/how-to-get-proposal-ready-for-gsoc.html. >>> (Later part starting from "Now you need to start work, you may have " >>> will guide you) >>> [2] - Sample proposal - http://www.slideshare.net/Pushpalanka/gsoc-2012 >>> <http://www.slideshare.net/Pushpalanka/gsoc-2012> >>> >>> Thanks, >>> Pushpalanka. >>> -- >>> Pushpalanka Jayawardhana, B.Sc.Eng.(Hons). >>> Senior Software Engineer, WSO2 Lanka (pvt) Ltd; wso2.com/ >>> Mobile: +94779716248 >>> Blog: pushpalankajaya.blogspot.com/ | LinkedIn: >>> lk.linkedin.com/in/pushpalanka/ | Twitter: @pushpalanka >>> >>> >>> On Tue, Mar 22, 2016 at 8:57 PM, Manujith Pallewatte < >>> manujith...@gmail.com> wrote: >>> >>>> Hi Chamila, >>>> >>>> Thank a bunch, that cleared a lot of doubts i was having >>>> I would try with the patch9000 method so that i dont have to build the >>>> product-is every time >>>> And then try the other method as well >>>> >>>> Thankx again! >>>> >>>> >>>> On Tue, Mar 22, 2016 at 8:40 PM, Chamila Wijayarathna <cham...@wso2.com >>>> > wrote: >>>> >>>>> Hi Manujith, >>>>> >>>>> identity-framework [1] contains the code base of the features of >>>>> Identity Server, and product-is [2] contains the code which install >>>>> features at identity-framework to Identity Server. Component specific code >>>>> is available at identity-framework repo, because some of these features >>>>> are >>>>> not only used in Identity Server, but in some other carbon based products >>>>> as well. So you need to work with the code at identity-framework mainly. >>>>> >>>>> But for building the Ide
Re: [Dev] Fwd: [GSoC 16'] Proposal 20: [IS] SCIM 2.0 Support to WSO2 Identity Server
Hi Pushpalanka, I tried examining the PDP and PAP of IS to get an idea of how things work and i followed the blog article [ http://pushpalankajaya.blogspot.com/2013/06/working-with-xacml-30-policies-for-fine.html]. I tested out few policies and all seems fine. Now I want to test the policies using a PEP Is there any way to simulate a authorization request? (may be using curl as we use to test RESP APIs) If there's any such way, where should I point the requests at? ex: I added a policy for the resource url http://localhost/services/secret and the IS server is hosted at http://localhost:9443/ now i want to do a authorized requests to the 1st mentioned service through the IS server, i sense i'm missing a piece here. Please help me to clarify this point Thank You On Tue, Mar 22, 2016 at 10:47 PM, Manujith Pallewatte <manujith...@gmail.com > wrote: > Hi Pushpalanka, > > Thank you for the resources, I will for sure start working on the > proposal. I was trying to get the basic implementation details straight > before jumping into the proposal > so I could include a better plan in the proposal. But it seems with the > time constraints I would have to speed it up. Trying my best to deliver the > proposal by > tomorrow. > > Thank you > > On Tue, Mar 22, 2016 at 10:32 PM, Pushpalanka Jayawardhana <la...@wso2.com > > wrote: > >> Hi Manujith, >> >> If you haven't already try go through instructions provided at Dev list >> under the thread "GSoC project proposal questions" for this proposal as >> well. >> >> Hope you are getting up with the pace as the proposal deadline is falling >> on 25th March(this Friday). While you try get familiar with the development >> procedure and other resources, please try to go ahead with drafting the >> proposal as well. This will allow us to give some early feed back and time >> for you to adjust. Following resources might help you. >> >> [1] - >> http://cdwijayarathna.blogspot.com/2016/02/how-to-get-proposal-ready-for-gsoc.html. >> (Later part starting from "Now you need to start work, you may have " >> will guide you) >> [2] - Sample proposal - http://www.slideshare.net/Pushpalanka/gsoc-2012 >> <http://www.slideshare.net/Pushpalanka/gsoc-2012> >> >> Thanks, >> Pushpalanka. >> -- >> Pushpalanka Jayawardhana, B.Sc.Eng.(Hons). >> Senior Software Engineer, WSO2 Lanka (pvt) Ltd; wso2.com/ >> Mobile: +94779716248 >> Blog: pushpalankajaya.blogspot.com/ | LinkedIn: >> lk.linkedin.com/in/pushpalanka/ | Twitter: @pushpalanka >> >> >> On Tue, Mar 22, 2016 at 8:57 PM, Manujith Pallewatte < >> manujith...@gmail.com> wrote: >> >>> Hi Chamila, >>> >>> Thank a bunch, that cleared a lot of doubts i was having >>> I would try with the patch9000 method so that i dont have to build the >>> product-is every time >>> And then try the other method as well >>> >>> Thankx again! >>> >>> >>> On Tue, Mar 22, 2016 at 8:40 PM, Chamila Wijayarathna <cham...@wso2.com> >>> wrote: >>> >>>> Hi Manujith, >>>> >>>> identity-framework [1] contains the code base of the features of >>>> Identity Server, and product-is [2] contains the code which install >>>> features at identity-framework to Identity Server. Component specific code >>>> is available at identity-framework repo, because some of these features are >>>> not only used in Identity Server, but in some other carbon based products >>>> as well. So you need to work with the code at identity-framework mainly. >>>> >>>> But for building the Identity Server using source, first you need to >>>> run identity-framework, then build identity-extensions [3] which get packed >>>> into Identity server (You can find this list at [4], you can use scripts at >>>> there to clone and build those extensions). Then build product-is. When you >>>> are building identity-framework and extensions, maven save those artifacts >>>> in your M2_HOME and when you are building product-is, it use these >>>> artifacts. If you only build product-is, since there are no artifacts in >>>> M2_HOME, it will download artifacts available online, so if you have done >>>> any changes they will not appear in Identity Server pack you build. >>>> >>>> Additionally, if you are changing only entitlement component in >>>> identity server, without following above mentioned process, you can just >>>> build a pack by building product-is, then bu
Re: [Dev] Fwd: [GSoC 16'] Proposal 20: [IS] SCIM 2.0 Support to WSO2 Identity Server
Hi Pushpalanka, Thank you for the resources, I will for sure start working on the proposal. I was trying to get the basic implementation details straight before jumping into the proposal so I could include a better plan in the proposal. But it seems with the time constraints I would have to speed it up. Trying my best to deliver the proposal by tomorrow. Thank you On Tue, Mar 22, 2016 at 10:32 PM, Pushpalanka Jayawardhana <la...@wso2.com> wrote: > Hi Manujith, > > If you haven't already try go through instructions provided at Dev list > under the thread "GSoC project proposal questions" for this proposal as > well. > > Hope you are getting up with the pace as the proposal deadline is falling > on 25th March(this Friday). While you try get familiar with the development > procedure and other resources, please try to go ahead with drafting the > proposal as well. This will allow us to give some early feed back and time > for you to adjust. Following resources might help you. > > [1] - > http://cdwijayarathna.blogspot.com/2016/02/how-to-get-proposal-ready-for-gsoc.html. > (Later part starting from "Now you need to start work, you may have " > will guide you) > [2] - Sample proposal - http://www.slideshare.net/Pushpalanka/gsoc-2012 > <http://www.slideshare.net/Pushpalanka/gsoc-2012> > > Thanks, > Pushpalanka. > -- > Pushpalanka Jayawardhana, B.Sc.Eng.(Hons). > Senior Software Engineer, WSO2 Lanka (pvt) Ltd; wso2.com/ > Mobile: +94779716248 > Blog: pushpalankajaya.blogspot.com/ | LinkedIn: > lk.linkedin.com/in/pushpalanka/ | Twitter: @pushpalanka > > > On Tue, Mar 22, 2016 at 8:57 PM, Manujith Pallewatte < > manujith...@gmail.com> wrote: > >> Hi Chamila, >> >> Thank a bunch, that cleared a lot of doubts i was having >> I would try with the patch9000 method so that i dont have to build the >> product-is every time >> And then try the other method as well >> >> Thankx again! >> >> >> On Tue, Mar 22, 2016 at 8:40 PM, Chamila Wijayarathna <cham...@wso2.com> >> wrote: >> >>> Hi Manujith, >>> >>> identity-framework [1] contains the code base of the features of >>> Identity Server, and product-is [2] contains the code which install >>> features at identity-framework to Identity Server. Component specific code >>> is available at identity-framework repo, because some of these features are >>> not only used in Identity Server, but in some other carbon based products >>> as well. So you need to work with the code at identity-framework mainly. >>> >>> But for building the Identity Server using source, first you need to run >>> identity-framework, then build identity-extensions [3] which get packed >>> into Identity server (You can find this list at [4], you can use scripts at >>> there to clone and build those extensions). Then build product-is. When you >>> are building identity-framework and extensions, maven save those artifacts >>> in your M2_HOME and when you are building product-is, it use these >>> artifacts. If you only build product-is, since there are no artifacts in >>> M2_HOME, it will download artifacts available online, so if you have done >>> any changes they will not appear in Identity Server pack you build. >>> >>> Additionally, if you are changing only entitlement component in identity >>> server, without following above mentioned process, you can just build a >>> pack by building product-is, then build the component you change (eg: >>> components/entitlement/org.wso2.carbon.identity.entitlement) and copy the >>> jar file build at target folder (eg: >>> components/entitlement/org.wso2.carbon.identity.entitlement) into >> Server Home>/repository/components/patches/patch9000 (You'll have to create >>> patch9000 folder ). In this way also you can test any changes you are doing >>> to code. >>> >>> This may be bit complex task, try it and if you find anything difficult, >>> please put a mail here. >>> >>> [1]. https://github.com/wso2/identity-framework >>> [2]. https://github.com/wso2/product-is >>> [3]. https://github.com/wso2-extensions >>> [4]. https://gist.github.com/pulasthi7/3d365a3345371fd63f74 >>> >>> Cheers! >>> >>> On Tue, Mar 22, 2016 at 8:09 PM, Manujith Pallewatte < >>> manujith...@gmail.com> wrote: >>> >>>> Hi Omindu, >>>> >>>> Thank alot, I will look into those. >>>> also should I be working on the >>>> https://github.com/wso2/id
Re: [Dev] Fwd: [GSoC 16'] Proposal 20: [IS] SCIM 2.0 Support to WSO2 Identity Server
Hi Chamila, Thank a bunch, that cleared a lot of doubts i was having I would try with the patch9000 method so that i dont have to build the product-is every time And then try the other method as well Thankx again! On Tue, Mar 22, 2016 at 8:40 PM, Chamila Wijayarathna <cham...@wso2.com> wrote: > Hi Manujith, > > identity-framework [1] contains the code base of the features of Identity > Server, and product-is [2] contains the code which install features at > identity-framework to Identity Server. Component specific code is available > at identity-framework repo, because some of these features are not only > used in Identity Server, but in some other carbon based products as well. > So you need to work with the code at identity-framework mainly. > > But for building the Identity Server using source, first you need to run > identity-framework, then build identity-extensions [3] which get packed > into Identity server (You can find this list at [4], you can use scripts at > there to clone and build those extensions). Then build product-is. When you > are building identity-framework and extensions, maven save those artifacts > in your M2_HOME and when you are building product-is, it use these > artifacts. If you only build product-is, since there are no artifacts in > M2_HOME, it will download artifacts available online, so if you have done > any changes they will not appear in Identity Server pack you build. > > Additionally, if you are changing only entitlement component in identity > server, without following above mentioned process, you can just build a > pack by building product-is, then build the component you change (eg: > components/entitlement/org.wso2.carbon.identity.entitlement) and copy the > jar file build at target folder (eg: > components/entitlement/org.wso2.carbon.identity.entitlement) into Server Home>/repository/components/patches/patch9000 (You'll have to create > patch9000 folder ). In this way also you can test any changes you are doing > to code. > > This may be bit complex task, try it and if you find anything difficult, > please put a mail here. > > [1]. https://github.com/wso2/identity-framework > [2]. https://github.com/wso2/product-is > [3]. https://github.com/wso2-extensions > [4]. https://gist.github.com/pulasthi7/3d365a3345371fd63f74 > > Cheers! > > On Tue, Mar 22, 2016 at 8:09 PM, Manujith Pallewatte < > manujith...@gmail.com> wrote: > >> Hi Omindu, >> >> Thank alot, I will look into those. >> also should I be working on the >> https://github.com/wso2/identity-framework codebase or >> https://github.com/wso2/product-is codebase >> i was under the impression that the latter is what I should focus on >> >> >> >> >> >> On Tue, Mar 22, 2016 at 7:55 PM, Omindu Rathnaweera <omi...@wso2.com> >> wrote: >> >>> Hi Manujith, >>> >>> Pushpalanka will be able to provide you more details on this. >>> >>> For the time being, you can try out the current XACML implementation by >>> following the resources at [1]. >>> >>> The documentation related to XACML architecture [2] will help you to >>> understand the current implementation. The feature codebase can be found at >>> [3]. In the codebase, EntitlmentService [4] is the SOAP service >>> implementation. >>> >>> [1] - >>> https://docs.wso2.com/display/IS510/Configuring+the+Policy+Administration+Point >>> , >>> http://pushpalankajaya.blogspot.com/2013/06/try-out-xacml-policies-with-wso2.html >>> [2] - https://docs.wso2.com/display/IS510/Access+Control >>> [3] - >>> https://github.com/wso2/identity-framework/tree/master/components/entitlement >>> [4] - >>> https://github.com/wso2/identity-framework/blob/master/components/entitlement/org.wso2.carbon.identity.entitlement/src/main/java/org/wso2/carbon/identity/entitlement/EntitlementService.java >>> >>> Regards, >>> Omindu. >>> >>> On Tue, Mar 22, 2016 at 6:51 PM, Chamila Wijayarathna <cham...@wso2.com> >>> wrote: >>> >>>> [Adding Pushpalanka] >>>> >>>> On Tue, Mar 22, 2016 at 6:05 PM, Manujith Pallewatte < >>>> manujith...@gmail.com> wrote: >>>> >>>>> Hi Omindu, >>>>> >>>>> It that case, I'm interested in doing *Proposal 22: [IS] RESTful Fine >>>>> Grained Authorization-as-a-Service (AZaaS)* >>>>> Since I'm a bi behind the schedule for starting over with it, can you >>>>> give me some pointers to start working? As I get it I have to focus on >>>>
Re: [Dev] Fwd: [GSoC 16'] Proposal 20: [IS] SCIM 2.0 Support to WSO2 Identity Server
Hi Omindu, Thank alot, I will look into those. also should I be working on the https://github.com/wso2/identity-framework codebase or https://github.com/wso2/product-is codebase i was under the impression that the latter is what I should focus on On Tue, Mar 22, 2016 at 7:55 PM, Omindu Rathnaweera <omi...@wso2.com> wrote: > Hi Manujith, > > Pushpalanka will be able to provide you more details on this. > > For the time being, you can try out the current XACML implementation by > following the resources at [1]. > > The documentation related to XACML architecture [2] will help you to > understand the current implementation. The feature codebase can be found at > [3]. In the codebase, EntitlmentService [4] is the SOAP service > implementation. > > [1] - > https://docs.wso2.com/display/IS510/Configuring+the+Policy+Administration+Point > , > http://pushpalankajaya.blogspot.com/2013/06/try-out-xacml-policies-with-wso2.html > [2] - https://docs.wso2.com/display/IS510/Access+Control > [3] - > https://github.com/wso2/identity-framework/tree/master/components/entitlement > [4] - > https://github.com/wso2/identity-framework/blob/master/components/entitlement/org.wso2.carbon.identity.entitlement/src/main/java/org/wso2/carbon/identity/entitlement/EntitlementService.java > > Regards, > Omindu. > > On Tue, Mar 22, 2016 at 6:51 PM, Chamila Wijayarathna <cham...@wso2.com> > wrote: > >> [Adding Pushpalanka] >> >> On Tue, Mar 22, 2016 at 6:05 PM, Manujith Pallewatte < >> manujith...@gmail.com> wrote: >> >>> Hi Omindu, >>> >>> It that case, I'm interested in doing *Proposal 22: [IS] RESTful Fine >>> Grained Authorization-as-a-Service (AZaaS)* >>> Since I'm a bi behind the schedule for starting over with it, can you >>> give me some pointers to start working? As I get it I have to focus on >>> Balana engine, should I be interacting more with the code of Balana, or IS? >>> >>> Thank You >>> >>> On Mon, Mar 21, 2016 at 10:56 PM, Omindu Rathnaweera <omi...@wso2.com> >>> wrote: >>> >>>> Hi Manujith, >>>> >>>> Thank you for showing interest in the project. Unfortunately we have >>>> decided to remove the project from the project proposals list since we need >>>> to add the scim 2.0 support to an upcoming release which is scheduled to be >>>> done prior to the GSoC project period. We apologize for any inconvenience >>>> this may have caused. >>>> >>>> We have included a new project [1] to add *SAML Assertion >>>> Query/Request Profile support for WSO2 Identity Server*. If >>>> interested, you can go through the project details and submit a proposal >>>> for the new project or one of the other Identity Server projects (project >>>> 22 >>>> & 23). If you have any questions, feel free to raise. >>>> >>>> [1] - >>>> https://docs.wso2.com/display/GSoC/Project+Proposals+for+2016#ProjectProposalsfor2016-Proposal20:[IS]SAMLAssertionQuery/RequestProfilesupportforWSO2IdentityServer >>>> >>>> Thanks, >>>> Omindu. >>>> >>>> On Mon, Mar 21, 2016 at 9:59 PM, Pubudu Fernando <pubu...@wso2.com> >>>> wrote: >>>> >>>>> [adding mentors] >>>>> >>>>> On Mon, Mar 21, 2016 at 8:35 PM, Manujith Pallewatte < >>>>> manujith...@gmail.com> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I'm Manujith Pallewatte, a 2nd year undergraduate from Department of >>>>>> Computer Science and Engineering, University of Moratuwa. I'm interested >>>>>> in >>>>>> doing project for WSO2 for GSoC 2016. >>>>>> >>>>>> I already picked Proposal 20 considering my capabilities and interest >>>>>> in the area. >>>>>> As a Oracle certified java programmer I have a firm hand on Java, and >>>>>> I have developed several REST APIs on top of different platforms (like >>>>>> google app engine). And currently I'm reading on SCIM specification. >>>>>> >>>>>> So far, I cloned the *product-is* repo ( >>>>>> https://github.com/wso2/product-is) which i believe to be the source >>>>>> of Identity Server and then build it. I played around with the system a >>>>>> bit >>>>>> and now trying to connect different services to it. >>>>>> >&
Re: [Dev] Fwd: [GSoC 16'] Proposal 20: [IS] SCIM 2.0 Support to WSO2 Identity Server
Hi Omindu, It that case, I'm interested in doing *Proposal 22: [IS] RESTful Fine Grained Authorization-as-a-Service (AZaaS)* Since I'm a bi behind the schedule for starting over with it, can you give me some pointers to start working? As I get it I have to focus on Balana engine, should I be interacting more with the code of Balana, or IS? Thank You On Mon, Mar 21, 2016 at 10:56 PM, Omindu Rathnaweera <omi...@wso2.com> wrote: > Hi Manujith, > > Thank you for showing interest in the project. Unfortunately we have > decided to remove the project from the project proposals list since we need > to add the scim 2.0 support to an upcoming release which is scheduled to be > done prior to the GSoC project period. We apologize for any inconvenience > this may have caused. > > We have included a new project [1] to add *SAML Assertion Query/Request > Profile support for WSO2 Identity Server*. If interested, you can go > through the project details and submit a proposal for the new project or > one of the other Identity Server projects (project 22 & 23). If you have > any questions, feel free to raise. > > [1] - > https://docs.wso2.com/display/GSoC/Project+Proposals+for+2016#ProjectProposalsfor2016-Proposal20:[IS]SAMLAssertionQuery/RequestProfilesupportforWSO2IdentityServer > > Thanks, > Omindu. > > On Mon, Mar 21, 2016 at 9:59 PM, Pubudu Fernando <pubu...@wso2.com> wrote: > >> [adding mentors] >> >> On Mon, Mar 21, 2016 at 8:35 PM, Manujith Pallewatte < >> manujith...@gmail.com> wrote: >> >>> Hi, >>> >>> I'm Manujith Pallewatte, a 2nd year undergraduate from Department of >>> Computer Science and Engineering, University of Moratuwa. I'm interested in >>> doing project for WSO2 for GSoC 2016. >>> >>> I already picked Proposal 20 considering my capabilities and interest in >>> the area. >>> As a Oracle certified java programmer I have a firm hand on Java, and I >>> have developed several REST APIs on top of different platforms (like google >>> app engine). And currently I'm reading on SCIM specification. >>> >>> So far, I cloned the *product-is* repo ( >>> https://github.com/wso2/product-is) which i believe to be the source of >>> Identity Server and then build it. I played around with the system a bit >>> and now trying to connect different services to it. >>> >>> So I want to know if I'm going in the wrong direction (with the >>> objective of working for the above proposal) and please give me some >>> suggestions to read or work on to improve my familiarity with the system. >>> >>> Thank You >>> -- >>> >>> >>> >>> [image: Manujith Pallewatte on about.me] >>> >>> Manujith Pallewatte >>> about.me/manzzup >>> <http://about.me/manzzup> >>> >>> >>> >>> -- >>> >>> >>> >>> [image: Manujith Pallewatte on about.me] >>> >>> Manujith Pallewatte >>> about.me/manzzup >>> <http://about.me/manzzup> >>> >>> _______ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Pubudu Fernando* >> Software Engineer - Intern >> WSO2 Inc. >> m: +94 77 888 2543 >> >> <https://lk.linkedin.com/in/pubuduf> <http://blog.pubudu.xyz/> >> <https://github.com/pubudu91> >> <http://stackoverflow.com/users/4329912/pubudu> >> >> > > > -- > Omindu Rathnaweera > Software Engineer, WSO2 Inc. > Mobile: +94 771 197 211 > -- [image: Manujith Pallewatte on about.me] Manujith Pallewatte about.me/manzzup <http://about.me/manzzup> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [GSoC 16'] Proposal 20: [IS] SCIM 2.0 Support to WSO2 Identity Server [Adding Mentors]
Hi, I'm Manujith Pallewatte, a 2nd year undergraduate from Department of Computer Science and Engineering, University of Moratuwa. I'm interested in doing project for WSO2 for GSoC 2016. I already picked Proposal 20 considering my capabilities and interest in the area. As a Oracle certified java programmer I have a firm hand on Java, and I have developed several REST APIs on top of different platforms (like google app engine). And currently I'm reading on SCIM specification. So far, I cloned the *product-is* repo (https://github.com/wso2/product-is) which i believe to be the source of Identity Server and then build it. I played around with the system a bit and now trying to connect different services to it. So I want to know if I'm going in the right direction (with the objective of working for the above proposal) and please give me some suggestions to read or work on to improve my familiarity with the system. Thank You -- [image: Manujith Pallewatte on about.me] Manujith Pallewatte about.me/manzzup <http://about.me/manzzup> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Fwd: [GSoC 16'] Proposal 20: [IS] SCIM 2.0 Support to WSO2 Identity Server
Hi, I'm Manujith Pallewatte, a 2nd year undergraduate from Department of Computer Science and Engineering, University of Moratuwa. I'm interested in doing project for WSO2 for GSoC 2016. I already picked Proposal 20 considering my capabilities and interest in the area. As a Oracle certified java programmer I have a firm hand on Java, and I have developed several REST APIs on top of different platforms (like google app engine). And currently I'm reading on SCIM specification. So far, I cloned the *product-is* repo (https://github.com/wso2/product-is) which i believe to be the source of Identity Server and then build it. I played around with the system a bit and now trying to connect different services to it. So I want to know if I'm going in the wrong direction (with the objective of working for the above proposal) and please give me some suggestions to read or work on to improve my familiarity with the system. Thank You -- [image: Manujith Pallewatte on about.me] Manujith Pallewatte about.me/manzzup <http://about.me/manzzup> -- [image: Manujith Pallewatte on about.me] Manujith Pallewatte about.me/manzzup <http://about.me/manzzup> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
