Novell, Inc.

Calvin R Gaisford

Matthew G Brooks

Randall Richards Cook

Kelly Ervin Sonderegger

Bill Guy Bodine

Nicholas Huston Franklin

Damon V Janis

Carla M Heesch

Brady A Anderson

Todd F Millett

A system and method of providing associations between resources and actions in a network includes the steps of providing, in a database schema an action object class defining the structure and attributes of actions available in the network. During operation, action objects are created and stored in a database. When a user enters the system, an internal list is created at that user, identifying the resources available to that user and the action objects capable of being performed on those resources. When a user selects an resource object, the action objects associated with that resource object are displayed, the user selects the action, and the action is performed at the resource. In one example the selection of an action objects cause an associated application to be launched. Each action object represents a string of executable code. The executable code may either be hardcoded in the network software, such that action objects are created at network startup, or alternatively may be linked to the network via an external code module.

Apparatus and method for performing actions on object-oriented software objects in a directory services system

A system and method for managing user accounts in a distributed network that provides authentication to a client user account is provided. The system authenticates a user to a directory services database having a set of credential information, and a number of workstation objects and creates a user account on the client according to configuration information associated with one of the workstation objects. Depending on the configuration information, the system will create the user account with the same set of credential information as a user account in the directory services database, or, create the user account with credentials having an alternate username and random password. The system is operable to store client workstation configuration information, and to associate other networking objects in the directory services database with the workstation object.

System and method for managing user accounts in a communication network

An apparatus for distributing software implements directory services of a network to provide data for controlling a distribution of software. A software object may be any electronic representation of data of any type, from a single byte, to a complex application, or the like. A directory services computer, responsible for maintaining a data store of inter-related logical entities may store a distribution object containing all distribution information associated with a distribution. Distribution information may include a listing of targets, actual entities represented as logical entities in the data store, which are to receive a distribution of a software object. The directory services computer provides instantiations of various portions or an entire data store to be read by various nodes or computers throughout a network or internetwork. Accordingly, an individual computer, such as an individual client or workstation may read information in a distribution object, identified itself as a target of a distribution, and pull the designated software object, completing the distribution to itself. Distribution may also be effected by a workstation from a remote source node to a remote destination node. Authorizations, timing, targets, and software objects, may all be identified in a distribution object.

Directory-services-based software distribution apparatus and method

A directory services system includes a resource object, such as an application object for accessing a resource associated with the resource object. Attributes of the resource object contain licensing control information. The licensing attributes may be used by executables to control access by a user to properly licensed instances of a resource corresponding to the resource object. Also, a utility may be provided to manage the licensing attributes in the resource object. A licensing function may thus control a resource, via its resource object in the directory services database. Licensing maybe easily implemented by setting a new disabling attribute in the object.

Licensing controller using network directory services

A directory services system includes a resource object, such as an application object for accessing an actual resource associated with the resource object. Rights attributes of the resource object reflects information for controlling rights of a user (or entity) to access the actual resource. The rights attributes may include criteria for distribution. The rights attributes may be used to rapidly, dynamically, remotely, and easily define and control access to available instances of a resource object based on certain criteria, such as organization, membership, etc. A utility (snap-in) module may be relied upon to manage the values of the attribute. Application programming interfaces (executables) in a dynamically linked library may be provided to 'consume' (use) the attributes in the resource objects stored in directory services database.

Dynamic rights assignment apparatus and method using network directory

An apparatus and method for self-healing of software may rely on a distribution object in a directory services of a network to provide data for controlling distribution of software and installation of files associated therewith. A software object may represent a software product, system, data structure, application, or the like, from a single byte, to a complex program. A directory services system is responsible for maintaining a data store of inter-related logical entities (directory services objects), including software objects and a distribution object containing all distribution information associated with certain distribution processes. Maintenance methods may be programmed into a directory services object or some other executable to verify the existence of files required for particular software. Verification may be completed in association with a launch request, by explicit request, or in an ongoing maintenance procedure. Maintenance may include executables and data to control, complete, and record integrity of distributed files as a distinct activity or as an ongoing, routine, periodic process of verification and appropriate re-installation of files, operating transparently to a user.

Growing community of inventors

Provo, UT, United States of America

Calvin R Gaisford