Security options for mashup services?
Hi,
I did not see any documentations on security options available for mashup services (beside share your mashup). Is there any other form of security coming up?
Bookmark/Search this post with:
- Login or register to post comments
- Printer friendly version
- 334 reads
Plans for future releases
Hi,
We have planned for security features such as allowing a user to specify who has access to his or her mashups (for which we already have the infrastructure in place) in a future release.
If you join our developer mailing list (mashup-dev@wso2.org) you can keep up with progress on this and other areas.
Bye,
Channa.
Hi again, Thank you for
Hi again, Thank you for your reply.
Let me try to understand wso2 abit. By all means, you guys offer a great stack of infra but I have yet to see how it fits together. For example, I believe Mashup Server aims composition of services which apparently current wso2 esb does not support? If so if I were to use in an enterprise environment to mashup my various data sources effectively, should it be integrated into your esb? or tight to your registry for discovery maybe?
Thank you in advance..
How it fits together
Hi
So far we have kept the development of the indepedent functions reasonably separate - as you will have noticed that has given us a great deal of agility. Now we are working on how to host and manage the different components in whatever topology you want - single VM, multi-VM cluster, etc.
The plan is they all work off the Registry (or any other registry) and share common functions. We already have some capabilities in this direction, for example we have ways you can host the Mashup Server and Data Services in the same instance (but its not directly exposed - you have to know the right backdoor!).
Once we've made a little more progress on this next phase we'll post some more details.
Paul