Don't we need to restrict this to a particular space in registry? So that this would not overwrite the wanted data.
On Tue, Jun 2, 2015 at 11:02 PM, Kasun Indrasiri <[email protected]> wrote: > Looks good. Please proceed with the fix and update the documentation. > > On Mon, Jun 1, 2015 at 10:44 AM, Nadeeshaan Gunasinghe < > [email protected]> wrote: > >> Hi all, >> In order to persist content in to mediation layer I added an initial >> implementation and via that we can use the following mediation logic to >> store new persistent content in the registry, >> >> <property name="conf:/Resource/bar value="xx" | expression="yy" >> scope="registry"/> and >> <property name="conf:/Resource/foo@prop value="xx" | expression="yy" >> scope="registry"/> >> >> In this implementation it uses scope to determine whether the content >> need to be stored persistently or not. Then a new registry entry is created >> to store the content either as a resource or as a new resource property. >> Name attribute include the registry location to store the content >> >> Initial implementation can be found bellow. >> >> [1] >> https://github.com/wso2/wso2-synapse/compare/master...nadeeshaan:Persistant_Property_Impl >> [2] >> https://github.com/wso2/carbon-mediation/compare/master...nadeeshaan:Persistant_Property_Impl >> >> Regards >> >> >> >> On Tue, May 26, 2015 at 10:03 AM, Malaka Silva <[email protected]> wrote: >> >>> Hi, >>> >>> Yes this make sense if the provider does not support password grant type. >>> >>> But my concern is security. If we save the access tokens and refresh >>> token it's visible to all parties. >>> >>> Can we do the same with secure-vault instead. WDYT? >>> >>> eg:- >>> >>> wso2:vault-lookup('UserManager.AdminUser.Password') >>> >>> wso2:vault-set('UserManager.AdminUser.Password','<VALUE>'); >>> >>> On Tue, May 26, 2015 at 9:51 AM, Kasun Indrasiri <[email protected]> wrote: >>> >>>> Hi, >>>> >>>> It is often required to persist content into the underlying registry >>>> impl during message mediation (in stateful mediation scenarios). For >>>> example, with connector we need to keep the access token/refresh token >>>> persisted. Therefore a generic mechanism of persisting content from >>>> mediation flow will be useful. >>>> >>>> At the moment, we do support retrieving content from the registry with >>>> following mediation logic. >>>> >>>> <property name="myProperty" action="set" >>>> >>>> expression="get-property('registry', 'conf:/Resource/bar')" >>>> >>>> Similarly, we can implement the content persistent capability with >>>> property mediator using its scope concept. >>>> >>>> <property name="conf:/Resource/bar value="xx" | expression="yy" >>>> scope="registry"/> >>>> >>>> Please share your thoughts. >>>> @Nadeeshan/Buddhima : Will this design fits into solving access >>>> token/refresh token handling limitations with Connectors? >>>> >>>> -- >>>> Kasun Indrasiri >>>> Software Architect >>>> WSO2, Inc.; http://wso2.com >>>> lean.enterprise.middleware >>>> >>>> cell: +94 77 556 5206 >>>> Blog : http://kasunpanorama.blogspot.com/ >>>> >>> >>> >>> >>> -- >>> >>> Best Regards, >>> >>> Malaka Silva >>> Senior Tech Lead >>> M: +94 777 219 791 >>> Tel : 94 11 214 5345 >>> Fax :94 11 2145300 >>> Skype : malaka.sampath.silva >>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 >>> Blog : http://mrmalakasilva.blogspot.com/ >>> >>> WSO2, Inc. >>> lean . enterprise . middleware >>> http://www.wso2.com/ >>> http://www.wso2.com/about/team/malaka-silva/ >>> <http://wso2.com/about/team/malaka-silva/> >>> >>> Save a tree -Conserve nature & Save the world for your future. Print >>> this email only if it is absolutely necessary. >>> >> >> > > > -- > Kasun Indrasiri > Software Architect > WSO2, Inc.; http://wso2.com > lean.enterprise.middleware > > cell: +94 77 556 5206 > Blog : http://kasunpanorama.blogspot.com/ > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Susinda Perera* Software Engineer Mobile:(+94)716049075 WSO2 Inc. http://wso2.com/ Tel : 94 11 214 5345 Fax :94 11 2145300
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
