jumpinjackie
commented
9 years ago Won't implement for 1.0.
This is taking the whitelisting concept to crazy levels of complexity, which I do not have the time to implement or fully verify in the 1.0 timeframe.
I intend to release 1.0 final before the start of July.
Hi Jackie,
I am using one database feature source for multiple layers. Each layer connect with specific data table in the database. Current whitelist is very handy for the user who are using file-based feature source such as shp, sqlite, and sdf to restrict which feature sources are able to be accessed with certain actions by specific users.
If the whitelist can also allow users to decide which feature class (data table) under their database feature source are able to be accessed with certain actions by specific users. It will be really awesome and useful.
"MapGuide.FeatureSourceConfiguration" => array( "Library://test/SQLServerDB.FeatureSource" => array( "FeatureClass" => array( //data table or feature class list (If the tables are not listed here, users won't be able to
//access it at all "AllowFeatureClass" => array( table1Name, table2Name, table3Name ); ) "Actions" => array( "GETCONNECTIONPROPERTYVALUES" => array( "AllowRoles" => array("Author", "Administrator") ), "ENUMERATEDATASTORES" => array( "AllowRoles" => array("Author", "Administrator") ), "GETPROVIDERCAPABILITIES" => array( "AllowRoles" => array("Author", "Administrator") ), "GETFEATUREPROVIDERS" => array( "AllowRoles" => array("Author", "Administrator") ), "GETSCHEMAMAPPING" => array( "AllowRoles" => array("Author", "Administrator") ), "Representations" => array( "xml" => array(), "json" => array(), "geojson" => array(), "html" => array(), "kml" => array(), "czml" => array() ) ) ),
What do you think about this idea? Thank you so much!