A scope defines a unique action (view_user_profile, update_profile_status, etc). You won't have two APIs performing the same action.
And it confuses the authorization part too. Ex: If role 'a' has permissions for scope 'x' on 'API1', it won't necessarily mean role 'a' can perform the same action on 'API2' because what API2 does is different to what API1 does. Thanks, NuwanD. On Fri, Jun 24, 2016 at 11:33 AM, Niranjan Karunanandham <niran...@wso2.com> wrote: > Hi APIM, > > In APIM 1.10.0, I need to use the same scope name for two different API. > When I try to assign a scope (which is already assigned to an API) to an > API, I get the error message "Scope is already assigned by another API". Is > this by design? Any reason as to why we can't apply the same scope to > multiple APIs? > > Regards, > Nira > > -- > > > *Niranjan Karunanandham* > Associate Technical Lead - WSO2 Inc. > WSO2 Inc.: http://www.wso2.com > -- Nuwan Dias Technical Lead - WSO2, Inc. http://wso2.com email : nuw...@wso2.com Phone : +94 777 775 729
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
