Hi all, @Youcef, Thanks for the use case, you have provided. We will try to incorporate it and will also share the updated user story.
@Fazlan, @Ishara, +1 for your suggestions. I will update the user story and share it. @Rajith, +1 for your suggestion. We could differentiate key values as *required* and *optional *based on requirements and user can specify these according to their needs. @Nuwan, Yes, I will work on these. As first step, I will work on design and implementation of saving these data against the Application and also will update the user story accordingly. Thanks & Regards, On Thu, Apr 19, 2018 at 11:18 AM, Nuwan Dias <[email protected]> wrote: > > > On Thu, Apr 19, 2018 at 11:15 AM, Rajith Roshan <[email protected]> wrote: > >> Hi all >> >> On Thu, Apr 19, 2018 at 9:19 AM, Nuwan Dias <[email protected]> wrote: >> >>> We don't have an application search capability right now right? If so I >>> don't think we should be adding such a feature. Because its unlikely >>> someone will have so many apps to search from. >>> >>> Some of the usages of these properties that I could think are (based on >>> some replies as well). >>> >>> 1. The need to publish these data to third party key managers when >>> generating application keys. >>> 2. The need to publish these data to application/subscription related >>> workflows. >>> 3. The need to access these data at the API Gateway when processing a >>> request (we could probably use the JWT for this). >>> >> >> So based on the usages of these attributes , and analyzing some of the >> use cases , I think better option is to have set of predefined key values >> for these application attributes. Giving the api consumer to add the >> both key , value pairs is meaning less because none of the key manager, >> gateway, workflows etc would not know how to process those values, if api >> consumer add what ever the values they have in mind as keys. >> I think we should have way to configure the set of predefined keys , >> where UI will read the config and render the keys as text fields so api >> consumer can provide values to those keys. >> With fixed set of pre configured attributes and we can also provide >> flexibility to define both key value pairs to the api consumer as well. >> > > +1. > >> >>> Anyhow, Vithursa let's take these requirements step by step. First lets >>> work on the design and implementation of saving these data against the >>> Application. >>> >>> On Thu, Apr 19, 2018 at 7:12 AM, Prasanna Dangalla <[email protected]> >>> wrote: >>> >>>> Hi Vithursa, >>>> >>>> Is there a possibilty of adding a functionality to search applications >>>> using custom attibutes. IMO this will aslo be a valied use case. >>>> >>>> Thanks >>>> Prasanna >>>> >>>> On Thu, Apr 19, 2018 at 5:35 AM Ishara Cooray <[email protected]> wrote: >>>> >>>>> Hi Vithursa, >>>>> >>>>> IMO you also need to have *another user story to delete applications >>>>> with custom attributes *where you need to make sure application is >>>>> successfully deleted from the application list along with its custom >>>>> attributes. >>>>> >>>>> Thanks & Regards, >>>>> Ishara Cooray >>>>> Senior Software Engineer >>>>> Mobile : +9477 262 9512 >>>>> WSO2, Inc. | http://wso2.com/ >>>>> Lean . Enterprise . Middleware >>>>> >>>>> On Thu, Apr 19, 2018 at 1:54 AM, Nuwan Dias <[email protected]> wrote: >>>>> >>>>>> Based on what Youcef has mentioned, we would need to include these >>>>>> additional properties on the JWT perhaps so that they can be accessed by >>>>>> the Gateway upon validating an access token. >>>>>> >>>>>> On Wed, Apr 18, 2018 at 11:38 PM, Youcef HILEM < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Hi, >>>>>>> ++++ for this feature. >>>>>>> I do not have access to the document [1] but we wish to develop >>>>>>> mediations >>>>>>> reinforcing access control to APIs according to these metadata >>>>>>> (example >>>>>>> (key: client-contract, value: contractx), ie : association between >>>>>>> client-id >>>>>>> & client-contract-id). >>>>>>> Thanks >>>>>>> Youcef HILEM >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Sent from: http://wso2-oxygen-tank.10903. >>>>>>> n7.nabble.com/WSO2-Architecture-f62919.html >>>>>>> _______________________________________________ >>>>>>> Architecture mailing list >>>>>>> [email protected] >>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Nuwan Dias >>>>>> >>>>>> Software Architect - WSO2, Inc. http://wso2.com >>>>>> email : [email protected] >>>>>> Phone : +94 777 775 729 >>>>>> >>>>>> _______________________________________________ >>>>>> Architecture mailing list >>>>>> [email protected] >>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>> >>>>>> >>>>> _______________________________________________ >>>>> Architecture mailing list >>>>> [email protected] >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>> -- >>>> *Prasanna Dangalla* >>>> Senior Software Engineer, WSO2, Inc.; http://wso2.com/ >>>> lean.enterprise.middleware >>>> >>>> >>>> *cell: +94 718 11 27 51* >>>> *twitter: @prasa77* >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> Nuwan Dias >>> >>> Software Architect - WSO2, Inc. http://wso2.com >>> email : [email protected] >>> Phone : +94 777 775 729 >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Rajith Roshan >> Senior Software Engineer, WSO2 Inc. >> Mobile: +94-7 <%2B94-71-554-8430>17-064-214 >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Nuwan Dias > > Software Architect - WSO2, Inc. http://wso2.com > email : [email protected] > Phone : +94 777 775 729 > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Vithursa Mahendrarajah Software Engineer WSO2 Inc. - http ://wso2.com Mobile : +947*66695643* <+94%2077%20819%201300> * <http://wso2.com/signature> <http://wso2.com/signature> <http://wso2.com/signature>*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
