Advanced TOAD Security Options
The approach discussed in the prior section was the original method by which TOAD supported a read-only mode of operation (and it is still used today). Over time, however, administrators asked for additional and more complex methods to control their TOAD users. And even though we always said that's what Oracle database security is for, the requests nonetheless persisted. TOAD administrators wanted to manage and control TOAD user behavior based on screens, wizards and utilities. Thus began the quest to create TOAD security.
Beginning with version 7.3, TOAD offered an advanced security management screen permitting your site's TOAD administrator to specifically define which TOAD screens, wizards, and utilities were available and executable by special TOAD security roles granted to users. Unfortunately, this TOAD security approach proved quite resource intensive, as it had to be done at the database level. Thus, for each database you manage that has TOAD users, you had to define these special TOAD roles and then define what users could or could not do within TOAD.
Beginning with version 9.5, TOAD began offering the TOAD Group Policy Manager (TGPM), which totally centralizes the implementation of this application-level TOAD security. To use this functionality, you simply install the TGPM on a Windows server that is accessible by all TOAD users, and then define your security. Think of it as an "active directory" of sorts for controlling TOAD. This highly advanced security feature is beyond the scope of this chapter's basic setup and configuration theme. Because TGPM is not required for most general-purpose TOAD usage scenarios, it is not covered in this book. TOAD's online help and www.toadworld.com provide more information if you're interested.