Hi Dinusha,

Does two userstores mean two separate permission databases? If so this is
expected behavior. If not, we probably need to look into the permission
storing/retrieving logic in UM. Also, IIRC, there were some concepts of
internal/external roles added to UM. Are you making use of that as well?

Thanks,
Senaka.


On Tue, Apr 16, 2013 at 10:01 PM, Dinusha Senanayaka <[email protected]>wrote:

> Hi All,
>
> We have mount the registries of API Store and API Publisher nodes. But we
> encountered an issue when Store and Publisher nodes are pointed to
> different user stores. When creating an API with public visibility, we
> assign 'wso2.anonymous.role' permission to api registry resource (Refer to
> the code segment [1]).. This works if both publisher and store nodes are
> point to the same user store. But when we have point them into two
> different user stores, the  'wso2.anonymous.role' permission has assigned
> only to the api in publisher node but not in the Store (Even both nodes are
> mounted into single registry). Any help/explanation would appreciate to
> resolve this.
>
> [1]
> RegistryAuthorizationManager authorizationManager = new
> RegistryAuthorizationManager (ServiceReferenceHolder.getUserRealm());
> ...
> ...
> authorizationManager.authorizeRole(APIConstants.ANONYMOUS_ROLE,
> resourcePath,
>                                                    ActionConstants.GET);
>
>
> Regards,
> Dinusha.
>
> --
> Dinusha Dilrukshi
> Software Engineer
> WSO2 Inc.: http://wso2.com/
> Mobile: +94725255071
> Blog: http://dinushasblog.blogspot.com/
>



-- 
*Senaka Fernando*
Member - Integration Technologies Management Committee;
Technical Lead; WSO2 Inc.; http://wso2.com*
Member; Apache Software Foundation; http://apache.org

E-mail: senaka AT wso2.com
**P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
Linked-In: http://linkedin.com/in/senakafernando

*Lean . Enterprise . Middleware
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to