row level security

[R. Jahn]

Dear H2 community:

I am wondering if H2 supports row level security? 

My search in h2database.com and forums so far has failed to provide a definitive info.

Thank you in advance for advice.

Sincerely,
Ray

[Noel Grandin]

Nope

[R. Jahn]

Re: row level security (RLS)

HSQLDB 2.5.0, user guide, page 101,
fine grained access control,
Filter Where clause for RLS.

Dear Noel:

Thanks for feedback. 

Would H2 become capable of RLS by adding (Where clause) to Grant statement?

in syntax

Grant ... on Table client_po to role_merchant
Where ( client, USER() ) in (Select client, merchant from permission_table);

in semantics

Grant ... on Table client_po to role_merchant
Where ( client, USER() ) in permission_table( client, merchant );

The reasoning is provided below.

Sincerely,
Ray

[background]

We are looking for a terse solution to access control, with a differentiation metric based on the (assignment / association).

Each client, or (client, division), is assigned to a group of merchants. The organization table (client, merchant) ensues. Company adjusts the groups (reallocating merchants) upon business change. In database each client should be served / handled only by assigned / authorized merchants at the given time.

Two types of Grant syntax exist for access control.

1. table based
   Grant ... on Table client_po to role_merchant;

In table based approach, all merchants are allowed access to all client POs in the entire table. No differentiation among merchants. This is not enough.

2. row based
   Grant ... on Table client_po to role_merchant
   Where ( client, USER() ) in permission_table( client, merchant );

In row based approach, when the (Where ... in ...) predicate is supported in the Grant statement, the permission_table( client, merchant ) would control, ROW BY ROW, the access to the table of trading data. This RLS, based on differentiation metric of (client-merchant association), is what we need. This scenario of (client-merchant association) may be extended to financial industry, health care systems, insurance claims, etc., where agents are assigned / authorized to serve the designated institutional clients.

Alternative designs could achieve similar security results. But the Where clause in HSQLDB 2.5.0 appears to be a clever winner hands down. It is terse, versatile, easy on code maintenance, and very importantly, easy on association management (personnel reallocation) in database.

[Noel Grandin]

That looks like a reasonable design