Re: [teiid-dev] Defining Data Roles - was [Re: [teiid-designer-dev] Proposed Schema for "ConfigurationInfo.def" file]
So the roles would be defined in the Designer and the users would be created and assigned
to the roles in JON?
If so, that seems like a reasonable approach.
Ted
----- Original Message -----
From: "Ramesh Reddy" <rareddy(a)redhat.com>
To: teiid-designer-dev(a)lists.jboss.org, teiid-dev(a)lists.jboss.org
Sent: Thursday, February 4, 2010 12:14:35 PM GMT -06:00 US/Canada Central
Subject: [teiid-dev] Defining Data Roles - was [Re: [teiid-designer-dev] Proposed Schema
for "ConfigurationInfo.def" file]
On Wed, 2010-02-03 at 13:02 -0500, Ted Jones wrote:
We should keep Jopr/JON as a possibility. If the data driving UI is
User/group/role, we should be able to code that into our plugin.
Even if we can have rich UI in the JON tool, in order for this to work
we would need to expose the Model's metadata through profile service,
such as Tables, columns, procedures etc. Which IMO is not feasible or
right place to do in a management tool.
There are two distinctive tasks here
1) At design time a data architect is defining the security model for
the data access defined by a VDB
2) Second as the production admin, see which user qualifies for a
particular role and do the role-mapping. As production admin would not
have any clue about your data model.
IMO, Designer is right tool for (1), JON for (2).
Ramesh..
PS: please correct the subject line in your next post. take off "was-*$"
_______________________________________________
teiid-dev mailing list
teiid-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/teiid-dev