Hi Sagara, On Mon, Jun 8, 2015 at 5:07 AM, Sagara Gunathunga <[email protected]> wrote:
> > It seems Governance Center/ES2 Publisher and Store portals also depend on > "login" permission we traditionally defined for Carbon console but IMHO we > should have 3 distinct login permissions for above 3 portals. > > login - For Carbon Admin Console Login > publisher-login - For ES2 based publisher login > store-login - For ES2 based store login > > As an example, say as an admin I don't want anyone else to be logged-in to > Admin console but depend on their designation some may login to Publisher > and some may login to store, AFAIK without 3 separate permissions we can't > achieve this kind of use cases. > > WDYT ? > +1. Additionally we will need to think on asset specific permissions layer as well.Such that,hide the asset from left side button based on logged user's permissions. For eg: In APIManager scenarios,we have defined custom permissions for Publisher api creation ['Create'/'Publish']. Such that,if a user doesn't have those permissions we will need to hide the API asset menu option from left side top button in publisher. Thanks; > > Thanks ! > -- > Sagara Gunathunga > > Architect; WSO2, Inc.; http://wso2.com > V.P Apache Web Services; http://ws.apache.org/ > Linkedin; http://www.linkedin.com/in/ssagara > Blog ; http://ssagara.blogspot.com > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Lalaji Sureshika WSO2, Inc.; http://wso2.com/ email: [email protected]; cell: +94 71 608 6811 blog: http://lalajisureshika.blogspot.com
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
