Re: [Architecture] [Analytics] Introducing a common permission model.

As of the offline discussion We decided to go ahead with the following databases *PERMISSIONS* APP_NAME VARCHAR(3) NOT NULL PERMISSION_STRING VARCHAR(50) NOT NULL PRIMARY KEY (APP_NAME, PERMISSION_STRING) *ROLE_PERMISSIONS* APP_NAME VARCHAR(3) NOT NULL PERMISSION_STRING VARCHAR(50) NOT NULL

Re: [Architecture] [Analytics] Introducing a common permission model.

On Wed, Oct 18, 2017 at 2:20 PM, Lasantha Samarakoon wrote: > ​Where do we maintain the resource to permission mapping? Is it at the > common component level or each app has to maintain its own mapping? > > Resource to permission mapping needs to be maintained at each app

Re: [Architecture] [Analytics] Introducing a common permission model.

​Where do we maintain the resource to permission mapping? Is it at the common component level or each app has to maintain its own mapping? Resource to permission mapping needs to be maintained at each app level. Common component doesn't need to know about the resources but only roles and

Re: [Architecture] [Analytics] Introducing a common permission model.

Hi Lasantha, Where do we maintain the resource to permission mapping? Is it at the common component level or each app has to maintain its own mapping? Thanks, Tanya On Wed, Oct 18, 2017 at 1:34 PM, Lasantha Samarakoon wrote: > Hi all, > > In the new React based dashboard

[Architecture] [Analytics] Introducing a common permission model.

Hi all, In the new React based dashboard component we need to implement a permission model based on user roles to limit access to dashboard resources. Since this can be a common requirement among all the React based apps in under Analytics we thought of introducing a common component to serve the