US20070250905A1 - Method, System and Computer Program for Managing User Authorization Levels - Google Patents

Method, System and Computer Program for Managing User Authorization Levels Download PDF

Info

Publication number
US20070250905A1
US20070250905A1 US11767714 US76771407A US2007250905A1 US 20070250905 A1 US20070250905 A1 US 20070250905A1 US 11767714 US11767714 US 11767714 US 76771407 A US76771407 A US 76771407A US 2007250905 A1 US2007250905 A1 US 2007250905A1
Authority
US
Grant status
Application
Patent type
Prior art keywords
user
application
level
user authorization
authorization level
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US11767714
Inventor
David Clark
Marcee Burns
James Mathis
Danny Ashley
Jeff Jacobs
Trent Hinkel
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
AT&T Delaware Intellectual Property Inc
Original Assignee
AT&T Delaware Intellectual Property Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60Protecting data
    • G06F21/62Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database

Abstract

An embodiment of the invention is a method of managing user authorization levels for access to a plurality of applications. The method includes receiving a request from a user to establish a user profile and establishing an employment indicator for the user. A user authorization level template is obtained in response to the employment indicator. The user authorization level template identifies a plurality of applications and a user authorization level for each application. The user authorization levels are then associated with the user.

Description

    CROSS REFERENCE TO RELATED APPLICATIONS
  • This application is a continuation of U.S. patent application Ser. No. 10/611,436 filed Jun. 30, 2003, the contents of which are incorporated herein in their entirety.
  • BACKGROUND OF THE INVENTION
  • The present invention relates generally to managing user authorization levels.
  • Many software applications employ user authorization levels to control items such as user access and user permission levels for those applications. While helpful in preventing unauthorized access, such systems have a number of drawbacks. For a large application user base, the administrator(s) of those application(s) can be overwhelmed by numerous requests to add new users and/or to change the authorization levels of existing users of the applications(s). Additionally, if the user base extends to different work groups or even different cities from where the application administrator(s) are located, there are security issues where the administrator(s) must validate that the user is indeed an employee requiring application access and in many cases, the application administrator(s) will not know when to disable a user's access when the user is no longer employed by the company or they change to a different job within the company that does not require access to the application(s). Also, another security issue is the validation of permission levels for users in other work groups or cities where those users are not personally known by the application administrator(s).
  • Some application users require authorization levels for accessing multiple software applications (in a suite of applications) with the correct permission levels for each application. Enabling authorization levels (e.g., user access and permission) for multiple software applications can be a time-consuming process for an application administrator to handle even for a single user.
  • A new user may take over the job of an existing application user (i.e., the existing user has retired and a new person takes their job). This requires a time consuming amount of work for the application administrator(s) to duplicate the exact same application access and permission levels for the new user to match the access and permission levels of the outgoing user. If users need access to multiple software applications (in a suite of applications) with the correct permission levels for each application, then a problem exists in providing consistent standardized access and permission levels based on work group or job title. In addition, if the application access was created on an individual application basis, and one or more required applications were forgotten on the initial set-up of a user, then the user and application manager would have to go through the process of setting up access and permissions for those application(s) at a later time.
  • An additional problem for large application user groups is that certain types of users (company, contractor, application provider, etc.) may require certain restrictions or permissions based on their user type. An example is that a company user may need access to all application database records with no restrictions placed on viewing these records. However, a contractor user may need to have restrictions placed to protect proprietary information (such as pricing or another contractor's information) within the application databases. In addition, the application provider may need full administrative rights in order to maintain the application(s).
  • Many large companies have applications that require user IDs and passwords for security reasons. Application databases may require the current employee information must be entered in the application database prior to granting access to an application. This can be a time-consuming process to type employee information in the application database.
  • Existing systems attempt to manage employee authorization levels by establishing user profiles. The user profiles are used to define permissions such as read, write and execute permission. Permissions may be defined for an individual or for a group. Creation and management of these user profiles, however, requires significant involvement from an administrator.
  • SUMMARY OF THE INVENTION
  • An embodiment of the invention is a method of managing user authorization levels for access to a plurality of applications. The method includes receiving a request from a user to establish a user profile and establishing an employment indicator for the user. A user authorization level template is obtained in response to the employment indicator. The user authorization level template identifies a plurality of applications and a user authorization level for each application. The user authorization levels are then associated with the user.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • Referring to the exemplary drawings wherein like elements are numbered alike in the accompanying Figures:
  • FIG. 1 is a block diagram of an exemplary system for implementing the invention;
  • FIG. 2 is a flowchart of an exemplary process for creating or editing a user profile;
  • FIGS. 3-5 depict exemplary user interfaces for managing user authorization levels;
  • FIG. 6 depicts an exemplary user authorization level template database;
  • FIG. 7 depicts an exemplary user interface for managing user authorization level templates.
  • DETAILED DESCRIPTION OF THE INVENTION
  • FIG. 1 is a block diagram of an exemplary system 10 for managing user authorization levels to control access to applications and permissions within applications. Access refers to a user's ability to execute an application. Permissions refers to a user's abilities within an application (read, write, etc.). User authorization levels may include access and permission levels, along with other security indicators.
  • System 10 includes a number of user terminals 12 operated by users desiring access to applications. The user systems 12 may be implemented using general-purpose computers executing a computer program for carrying out the processes described herein. Alternatively, user systems 12 may be implemented using devices programmed primarily for accessing network 14 such as a dumb terminal. Further, the user systems 12 may be portable devices such as PDAs, cell phones, etc. User systems 12 are coupled to network 14 which may be any type of known network including a local area network (LAN), wide area network (WAN), global network (e.g., Internet), intranet, virtual private network (VPN), etc. User systems 12 may be physically located in geographically disperse locations. A user at user system 12 may act as an administrator depending on the user's authorization level, described in further detail herein.
  • The user systems 12 are coupled to an applications system 20 including a server 22 and a database 24. Database 24 may be a part of server 22, a separate device, or a collection of multiple devices accessible by server 22. The user systems 12 may be coupled to the applications system 20 through multiple networks (e.g., intranet and Internet) so that not all user systems 12 are coupled to the applications system 20 by the same network. One or all of the user systems 12 and applications system 20 may be connected to the network 14 in a wireless fashion and network 14 may be a wireless network.
  • In operation, an administrator at administrator system 18 is responsible for establishing a user profile for each user that may access server 22 and request access to an application. To facilitate managing user authorization levels, the administrator system 18 has access to a plurality of user authorization level templates on database 24. Further, human resource information on database 24 facilitates establishing or editing user authorization levels.
  • FIG. 2 is a flowchart of an exemplary process for creating or editing a user profile which utilizes user authorization level templates. The process begins at step 110 where there is a need to create or edit a user profile. This may be initiated for a variety of reasons such as a new user requesting a new profile or an existing user requesting a change in their user profile. The request is submitted to an administrator operating administrator system 18.
  • The administrator then either creates a new user profile or accesses an existing user profile from database 24 at step 112. FIG. 3 depicts an exemplary user interface for creating a user profile and in particular shows fields for entering personal information. Server 22 executes a user profile management software application that provides the functions disclosed herein, along with the user interfaces. If the administrator is editing a user profile, the fields would be completed. The user interface includes fields for a variety of information such as user identifier (CUID), name, address, etc.
  • In one embodiment of the invention, the personal information fields in the user profile may be populated using an auxiliary database as shown at step 114. In this embodiment, the user information is retrieved from another database (e.g., a human resources database) to complete fields in the user profile. This auxiliary data may be stored on database 24 and then imported into the user interface shown in FIG. 3. If such information is not available, then the administrator enters the personal information manually.
  • The administrator then assigns user authorization levels to the user as shown at step 116. FIG. 4 shows an exemplary user interface for entering user authorization levels. Through the interface in FIG. 4, the administrator can select an authorization level from an authorization level drop down menu 140 and an application from an application drop down menu 142. The user may be assigned a variety of authorization levels for each application. In an exemplary embodiment, three levels of access are used. Level 3 is the highest level of access to any application. Level 3 access to an application allows the assignment of level 2 or level 1 access to that application. Level 2 access to an application allows the assignment of level 1 access to that application. Level 1 access is at the user level, and is provided to users of the application(s). Level 1 access has no ability to assign access to other users.
  • Level 2 access also allows user level access, but in addition, provides the capability to assign level 1 access to other users. Level 2 access is given to one or two local people in each work group or district so that they can be responsible for adding/changing/deleting users in their own area. This provides more security since they personally know the people who need access and when someone retires, the Level 2 user know s that they have left, and they can remove that person's access. Level 3 access is the administrator level access for an application. Level 3 access also allows user level access, but in addition, provides the capability to assign level 2 (or level 1) access to other users. This enables the level 3 administrator to extend level 2 access to key users in each work group or district so that they can control their own access and permission levels in their own district.
  • An administrator has the ability to copy an existing user's access and permission level profile to a new user. As an example, assume that an existing user has access to ten different applications with varying degrees of access permission levels for each application. This user may have level 1 read only access in some applications, level 1 read-write capabilities in other applications, and level 2 read-write access in some applications. It would be tedious to totally build the new user's authorization levels from scratch on an application-by-application basis to in effect copy the outgoing user's exact authorization levels. The user interface of FIG. 3 includes a duplicate button 132 for copying the existing user's authorization levels to the new user.
  • As an alternative to entering the user authorization levels through the interface in FIG. 4, a user authorization level template may be associated with a user through the interface shown in FIG. 5. The administrator can associate a user authorization level template with a user by selecting a template from a template drop down menu 144.
  • A set of defined templates are stored in database 24 that provide an administrator the ability to create or change user permissions for a single user and any combination of multiple applications based on the person's job title. FIG. 6 depicts an exemplary user authorization level template database which correlates job titles 150 with applications 152. For each application 152, the database indicates the authorization level for each lob title. For example, certain job titles are provided read only access while other job titles are provided read write access to the DSX/FOX application. This allows the administrator to select a user authorization level template based on the user's job title. This is much faster than setting up individual user authorization levels on an application-by-application basis.
  • The database shown in FIG. 6 associates user authorization levels with job titles. It is understood that the templates may be indexed using indicators other than job title. Other employment indicators may be used to distinguish between the types of users (company employee, contractor, application provider, etc.) and apply certain restrictions or permissions based on their user type. Company users can see proprietary information such as pricing and all supplier information, which could be considered proprietary. Contractor users can only see proprietary information for their own company. Application developer users have full permissions so that they can develop, maintain, and support the applications.
  • Templates may be created and edited through a template inventory interface shown in FIG. 7. As shown in FIG. 7, an administrator can create new templates or edit/delete existing templates to define user authorization levels across multiple applications. The administrator can enter a new template identifier through template identifier field 160. Applications may be selected from a drop down application menu 162 and user authorization levels are defined through drop down user role and user group menus 164 and 166. As described above, the user authorization level templates provide user authorization levels for a variety of software applications indexed by employment indicators (job title, internal employee, contractor, full-time, part-time, etc.).
  • Once the user authorization levels are established by manual entry, duplicating existing user authorization levels or assigning a user authorization level template to the user, the user authorization levels are stored on database 24 as shown at step 118 of FIG. 2.
  • Subsequently, when a user attempts to access an application on server 22, the user profile associated with that user is accessed from database 24 and the authorization level for that application determined. Server 22 then permits access to the application and controls the appropriate permission within the application in accordance with the user authorization level.
  • As described above, the present invention can be embodied in the form of computer-implemented processes and apparatuses for practicing those processes. In an exemplary embodiment, the invention is embodied in computer program code executed by the server. The present invention may be embodied in the form of computer program code containing instructions embodied in tangible media, such as floppy diskettes, CD-ROMs, hard drives, or any other computer-readable storage medium, wherein, when the computer program code is loaded into and executed by a computer, the computer becomes an apparatus for practicing the invention. The present invention can also be embodied in the form of computer program code, for example, whether stored in a storage medium, loaded into and/or executed by a computer, or transmitted over some transmission medium, such as over electrical wiring or cabling, through fiber optics, or via electromagnetic radiation, wherein, when the computer program code is loaded into and executed by a computer, the computer becomes an apparatus for practicing the invention. When implemented on a general-purpose microprocessor, the computer program code segments configure the microprocessor to create specific logic circuits.
  • While the invention has been described with reference to exemplary embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted for elements thereof without departing from the scope of the invention. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the invention without departing from the essential scope thereof. Therefore, it is intended that the invention not be limited to the particular embodiment disclosed as the best mode contemplated for carrying out this invention, but that the invention will include all embodiments falling within the scope of the appended claims. Moreover, the use of the terms first, second, etc. do not denote any order or importance, but rather the terms first, second, etc. are used to distinguish one element from another. Furthermore, the use of the terms a, an, etc. do not denote a limitation of quantity, but rather denote the presence of at least one of the referenced item.

Claims (20)

  1. 1. A method of managing user authorization levels, the method comprising:
    receiving a request to establish or edit a profile for a user associated with an employment indicator;
    retrieving a user authorization level template based on the employment indicator, the user authorization level template identifying an application and a user authorization level for the application; and
    associating the user authorization level with the user.
  2. 2. The method of claim 1 wherein:
    the employment indicator distinguishes an employee from a contractor.
  3. 3. The method of claim 1 wherein:
    the employment indicator is job title.
  4. 4. The method of claim 1 wherein:
    the user authorization level indicates an access level for the application.
  5. 5. The method of claim 4 wherein:
    the user authorization level indicates a permission level for the application.
  6. 6. The method of claim 1 wherein:
    the user authorization level includes administration level permitting or denying the user an ability to assign an authorization level to the application to other users.
  7. 7. The method of claim 1 wherein:
    the user profile includes user personal information, the user personal information being retrieved from an auxiliary database.
  8. 8. The method of claim 7 wherein:
    the user personal information being retrieved from a human resources database.
  9. 9. A computer program for managing user authorization levels, the computer program including instructions for causing a computer to implement:
    receiving a request to establish or edit a profile for a user associated with an employment indicator;
    retrieving a user authorization level template based on the employment indicator, the user authorization level template identifying an application and a user authorization level for the application;
    associating the user authorization level with the user.
  10. 10. The computer program of claim 9 wherein:
    the employment indicator distinguishes an employee from a contractor.
  11. 11. The computer program of claim 9 wherein:
    the employment indicator is job title.
  12. 12. The computer program of claim 9 wherein:
    the user authorization level indicates an access level for the application.
  13. 13. The computer program of claim 12 wherein:
    the user authorization level indicates a permission level for the application.
  14. 14. The computer program of claim 9 wherein:
    the user authorization level includes administration level permitting or denying the user an ability to assign an authorization level to the application to other users.
  15. 15. The computer program of claim 9 wherein:
    the user profile includes user personal information, the user personal information being retrieved from an auxiliary database.
  16. 16. The computer program of claim 15 wherein:
    the user personal information being retrieved from a human resources database.
  17. 17. A system for managing user authorization levels, the system comprising:
    means for receiving a request to establish or edit a profile for a user associated with an employment indicator;
    means for retrieving a user authorization level template based on the employment indicator, the user authorization level template identifying an application and a user authorization level for the application;
    means for the applications system associating the user authorization level with the user.
  18. 18. The system of claim 17 wherein:
    the employment indicator distinguishes an employee from a contractor.
  19. 19. The system of claim 17 wherein:
    the employment indicator is job title.
  20. 20. The system of claim 17 wherein:
    the user authorization level indicates an access level for the application.
US11767714 2003-06-30 2007-06-25 Method, System and Computer Program for Managing User Authorization Levels Abandoned US20070250905A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US10611436 US7237119B2 (en) 2003-06-30 2003-06-30 Method, system and computer program for managing user authorization levels
US11767714 US20070250905A1 (en) 2003-06-30 2007-06-25 Method, System and Computer Program for Managing User Authorization Levels

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US11767714 US20070250905A1 (en) 2003-06-30 2007-06-25 Method, System and Computer Program for Managing User Authorization Levels

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US10611436 Continuation US7237119B2 (en) 2003-06-30 2003-06-30 Method, system and computer program for managing user authorization levels

Publications (1)

Publication Number Publication Date
US20070250905A1 true true US20070250905A1 (en) 2007-10-25

Family

ID=33541314

Family Applications (2)

Application Number Title Priority Date Filing Date
US10611436 Active 2025-06-13 US7237119B2 (en) 2003-06-30 2003-06-30 Method, system and computer program for managing user authorization levels
US11767714 Abandoned US20070250905A1 (en) 2003-06-30 2007-06-25 Method, System and Computer Program for Managing User Authorization Levels

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US10611436 Active 2025-06-13 US7237119B2 (en) 2003-06-30 2003-06-30 Method, system and computer program for managing user authorization levels

Country Status (1)

Country Link
US (2) US7237119B2 (en)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060179321A1 (en) * 2005-02-07 2006-08-10 Nigel Dawson Method and system of applying user permissions to an application program environment
US20110030051A1 (en) * 2009-07-29 2011-02-03 International Business Machines Corporation Autonomic manufacturing operator authorization adjustment
US8195819B1 (en) * 2009-07-13 2012-06-05 Sprint Communications Company L.P. Application single sign on leveraging virtual local area network identifier
US8443429B1 (en) 2010-05-24 2013-05-14 Sprint Communications Company L.P. Integrated sign on
US9059987B1 (en) 2013-04-04 2015-06-16 Sprint Communications Company L.P. Methods and systems of using single sign-on for identification for a web server not integrated with an enterprise network
US9558341B1 (en) 2004-10-07 2017-01-31 Sprint Communications Company L.P. Integrated user profile administration tool

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040177073A1 (en) * 2003-01-17 2004-09-09 Harry Snyder Executable application access management system
US20050119924A1 (en) * 2003-08-01 2005-06-02 Simpson Brian R. Computerized methods and software for business management
US20050198512A1 (en) * 2004-03-02 2005-09-08 International Business Machines Corporation System, method and program product for managing privilege levels in a computer system
US9288052B2 (en) * 2006-04-13 2016-03-15 Moreover Acquisition Corporation Method and apparatus to provide an authoring tool to create content for a secure content service
US20150295923A1 (en) * 2007-03-28 2015-10-15 Autodesk, Inc. Environment based switching between two dimensions and three dimensions
US20090308198A1 (en) * 2008-06-17 2009-12-17 Martin Jastrzembowski Starter System with Integral Clutch Pinion for Start-Stop Engine Cranking
US8533604B1 (en) * 2008-06-25 2013-09-10 Emc Corporation Techniques for user interface selection
CN102112978B (en) 2008-07-29 2017-04-12 惠普开发有限公司 Resource Deployment Manager
US9069774B1 (en) * 2008-11-04 2015-06-30 Infoblox Inc. Graphical visualization and management of networks
US8209638B2 (en) * 2008-12-31 2012-06-26 Sap Ag Customization abstraction
US9519425B1 (en) * 2010-06-28 2016-12-13 EMC IP Holding Company, LLC Techniques for device user interfaces
US8646100B2 (en) 2011-06-03 2014-02-04 Apple Inc. Method for executing an application in a restricted operating environment
KR101326896B1 (en) * 2011-08-24 2013-11-11 주식회사 팬택 Terminal and method for providing risk of applications using the same
WO2013053976A1 (en) * 2011-10-11 2013-04-18 Sandvik Mining And Construction Oy Arrangement for updating a control system
KR20150020398A (en) * 2013-08-13 2015-02-26 삼성전자주식회사 Apparatas and method for unified search of application in an electronic device

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5261102A (en) * 1991-03-28 1993-11-09 International Business Machines Corporation System for determining direct and indirect user access privileges to data base objects
US6014666A (en) * 1997-10-28 2000-01-11 Microsoft Corporation Declarative and programmatic access control of component-based server applications using roles
US6202066B1 (en) * 1997-11-19 2001-03-13 The United States Of America As Represented By The Secretary Of Commerce Implementation of role/group permission association using object access type
US6453353B1 (en) * 1998-07-10 2002-09-17 Entrust, Inc. Role-based navigation of information resources
US20030082155A1 (en) * 1999-12-06 2003-05-01 Habener Joel F. Stem cells of the islets of langerhans and their use in treating diabetes mellitus

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1998051029A1 (en) 1997-05-07 1998-11-12 Southwestern Bell Telephone Company Apparatus and method for customized secondary access authentication

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5261102A (en) * 1991-03-28 1993-11-09 International Business Machines Corporation System for determining direct and indirect user access privileges to data base objects
US6014666A (en) * 1997-10-28 2000-01-11 Microsoft Corporation Declarative and programmatic access control of component-based server applications using roles
US6202066B1 (en) * 1997-11-19 2001-03-13 The United States Of America As Represented By The Secretary Of Commerce Implementation of role/group permission association using object access type
US6453353B1 (en) * 1998-07-10 2002-09-17 Entrust, Inc. Role-based navigation of information resources
US20030082155A1 (en) * 1999-12-06 2003-05-01 Habener Joel F. Stem cells of the islets of langerhans and their use in treating diabetes mellitus

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9558341B1 (en) 2004-10-07 2017-01-31 Sprint Communications Company L.P. Integrated user profile administration tool
US20060179321A1 (en) * 2005-02-07 2006-08-10 Nigel Dawson Method and system of applying user permissions to an application program environment
US8554934B1 (en) * 2009-07-13 2013-10-08 Sprint Communications Company L.P. Application single sign on leveraging virtual local area network identifier
US8195819B1 (en) * 2009-07-13 2012-06-05 Sprint Communications Company L.P. Application single sign on leveraging virtual local area network identifier
US20110030051A1 (en) * 2009-07-29 2011-02-03 International Business Machines Corporation Autonomic manufacturing operator authorization adjustment
US9195954B2 (en) 2009-07-29 2015-11-24 International Business Machines Corporation Autonomic manufacturing operator authorization adjustment
US9489651B2 (en) 2009-07-29 2016-11-08 International Business Machines Corporation Autonomic manufacturing operator authorization adjustment
US8443429B1 (en) 2010-05-24 2013-05-14 Sprint Communications Company L.P. Integrated sign on
US9059987B1 (en) 2013-04-04 2015-06-16 Sprint Communications Company L.P. Methods and systems of using single sign-on for identification for a web server not integrated with an enterprise network

Also Published As

Publication number Publication date Type
US20040268125A1 (en) 2004-12-30 application
US7237119B2 (en) 2007-06-26 grant

Similar Documents

Publication Publication Date Title
US5132900A (en) Method and apparatus for limiting manipulation of documents within a multi-document relationship in a data processing system
US7673323B1 (en) System and method for maintaining security in a distributed computer network
US6289458B1 (en) Per property access control mechanism
US5911143A (en) Method and system for advanced role-based access control in distributed and centralized computer systems
US5446903A (en) Method and apparatus for controlling access to data elements in a data processing system based on status of an industrial process by mapping user's security categories and industrial process steps
US7155612B2 (en) Desktop database data administration tool with row level security
Tari et al. A role-based access control for intranet security
US20020073320A1 (en) Aggregated authenticated identity apparatus for and method therefor
US6928439B2 (en) Computer system with access control mechanism
US5263165A (en) System for providing user access control within a distributed data processing system having multiple resource managers
US20090178111A1 (en) System and method for maintaining security in a distributed computer network
US5283830A (en) Security mechanism for a computer system
Al-Kahtani et al. A model for attribute-based user-role assignment
US20030041198A1 (en) Authorization model for administration
US5263157A (en) Method and system for providing user access control within a distributed data processing system by the exchange of access control profiles
US20020023232A1 (en) Interactive key control system and method of managing access to secured locations
US5263158A (en) Method and system for variable authority level user access control in a distributed data processing system having multiple resource manager
US20050193221A1 (en) Information processing apparatus, information processing method, computer-readable medium having information processing program embodied therein, and resource management apparatus
Downs et al. Issues in discretionary access control
US7035910B1 (en) System and method for document isolation
US20090319529A1 (en) Information Rights Management
US20020128976A1 (en) Method and system for tracking software licenses and usage
Ferraiolo et al. A role-based access control model and reference implementation within a corporate intranet
US7206791B2 (en) System and method for managing and securing meta data
US20030115322A1 (en) System and method for analyzing security policies in a distributed computer network