Author: shawkins Date: 2010-09-14 14:32:18 -0400 (Tue, 14 Sep 2010) New Revision: 2571 Modified: branches/7.1.x/build/kits/jboss-container/conf/props/teiid-security-roles.properties branches/7.1.x/build/kits/jboss-container/teiid-releasenotes.html Log: TEIID-1246 release not update for sysadmin Modified: branches/7.1.x/build/kits/jboss-container/conf/props/teiid-security-roles.properties =================================================================== --- branches/7.1.x/build/kits/jboss-container/conf/props/teiid-security-roles.properties 2010-09-14 17:18:39 UTC (rev 2570) +++ branches/7.1.x/build/kits/jboss-container/conf/props/teiid-security-roles.properties 2010-09-14 18:32:18 UTC (rev 2571) @@ -1,3 +1,3 @@ # A roles.properties file for use with the UsersRolesLoginModule -# username=role1,role1. +# username=role1,role2 admin=admin Modified: branches/7.1.x/build/kits/jboss-container/teiid-releasenotes.html =================================================================== --- branches/7.1.x/build/kits/jboss-container/teiid-releasenotes.html 2010-09-14 17:18:39 UTC (rev 2570) +++ branches/7.1.x/build/kits/jboss-container/teiid-releasenotes.html 2010-09-14 18:32:18 UTC (rev 2571) @@ -40,6 +40,8 @@ </ul> <h4>from 7.1</h4> <ul> + <li>The SYSADMIN schema was created to hold procedures and tables that should not be generally accessible. SYS and pg_catalog are now always accessible - permissions do not apply to these schemas. The SYS.getBinaryVDBResource, SYS.getCharacterVDBResource, and SYS.getVDBResourcePaths have been replaced with the + SYSADMIN.VDBResources table. The Matviews table and the refreshMatView/refreshMatViewRow procedures were also moved into SYSADMIN. <li>Overwriting an existing VDB will cause old connections to be terminated. Production systems should rely on VDB versioning. <li>The jdbc:metamatrix JDBC URL prefix is no longer accepted. Use jdbc:teiid instead. <li>Model visibility no longer restricts access to tables and procedures. Setting visible to false will only hide entries from system tables. Data roles should be used to restrict data access.