You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bloodhound.apache.org by Wenli Ji <we...@yahoo.com.INVALID> on 2014/06/26 10:55:52 UTC

How to configure bh to support different customers

Hello,

It's will be very helpful if anyone could give me some hints...

We have a special requirement that we want our customers to access out bloodhound website to create tickets/wikis, but they should be invisible from each other.

For example, users belong to customer A cannot never view/modify tickets/wikis of customer B.

Is there a way to configure bloodhound to satisfy the requirement, or we have to develop it ourselves?

Thanks
Wenli

Re: How to configure bh to support different customers

Posted by Wenli Ji <we...@yahoo.com.INVALID>.
Thank you, Ryan.


On Thursday, June 26, 2014 6:01 PM, Ryan Ollos <ry...@gmail.com> wrote:
 


On Jun 26, 2014 3:56 PM, "Wenli Ji" <we...@yahoo.com.invalid> wrote:

>
> Hello,
>
> It's will be very helpful if anyone could give me some hints...
>
> We have a special requirement that we want our customers to access out
bloodhound website to create tickets/wikis, but they should be invisible
from each other.
>
> For example, users belong to customer A cannot never view/modify
tickets/wikis of customer B.
>
> Is there a way to configure bloodhound to satisfy the requirement, or we
have to develop it ourselves?
>
> Thanks
> Wenli

The permission policy attached to #777 should accomplish the aim for
tickets, or at least serve as a starting point:

https://issues.apache.org/bloodhound/ticket/777

For the wiki, you'll either want to implement a permission policy, or you
can use TracFineGrainedPermissions if the resource name or naming pattern
is known.

http://trac.edgewall.org/wiki/TracFineGrainedPermissions

Re: How to configure bh to support different customers

Posted by Ryan Ollos <ry...@gmail.com>.
On Jun 26, 2014 3:56 PM, "Wenli Ji" <we...@yahoo.com.invalid> wrote:
>
> Hello,
>
> It's will be very helpful if anyone could give me some hints...
>
> We have a special requirement that we want our customers to access out
bloodhound website to create tickets/wikis, but they should be invisible
from each other.
>
> For example, users belong to customer A cannot never view/modify
tickets/wikis of customer B.
>
> Is there a way to configure bloodhound to satisfy the requirement, or we
have to develop it ourselves?
>
> Thanks
> Wenli

The permission policy attached to #777 should accomplish the aim for
tickets, or at least serve as a starting point:

https://issues.apache.org/bloodhound/ticket/777

For the wiki, you'll either want to implement a permission policy, or you
can use TracFineGrainedPermissions if the resource name or naming pattern
is known.

http://trac.edgewall.org/wiki/TracFineGrainedPermissions