US20030191846A1 - Access check system utilizing cached access permissions - Google Patents
Access check system utilizing cached access permissions Download PDFInfo
- Publication number
- US20030191846A1 US20030191846A1 US09/224,918 US22491899A US2003191846A1 US 20030191846 A1 US20030191846 A1 US 20030191846A1 US 22491899 A US22491899 A US 22491899A US 2003191846 A1 US2003191846 A1 US 2003191846A1
- Authority
- US
- United States
- Prior art keywords
- user
- access
- resource
- memory
- token
- 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
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting 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
Definitions
- the invention relates to the control of access by users to resources available on a server.
- the invention relates to a caching mechanism for more efficiently performing an access check in response to a current resource request that is similar to a previous request.
- a user requesting a resource on a server may be local to the server or may be communicating over a network with the server.
- a network includes local-area networks, intranet networks, and the internet as well as any other networked computing environment. Requesting users might log on to the server with a unique user name and password or they might be ‘anonymous’ to the server.
- Anonymous users typically have limited access to the server's resources. The occurrence of anonymous users is particularly prevalent in the case of networks such as the internet where any public user with internet access can access a given server.
- Access control lists are used to define the extent to which different users will be allowed access to different resources on a server.
- An access control list contains information which allows the operating system of a server to determine if a particular user has been granted access rights for a particular resource requested by the user.
- Each restricted resource has associated with it an access control list which lists the users granted access to the resource.
- access control lists might be associated with disks, with files, or with other storage volumes.
- an access control list for a given disk defines the access restrictions for all the resources or files stored on that disk.
- access by users is separately controlled for each file.
- the operating system When a request for a given file-object is received, the operating system identifies the requesting user, opens the requested file-object, reads the access control list to determine if the user has the necessary access rights, and then delivers the file-object to the requesting user if the user has the necessary access privileges. Therefore it is necessary to open a requested file-object to perform the access check each time a file is requested.
- the above described problems and others are solved and an advance in the art is achieved by the access check system of the present invention.
- the methods of the present invention provide an access-permission caching system for storing the last most recently generated access-permissions. If a request arrives at the server that is similar, in terms of the requesting user and the requested resource, to a previously processed request, then the system of the present invention locates the previously generated access-permission in the access-cache. The requesting user's access-permission is therefore determined without opening the requested resource to read the associated access control list. This capability is a significant savings of processing time when repetitive resource-requests arrive, such as internet requests for a file. An access check performed according to the methods of the present invention is easily made about 15% faster than an access check according to existing systems.
- a user When a user “logs-on” to an operating system, the user supplies a user-name and password. If the operating system recognizes the user then a unique user-token is generated by the system and the user-token is added to a user-token cache. At subsequent log-ons by the same user, the system returns the same user-token from the user-token cache. Then, if the user has requested a resource, the system checks the access-cache to see if the requested resource has already been accessed by the requesting user. If the requested resource has already been accessed by the requesting user then access to the resource is again provided by the system.
- the access-cache contains access-permissions. Each access-permission relates to a previously processed resource request and contains the name of the requested resource and the user-name of the user that requested the resource. In an embodiment of the present invention, the access-cache contains an access-permission for each instance of a resource that has been accessed. In a further embodiment of the present invention the access-cache contains an access-permission for only the most-recent instance that a resource has been accessed. If the access-cache does not contain an access-permission containing the appropriate user-token and file-name, then a full access check is performed as described above with respect to existing access check systems.
- the system If upon performing the full access check it is determined that the requesting user has permission to access the requested resource, the system combines the name of the requested resource with the user-token of the requesting user into an access-permission and stores the access-permission in the access-cache. When this resource is specified in subsequent requests by the same user, the system will locate the relevant matching access-permission in the access-cache and return the matching access-permission to the server thereby indicating a positive result for the access check. The server then makes available to the user the requested resource.
- the access-cache is scanned for all access-permissions containing the subject user-token and all occurrences are removed from the access cache.
- all access-permissions in the access-cache associated with the subject resource are removed from the access-cache.
- An area of significant advantage for the present invention is handling file requests from anonymous users.
- the vast majority of file-object requests are from anonymous users.
- all anonymous users share the same user-token and as a result the number of full, file-open access checks performed is dramatically reduced.
- the system of the present invention can also be configured to utilize filters to group together users having similar access privileges thereby reducing the number of file-open access checks. Operation of the system of the present invention reduces the frequency of the file-open operation thereby reducing the CPU time necessary to perform access checks. The operating system is therefore able to run more efficiently and quickly.
- FIG. 1 illustrates a network-computing environment in block diagram form.
- FIG. 2 depicts a user-token cache memory location according to the present invention.
- FIG. 3 depicts a file-object and associated access control list.
- FIG. 4 depicts an access-control list according to the present invention.
- FIGS. 5 - 6 illustrate access checking according to the present invention in flow diagram form.
- FIG. 1 illustrates a block diagram of server 100 connected over local bus 101 to network 102 .
- Network 102 may be a local-area network or any other network where multiple users are able to access resources on a single server, such as the internet.
- clients 1 -N Connected to network 102 are clients 1 -N.
- Client N represents any number of additional clients connected to the network.
- Server 100 communicates with other servers (not shown) and clients 1 -N using a standard communications protocol.
- Programd instructions for the access check system of the present invention are executable on processor 103 .
- Processor 103 stores and/or retrieves the programmed instructions and/or data from memory devices that include, but are not limited to, Random Access Memory (RAM) 104 and Read Only Memory (ROM) 105 by way of memory bus 106 .
- RAM Random Access Memory
- ROM Read Only Memory
- Another accessible memory device includes non-volatile memory device 107 by way of local bus 101 .
- Programmed instructions for implementing the access check system of the present invention are stored on non-volatile memory device 107 as part of system application 108 .
- file storage volume 109 Also stored on non-volatile memory 107 is file storage volume 109 containing various files as discussed below.
- the access check system of the present invention is operable in any of several standard computing operating systems readily available in the industry.
- a multiplicity of users may connect to server 100 through each of clients 1 -N.
- the process by which a user connects to server 100 is called “logging on”.
- the user supplies a user-name and a password to server 100 . If the user-name and password supplied by the user are recognized by server 100 then the user is allowed to log on, or connect, to server 100 .
- logging on to the server only allows a user to then request access to a resource on the server. Checking whether a user has access-permission to a particular resource, and providing access to the resource, is the subject of the remaining discussion.
- the system of the present invention assigns a unique user-token to the user and stores the user-token in user-token cache 200 .
- User-token cache 200 stored on RAM 104 of server 100 or on another suitable storage device, is comprised of entries 201 - 203 . There is an entry 201 - 203 for each user that has logged on to server 100 .
- Each entry 201 - 203 in user-token cache 200 is comprised of a user-name 204 , a user-token 205 and a user-password 206 .
- server 100 assigns a unique user-token, Token 1 , to User 1 and stores User 1 's user-name, user-password, and user-token as entry 201 in user-token cache 200 .
- the system of the present invention retrieves User 1 's user-token from user-token cache 200 so that User 1 will be assigned the same user-token each time User 1 logs on to server 100 .
- server 100 assigns the user-name “Anonymous” to the user.
- each anonymous user one not supplying a username and password upon logging on, is assigned the same user-token by the system of the present invention.
- anonymous users are assigned user-token Token 3 .
- Entry 203 is the entry for user Anonymous in user-token cache 200 .
- User-tokens 205 are represented in textual form to simplify the description of the present invention.
- each user-token is a unique 32 bit value assigned by the system of the present invention.
- control of access to server 100 's resources is at the file level.
- ACL Access Control List
- Non-volatile memory 107 contains file-storage volume 109 .
- File-storage volume 109 contains a number of file-objects 300 - 302 of which file-object 300 of FIG. 3 is exemplary.
- File-objects 301 - 302 discussed with respect to FIG. 4 along with file-object 300 , are not shown in the figures but are of the same format as described below with respect to file-object 300 .
- File-object 300 is comprised of ACL 301 and file 302 .
- File 302 is the actual, substantive content of file-object 300 .
- ACL 301 defines the extent to which various users can access and manipulate file 302 .
- ACL 301 of file-object 300 contains Access Control Entries (ACE) 305 - 307 .
- Each ACE 305 - 307 is comprised of a user-token field 303 and a permitted-access field 304 .
- ACE 305 defines the permitted access to file 302 by the user having user-token token 1 .
- the permitted access 304 for Token 1 is “Full Control” meaning user 1 can manipulate file 302 in any way possible through the operation of server 100 .
- Token 2 has “read/write” permission for file-object 300 .
- Users logged in as Anonymous and assigned Token 3 as a user-token are permitted only read access according to ACE 307 of access control list 301 .
- ACE 307 of access control list 301 Although only three ACE's are depicted in access control list 301 of FIG. 3, those skilled in the art will recognize that any number of ACE's could be added to access control list 301 as necessary for the needs of server 100 .
- file-object 300 depicts access control at the file level of server 100
- server 100 an access control list could be associated with non-volatile memory 107 so that access to all resources on non-volatile memory 107 would be defined by a single access control list.
- Another example would be an access control list associated with file-storage volume 109 whereby access to all the files stored in file-storage volume 109 would be defined by a single access control list.
- access control list's at different levels within the same server 100 so, for example, there could be an access control list associated with non-volatile memory 107 and separate access control list's associated with some or all of the file-objects stored on non-volatile memory 107 .
- Access-cache 400 of FIG. 4 is comprised of access-permissions 403 - 407 each of which is comprised of a filename field 401 and a user-token field 402 .
- Each access-permission 403 - 407 indicates that a user, identified by the user-token in user-token field 402 , has permission to access, and has accessed, the file identified in the corresponding file-name field 401 .
- server 100 performs an access check for a user-token/file name combination not already existing as an access-permission in access-cache 400 for which access is permitted, server 100 enters a new access-permission in access cache 400 .
- access-cache 400 only contains an access-permission for the most recent instance of a file having been accessed.
- FIG. 4 indicates two access permissions 403 and 405 for file name 300 . If access-permission 403 is the more recent of the two then it would have overwritten access-permission 405 and there would be only a single access-permission for file 300 in access-cache 400 .
- This approach is simpler to implement than the embodiment creating an access-permission each time a new user-token accesses a given file. The same advantages are achieved, however, especially when there are few users or a common user such as the anonymous user of the internet example.
- server 100 when a user requests access to a file-object on non-volatile memory 107 , server 100 first checks access-cache 400 to determine if there is an access-permission 401 that matches both the user-token for the requesting user and the requested file. If there is a matching access-permission in access-cache 400 , the existence of which indicates that the necessary access check has already been performed, access to the requested file is granted. If there is no matching access-permission in access-cache 400 , server 100 performs a full access check by opening the requested file and reading the access control list associated with the requested file. If, as a result of the access check, access is permitted, then a corresponding access-permission is appended to access-cache 400 .
- User 1 requests file-object 300 by supplying a user-name and a password to server 100 over network 102 .
- the user-name and password supplied by User 1 are recognized by server 100 and User 1 is therefore allowed to log on to Server 100 .
- Server 100 first checks user-token cache 200 of FIG. 2 for a user-token matching User 1 's user-name and password. Entry 201 of user-token cache 200 matches User 1 's user-name and therefore server 100 retrieves Token 1 from user-token cache 200 to use as the user-token for User 1 .
- User 1 requests to read file 300 .
- Server 100 checks access-cache 400 for an access-permission matching the current request.
- Access-permission 403 relates to file-object 300 but the user-token for access-permission 403 doesn't match User 1 's user-token.
- Access-permission 405 is comprised of a file-name field containing the name of the requested file and a user-token field containing User 1 's user-token. Access-permission 405 is therefore returned by the system to server 100 signifying that User 1 has been granted permission to read file-object 300 . Server 100 then allows access to file 300 by User 1 .
- a further example of the general operation of the methods of the present invention is described with respect to User 2 requesting to read file-object 300 .
- User 2 as one of clients 1 -N, attempts to log onto server 100 by supplying a user-name and a password to server 100 over network 102 .
- the user-name and password supplied by User 2 are recognized by Server 100 and User 2 is therefore allowed to log on to Server 100 .
- Server 100 first checks user-token cache 200 of FIG. 2 for a user-token matching User 2 's user-name. Entry 202 of user-token cache 200 matches User 2 's user-name and therefore server 100 retrieves Token 2 from user-token cache 200 as the user-token for User 2 .
- User 2 now logged on to server 100 , places a request to read file-object 300 .
- Server 100 checks access-cache 400 for an access-permission matching the current request.
- Access-permissions 403 and 405 each have file-object 300 in the file-name field 401 but neither access-permission 403 or 405 have a user-token field 402 that matches User 2 's user-token. This means that User 2 has not previously read file 300 and the system must perform a full, file open, access check.
- file-object 300 is opened and access control list 301 is read to determine the access-permission granted to User 2 .
- ACE 306 defines User 2 's granted access to file-object 300 .
- Permitted-access field 304 of ACE 306 indicates that User 2 has read/write permission for file 300 . Access for reading file-object 300 is therefore provided to User 2 . Once the file-open access check is completed, an appropriate access-permission (not shown) is added to access-cache 400 so that a file-open access check will not need to be performed the next time User 2 requests file-object 300 .
- access-permissions are only generated and utilized with respect to Read access requests.
- access-cache 400 also includes information about the level of access associated with a previous resource request. In this embodiment, if a user having a certain user-token has previously read a certain file but is currently asking to write the file, a new access-permission reflecting the write permission is generated, if appropriate, and added to the access-cache.
- Access Check System Security Maintenance—FIGS. 2 - 4
- the methods of the present invention operate to ensure that access-cache 400 is updated so that unintended security holes are avoided. Likewise, if user-token cache 200 is modified, the methods of the present invention operate to ensure that access-cache 400 is updated appropriately.
- the system of the present invention flushes all access-permissions in access-cache 400 containing the file name of the modified file-object. This means that on the next request for the file-object, the system will be required to perform a full access check by opening the requested file-object to read the associated access control list thereby ensuring that any changes made to the access control list are not over-looked. Maintaining the security of the system in such a way is necessary or access-cache 400 could effectively circumvent any changes made to the access control lists.
- access-cache 400 is flushed of all occurrences of the file name of the modified file-object only when it is the access control list of the file-object that has been modified. Otherwise, if changes have been made to the file-object that do not effect the access control list then the corresponding entries in access-cache 400 are left untouched.
- a user's access to the resources of server 100 is modified or eliminated, then the corresponding entry in the user-token cache is removed.
- the system of the present invention flushes all access-permissions in access-cache 400 containing the removed user-token. This eliminates the possibility of access-cache 400 allowing access to resources even after a user's access to server 100 has been modified or eliminated.
- An advantage of the present invention for access checks is the elimination of the need to open access control lists each time a resource request is processed if a similar request has already been processed.
- a way to maximize this advantage is to group or cluster users to reduce the number of different user-tokens. For example, a number of users within the same work-group might all be granted the same level of access to the files on server 100 .
- a filter can be applied by the system of the present invention so that when a member of the group logs on to server 100 , they are assigned the user-token designated for that group rather than a user-token unique to the individual user. In this fashion, fewer user-tokens are generated and therefore fewer access checks requiring the reading of access control lists are performed.
- a variation of this advantage is to operate the system of the present invention so that a group or class of users log on to server 100 using the same user-name and password and as a result are assigned the same user-token upon logging on.
- user-name “Anonymous” is assigned to user's placing requests over the internet for resources on server 100 . All such users are assigned the same user-token, Token 3 in the example of FIGS. 2 - 4 , and the number of access checks performed by server 100 is significantly reduced.
- Another example is a server that maps each user that logs on to one of several different user names. Each user name to which a logged-on user is mapped might correspond to a workgroup, a level of security access, or any other grouping deemed appropriate by the system administrator.
- FIGS. 5 - 6 depict the operation of the methods of the present invention in greater detail.
- FIG. 5 depicts the operation of the access-cache system while FIG. 6 depicts the operational steps of the security maintenance features of the present invention.
- Step 500 represents the process of a user logging on to server 100 .
- a user optionally supplies a user-name and a password and is allowed to log on to server 100 if server 100 recognizes the user-name and password.
- processing continues to decision block 502 .
- Decision block 502 operates to determine if the user-name of the user exists in an entry in user-token cache 200 . If the relevant user-name exists in user-token cache 200 then processing continues to step 504 , otherwise processing continues to step 508 . Step 504 operates to retrieve from user-token cache 200 the user-token associated with the relevant user-name. All file requests by the user are then identified by server 100 with the user-token retrieved from user-token cache 200 .
- Step 508 operates to generate a unique user-token for the user if, in decision block 502 , it was determined that a user-token had not yet been assigned to the user.
- step 510 the generated user-token is appended to user-token cache 200 so that the next time the user logs on to server 100 , the assigned user-token will be available in user-token cache 200 .
- decision block 506 processing continues with decision block 506 .
- Decision block 506 operates to determine if access-cache 400 contains an access-permission that matches the request made by the user. As noted above, a matching access-permission is one that contains the relevant user-token and the requested file-name. If a matching access-permission is identified in access-cache 400 then processing continues to step 512 otherwise processing continues to step 516 .
- Step 512 operates to retrieve the matching access-permission from access-cache 400 .
- Server 100 then, in step 514 , provides access to the requested file as requested by the user.
- step 516 since a matching access-permission was not found in access-cache 400 , a full access check is begun by opening the requested file-object and reading the associated access control list. Processing then continues to decision block 518 .
- Decision block 518 operates to determine if the access control list of the requested file-object permits the access requested by the user. If the user is permitted the requested access according to the access control list then processing continues with step 520 otherwise processing continues to step 522 . During step 520 , a new access-permission is generated for the current user and requested file and the new access-permission is appended to the contents of access-cache 400 . Processing then continues to step 514 where the user is provided access to the requested file.
- step 522 If, in decision block 18 , it is determined that the user does not have the requested access-permission, then processing continues to step 522 .
- step 522 an error message is generated and communicated to the user to notify the user of the negative result of the access check.
- Decision block 524 operates to determine if there are additional file requests by the user that have not been processed. For example, in the case of server 100 operating as an internet server, it often receives multiple file requests at once from a single user. Each of these file requests is processed in the same fashion as described above. If the operation of decision block 524 determines that there are further file requests by the same user to be processed then processing returns to decision block 506 otherwise processing continues to step 526 where processing of the user's file requests is concluded.
- processing steps 600 - 606 depicted in FIG. 6 are repeated on a regular, periodic basis to ensure the security of the resources of server 100 .
- Decision block 600 operates to determine if a file-object has been modified. If a file-object has been modified, processing continues to step 602 otherwise processing continues to step 604 .
- step 602 access-cache 400 is flushed of all access-permissions containing the file-name of the modified file. This operation ensures that any changes to a file's access control list will not be over-looked as a result of the operation of the access check system of the present invention. Processing then continues to decision block 604 .
- Decision block 604 operates to determine if a user-token has been deleted from the user-token cache. If a user's level of access to server 100 is modified or eliminated, the user-token associated with the user is removed from the user-token cache by the operation of server 100 . This occurrence is identified by the operation of decision block 604 and processing accordingly proceeds to step 606 . In step 606 , access-cache 400 is flushed of all access-permissions containing the deleted user-token. Processing then continues to decision block 600 where the security steps of 600 - 606 are again initiated.
- Steps 600 - 606 ensure that the speed and efficiency advantages of the access check system of the present invention do not result in security holes.
- the increased speed of the present invention is thereby implemented only when, from a security standpoint, it is safe to do so.
- the access check system of the present invention includes a method and apparatus for efficiently accomplishing access checks for requested resources rather than performing a full, file-open, access check each time a user requests a resource.
Abstract
An access-check system for a network server comprises an access-cache for storing access-permissions generated by the server in response to resource access requests. The system retrieves the appropriate access-permission from the access-cache in response to receipt of a request necessitating the same access-permission as already generated for an earlier processed request. A user-token cache is also employed to assign a unique user-token, to be used in the access-cache, to each user logged on to the server. Changes made to the user-token cache are reflected in the access-cache by removing from the access-cache those entries containing the changed user-token. Changes made to an access control list are reflected in the access-cache by removing from the access-cache those entries containing the server resource with which the changed access control list is associated.
Description
- This is a continuation of application Ser. No. 08/689,838, filed Aug. 14, 1996, which is hereby incorporated by reference.
- The invention relates to the control of access by users to resources available on a server. In particular, the invention relates to a caching mechanism for more efficiently performing an access check in response to a current resource request that is similar to a previous request.
- In a computer network it is often desirable to control access by users to resources available on the network. A user requesting a resource on a server may be local to the server or may be communicating over a network with the server. A network includes local-area networks, intranet networks, and the internet as well as any other networked computing environment. Requesting users might log on to the server with a unique user name and password or they might be ‘anonymous’ to the server.
- Anonymous users typically have limited access to the server's resources. The occurrence of anonymous users is particularly prevalent in the case of networks such as the internet where any public user with internet access can access a given server.
- Access control lists are used to define the extent to which different users will be allowed access to different resources on a server. An access control list contains information which allows the operating system of a server to determine if a particular user has been granted access rights for a particular resource requested by the user. Each restricted resource has associated with it an access control list which lists the users granted access to the resource. Depending on the level of access control implemented on a given server, access control lists might be associated with disks, with files, or with other storage volumes. In an operating system where access control lists are associated with disks, an access control list for a given disk defines the access restrictions for all the resources or files stored on that disk. In an operating system where access control lists are associated with files, access by users is separately controlled for each file.
- The flexibility and system performance offered by file-level access control is significant. However, the number of access checks performed by such a system is increased dramatically as compared to a system where access control is maintained only at the disk level. As with all operations of an operating system, performing an access check in response to a user request for a resource requires processing time of the central processing unit (“CPU time”). When a server is handling a large number of file requests a significant amount of CPU time can be consumed by performing the necessary access checks. In a system employing file-level access control lists, the access control list is part of each individual file-object. When a request for a given file-object is received, the operating system identifies the requesting user, opens the requested file-object, reads the access control list to determine if the user has the necessary access rights, and then delivers the file-object to the requesting user if the user has the necessary access privileges. Therefore it is necessary to open a requested file-object to perform the access check each time a file is requested.
- The file-open operation consumes a great deal of CPU time. In a server receiving frequent file requests, the need to open every requested file-object to check the access control list is very expensive in terms of CPU time.
- There exists a need for an access check system that is more efficient in its use of CPU time. Specifically, there exists a need for an access check system that performs the necessary access check, even at the file-level of access control, without the relatively slow operation of opening the requested file-object to check the associated access control list.
- The above described problems and others are solved and an advance in the art is achieved by the access check system of the present invention. The methods of the present invention provide an access-permission caching system for storing the last most recently generated access-permissions. If a request arrives at the server that is similar, in terms of the requesting user and the requested resource, to a previously processed request, then the system of the present invention locates the previously generated access-permission in the access-cache. The requesting user's access-permission is therefore determined without opening the requested resource to read the associated access control list. This capability is a significant savings of processing time when repetitive resource-requests arrive, such as internet requests for a file. An access check performed according to the methods of the present invention is easily made about 15% faster than an access check according to existing systems.
- When a user “logs-on” to an operating system, the user supplies a user-name and password. If the operating system recognizes the user then a unique user-token is generated by the system and the user-token is added to a user-token cache. At subsequent log-ons by the same user, the system returns the same user-token from the user-token cache. Then, if the user has requested a resource, the system checks the access-cache to see if the requested resource has already been accessed by the requesting user. If the requested resource has already been accessed by the requesting user then access to the resource is again provided by the system.
- The access-cache contains access-permissions. Each access-permission relates to a previously processed resource request and contains the name of the requested resource and the user-name of the user that requested the resource. In an embodiment of the present invention, the access-cache contains an access-permission for each instance of a resource that has been accessed. In a further embodiment of the present invention the access-cache contains an access-permission for only the most-recent instance that a resource has been accessed. If the access-cache does not contain an access-permission containing the appropriate user-token and file-name, then a full access check is performed as described above with respect to existing access check systems. If upon performing the full access check it is determined that the requesting user has permission to access the requested resource, the system combines the name of the requested resource with the user-token of the requesting user into an access-permission and stores the access-permission in the access-cache. When this resource is specified in subsequent requests by the same user, the system will locate the relevant matching access-permission in the access-cache and return the matching access-permission to the server thereby indicating a positive result for the access check. The server then makes available to the user the requested resource.
- When a user-token is removed from the user-token cache, the access-cache is scanned for all access-permissions containing the subject user-token and all occurrences are removed from the access cache. When a resource is changed, all access-permissions in the access-cache associated with the subject resource are removed from the access-cache.
- An area of significant advantage for the present invention is handling file requests from anonymous users. In an internet server application, for example, the vast majority of file-object requests are from anonymous users. According to the present invention, all anonymous users share the same user-token and as a result the number of full, file-open access checks performed is dramatically reduced. The system of the present invention can also be configured to utilize filters to group together users having similar access privileges thereby reducing the number of file-open access checks. Operation of the system of the present invention reduces the frequency of the file-open operation thereby reducing the CPU time necessary to perform access checks. The operating system is therefore able to run more efficiently and quickly.
- FIG. 1 illustrates a network-computing environment in block diagram form.
- FIG. 2 depicts a user-token cache memory location according to the present invention.
- FIG. 3 depicts a file-object and associated access control list.
- FIG. 4 depicts an access-control list according to the present invention.
- FIGS.5-6 illustrate access checking according to the present invention in flow diagram form.
- General Network Computing Environment—FIG. 1
- FIG. 1 illustrates a block diagram of
server 100 connected overlocal bus 101 tonetwork 102.Network 102 may be a local-area network or any other network where multiple users are able to access resources on a single server, such as the internet. Connected to network 102 are clients 1-N. Client N represents any number of additional clients connected to the network.Server 100 communicates with other servers (not shown) and clients 1-N using a standard communications protocol. Programmed instructions for the access check system of the present invention are executable onprocessor 103.Processor 103 stores and/or retrieves the programmed instructions and/or data from memory devices that include, but are not limited to, Random Access Memory (RAM) 104 and Read Only Memory (ROM) 105 by way ofmemory bus 106. Another accessible memory device includesnon-volatile memory device 107 by way oflocal bus 101. Programmed instructions for implementing the access check system of the present invention are stored onnon-volatile memory device 107 as part ofsystem application 108. Also stored onnon-volatile memory 107 isfile storage volume 109 containing various files as discussed below. The access check system of the present invention is operable in any of several standard computing operating systems readily available in the industry. - Assignment of User-Tokens—FIG. 2
- A multiplicity of users (not shown) may connect to
server 100 through each of clients 1-N. The process by which a user connects toserver 100 is called “logging on”. When a user logs on toserver 100, the user supplies a user-name and a password toserver 100. If the user-name and password supplied by the user are recognized byserver 100 then the user is allowed to log on, or connect, toserver 100. In a system where access-permission is required for a user to access resources on a server, such as is the subject of the present invention, logging on to the server only allows a user to then request access to a resource on the server. Checking whether a user has access-permission to a particular resource, and providing access to the resource, is the subject of the remaining discussion. - If a user logs on to
server 100 for the first time, the system of the present invention assigns a unique user-token to the user and stores the user-token in user-token cache 200. User-token cache 200, stored onRAM 104 ofserver 100 or on another suitable storage device, is comprised of entries 201-203. There is an entry 201-203 for each user that has logged on toserver 100. Each entry 201-203 in user-token cache 200 is comprised of a user-name 204, a user-token 205 and a user-password 206. - For example, when
User 1 first logs on toserver 100,server 100 assigns a unique user-token, Token1, toUser 1 andstores User 1's user-name, user-password, and user-token asentry 201 in user-token cache 200. WhenUser 1 subsequently logs on toserver 100, the system of the present invention retrievesUser 1's user-token from user-token cache 200 so thatUser 1 will be assigned the same user-token eachtime User 1 logs on toserver 100. - In a network such as the internet, a large portion of the users logging on to
server 100 do so as an ‘anonymous’ user. Administrators and certain other users may have unique user names and passwords but the bulk of the users logging on are doing so to access resources made available to anonymous users onserver 100. If no user-name and password is supplied by a user,server 100 assigns the user-name “Anonymous” to the user. As a result, each anonymous user, one not supplying a username and password upon logging on, is assigned the same user-token by the system of the present invention. In the example of FIG. 2, and the following figures, anonymous users are assigned user-token Token3.Entry 203 is the entry for user Anonymous in user-token cache 200. - User-
tokens 205 are represented in textual form to simplify the description of the present invention. In a preferred embodiment of the present invention, each user-token is a unique 32 bit value assigned by the system of the present invention. - Access-Control Lists—FIG. 3
- In a preferred embodiment of the present invention the control of access to
server 100's resources is at the file level. This means that each file-object stored onserver 100 has associated with it a definition, called an Access Control List (ACL), of which users have what access rights with respect to the particular file-object. -
Non-volatile memory 107 contains file-storage volume 109. File-storage volume 109 contains a number of file-objects 300-302 of which file-object 300 of FIG. 3 is exemplary. File-objects 301-302, discussed with respect to FIG. 4 along with file-object 300, are not shown in the figures but are of the same format as described below with respect to file-object 300. - File-
object 300 is comprised ofACL 301 and file 302.File 302 is the actual, substantive content of file-object 300.ACL 301 defines the extent to which various users can access and manipulatefile 302.ACL 301 of file-object 300 contains Access Control Entries (ACE) 305-307. Each ACE 305-307 is comprised of a user-token field 303 and a permitted-access field 304.ACE 305 defines the permitted access to file 302 by the user having user-token token1. The permittedaccess 304 for Token1 is “Full Control” meaninguser 1 can manipulate file 302 in any way possible through the operation ofserver 100. Likewise, the user to which Token2 is assigned as a user-token has “read/write” permission for file-object 300. Users logged in as Anonymous and assigned Token3 as a user-token are permitted only read access according toACE 307 ofaccess control list 301. Although only three ACE's are depicted inaccess control list 301 of FIG. 3, those skilled in the art will recognize that any number of ACE's could be added toaccess control list 301 as necessary for the needs ofserver 100. - Although the example of file-
object 300 depicts access control at the file level ofserver 100, those skilled in the art will readily recognize that the methods of the present invention readily apply to systems having different levels of access control. For example, inserver 100 an access control list could be associated withnon-volatile memory 107 so that access to all resources onnon-volatile memory 107 would be defined by a single access control list. Another example would be an access control list associated with file-storage volume 109 whereby access to all the files stored in file-storage volume 109 would be defined by a single access control list. It is also within the scope of the present invention to utilize access control list's at different levels within thesame server 100 so, for example, there could be an access control list associated withnon-volatile memory 107 and separate access control list's associated with some or all of the file-objects stored onnon-volatile memory 107. - Access-Cache—FIG. 4
- Access-
cache 400 of FIG. 4 is comprised of access-permissions 403-407 each of which is comprised of afilename field 401 and a user-token field 402. Each access-permission 403-407 indicates that a user, identified by the user-token in user-token field 402, has permission to access, and has accessed, the file identified in the corresponding file-name field 401. Eachtime server 100 performs an access check for a user-token/file name combination not already existing as an access-permission in access-cache 400 for which access is permitted,server 100 enters a new access-permission inaccess cache 400. - In a further embodiment of the present invention, access-
cache 400 only contains an access-permission for the most recent instance of a file having been accessed. - For example, FIG. 4 indicates two
access permissions file name 300. If access-permission 403 is the more recent of the two then it would have overwritten access-permission 405 and there would be only a single access-permission forfile 300 in access-cache 400. This approach is simpler to implement than the embodiment creating an access-permission each time a new user-token accesses a given file. The same advantages are achieved, however, especially when there are few users or a common user such as the anonymous user of the internet example. - Access Check System: General Operation—FIGS.1-4
- In general, when a user requests access to a file-object on
non-volatile memory 107,server 100 first checks access-cache 400 to determine if there is an access-permission 401 that matches both the user-token for the requesting user and the requested file. If there is a matching access-permission in access-cache 400, the existence of which indicates that the necessary access check has already been performed, access to the requested file is granted. If there is no matching access-permission in access-cache 400,server 100 performs a full access check by opening the requested file and reading the access control list associated with the requested file. If, as a result of the access check, access is permitted, then a corresponding access-permission is appended to access-cache 400. - An example of
User 1 requesting file-object 300 is described with respect to FIGS. 1-4.User 1, as one of clients 1-N, attempts to log on toserver 100 by supplying a user-name and a password toserver 100 overnetwork 102. The user-name and password supplied byUser 1 are recognized byserver 100 andUser 1 is therefore allowed to log on toServer 100.Server 100 first checks user-token cache 200 of FIG. 2 for a user-token matching User 1's user-name and password.Entry 201 of user-token cache 200matches User 1's user-name and thereforeserver 100 retrieves Token1 from user-token cache 200 to use as the user-token forUser 1. -
User 1 requests to readfile 300.Server 100 checks access-cache 400 for an access-permission matching the current request. Access-permission 403 relates to file-object 300 but the user-token for access-permission 403 doesn't matchUser 1's user-token. Access-permission 405 is comprised of a file-name field containing the name of the requested file and a user-tokenfield containing User 1's user-token. Access-permission 405 is therefore returned by the system toserver 100 signifying thatUser 1 has been granted permission to read file-object 300.Server 100 then allows access to file 300 byUser 1. - A further example of the general operation of the methods of the present invention is described with respect to
User 2 requesting to read file-object 300.User 2, as one of clients 1-N, attempts to log ontoserver 100 by supplying a user-name and a password toserver 100 overnetwork 102. The user-name and password supplied byUser 2 are recognized byServer 100 andUser 2 is therefore allowed to log on toServer 100.Server 100 first checks user-token cache 200 of FIG. 2 for a user-token matching User 2's user-name.Entry 202 of user-token cache 200matches User 2's user-name and thereforeserver 100 retrieves Token2 from user-token cache 200 as the user-token forUser 2. -
User 2, now logged on toserver 100, places a request to read file-object 300.Server 100 checks access-cache 400 for an access-permission matching the current request. Access-permissions object 300 in the file-name field 401 but neither access-permission token field 402 that matchesUser 2's user-token. This means thatUser 2 has not previously readfile 300 and the system must perform a full, file open, access check. Referring to FIG. 3, file-object 300 is opened andaccess control list 301 is read to determine the access-permission granted toUser 2.ACE 306 definesUser 2's granted access to file-object 300. Permitted-access field 304 ofACE 306 indicates thatUser 2 has read/write permission forfile 300. Access for reading file-object 300 is therefore provided toUser 2. Once the file-open access check is completed, an appropriate access-permission (not shown) is added to access-cache 400 so that a file-open access check will not need to be performed thenext time User 2 requests file-object 300. - In the above examples of an embodiment of the present invention, access-permissions are only generated and utilized with respect to Read access requests. In a further embodiment of the present invention, access-
cache 400 also includes information about the level of access associated with a previous resource request. In this embodiment, if a user having a certain user-token has previously read a certain file but is currently asking to write the file, a new access-permission reflecting the write permission is generated, if appropriate, and added to the access-cache. - Access Check System: Security Maintenance—FIGS.2-4
- When changes are made to a file-object, the methods of the present invention operate to ensure that access-
cache 400 is updated so that unintended security holes are avoided. Likewise, if user-token cache 200 is modified, the methods of the present invention operate to ensure that access-cache 400 is updated appropriately. - When a file-object is modified, the system of the present invention flushes all access-permissions in access-
cache 400 containing the file name of the modified file-object. This means that on the next request for the file-object, the system will be required to perform a full access check by opening the requested file-object to read the associated access control list thereby ensuring that any changes made to the access control list are not over-looked. Maintaining the security of the system in such a way is necessary or access-cache 400 could effectively circumvent any changes made to the access control lists. - In a further embodiment of the present invention, access-
cache 400 is flushed of all occurrences of the file name of the modified file-object only when it is the access control list of the file-object that has been modified. Otherwise, if changes have been made to the file-object that do not effect the access control list then the corresponding entries in access-cache 400 are left untouched. - If a user's access to the resources of
server 100 is modified or eliminated, then the corresponding entry in the user-token cache is removed. When a user-token is removed from user-token cache 200, the system of the present invention flushes all access-permissions in access-cache 400 containing the removed user-token. This eliminates the possibility of access-cache 400 allowing access to resources even after a user's access toserver 100 has been modified or eliminated. - Access Check System: Efficiency Optimization—FIGS.2-4
- An advantage of the present invention for access checks is the elimination of the need to open access control lists each time a resource request is processed if a similar request has already been processed. A way to maximize this advantage is to group or cluster users to reduce the number of different user-tokens. For example, a number of users within the same work-group might all be granted the same level of access to the files on
server 100. A filter can be applied by the system of the present invention so that when a member of the group logs on toserver 100, they are assigned the user-token designated for that group rather than a user-token unique to the individual user. In this fashion, fewer user-tokens are generated and therefore fewer access checks requiring the reading of access control lists are performed. - A variation of this advantage is to operate the system of the present invention so that a group or class of users log on to
server 100 using the same user-name and password and as a result are assigned the same user-token upon logging on. For example, user-name “Anonymous” is assigned to user's placing requests over the internet for resources onserver 100. All such users are assigned the same user-token, Token3 in the example of FIGS. 2-4, and the number of access checks performed byserver 100 is significantly reduced. Another example is a server that maps each user that logs on to one of several different user names. Each user name to which a logged-on user is mapped might correspond to a workgroup, a level of security access, or any other grouping deemed appropriate by the system administrator. - Access Check System: Detailed Operation—FIG. 5
- The flow-charts of FIGS.5-6 depict the operation of the methods of the present invention in greater detail. FIG. 5 depicts the operation of the access-cache system while FIG. 6 depicts the operational steps of the security maintenance features of the present invention.
-
Step 500 represents the process of a user logging on toserver 100. As described above with respect to FIG. 2, a user optionally supplies a user-name and a password and is allowed to log on toserver 100 ifserver 100 recognizes the user-name and password. Once a user has logged on, processing continues todecision block 502. -
Decision block 502 operates to determine if the user-name of the user exists in an entry in user-token cache 200. If the relevant user-name exists in user-token cache 200 then processing continues to step 504, otherwise processing continues to step 508. Step 504 operates to retrieve from user-token cache 200 the user-token associated with the relevant user-name. All file requests by the user are then identified byserver 100 with the user-token retrieved from user-token cache 200. -
Step 508 operates to generate a unique user-token for the user if, indecision block 502, it was determined that a user-token had not yet been assigned to the user. - Then, in
step 510, the generated user-token is appended to user-token cache 200 so that the next time the user logs on toserver 100, the assigned user-token will be available in user-token cache 200. After bothstep 504 and step 510 processing continues withdecision block 506. -
Decision block 506 operates to determine if access-cache 400 contains an access-permission that matches the request made by the user. As noted above, a matching access-permission is one that contains the relevant user-token and the requested file-name. If a matching access-permission is identified in access-cache 400 then processing continues to step 512 otherwise processing continues to step 516. -
Step 512 operates to retrieve the matching access-permission from access-cache 400.Server 100 then, instep 514, provides access to the requested file as requested by the user. Instep 516, since a matching access-permission was not found in access-cache 400, a full access check is begun by opening the requested file-object and reading the associated access control list. Processing then continues todecision block 518. -
Decision block 518 operates to determine if the access control list of the requested file-object permits the access requested by the user. If the user is permitted the requested access according to the access control list then processing continues withstep 520 otherwise processing continues to step 522. Duringstep 520, a new access-permission is generated for the current user and requested file and the new access-permission is appended to the contents of access-cache 400. Processing then continues to step 514 where the user is provided access to the requested file. - If, in decision block18, it is determined that the user does not have the requested access-permission, then processing continues to step 522. In
step 522 an error message is generated and communicated to the user to notify the user of the negative result of the access check. After a file request has been processed, either concluding with providing the requested access as instep 514 or by notifying the user of the user's lack of access as instep 522, processing continues to step 524. -
Decision block 524 operates to determine if there are additional file requests by the user that have not been processed. For example, in the case ofserver 100 operating as an internet server, it often receives multiple file requests at once from a single user. Each of these file requests is processed in the same fashion as described above. If the operation ofdecision block 524 determines that there are further file requests by the same user to be processed then processing returns to decision block 506 otherwise processing continues to step 526 where processing of the user's file requests is concluded. - Access Check System: Detailed Operation—FIG. 6
- The processing steps600-606 depicted in FIG. 6 are repeated on a regular, periodic basis to ensure the security of the resources of
server 100.Decision block 600 operates to determine if a file-object has been modified. If a file-object has been modified, processing continues to step 602 otherwise processing continues to step 604. - In
step 602, access-cache 400 is flushed of all access-permissions containing the file-name of the modified file. This operation ensures that any changes to a file's access control list will not be over-looked as a result of the operation of the access check system of the present invention. Processing then continues to decision block 604. - Decision block604 operates to determine if a user-token has been deleted from the user-token cache. If a user's level of access to
server 100 is modified or eliminated, the user-token associated with the user is removed from the user-token cache by the operation ofserver 100. This occurrence is identified by the operation of decision block 604 and processing accordingly proceeds to step 606. Instep 606, access-cache 400 is flushed of all access-permissions containing the deleted user-token. Processing then continues to decision block 600 where the security steps of 600-606 are again initiated. - Steps600-606 ensure that the speed and efficiency advantages of the access check system of the present invention do not result in security holes. The increased speed of the present invention is thereby implemented only when, from a security standpoint, it is safe to do so.
- The access check system of the present invention includes a method and apparatus for efficiently accomplishing access checks for requested resources rather than performing a full, file-open, access check each time a user requests a resource. Although specific embodiments are disclosed herein, it is expected that persons skilled in the art can and will design alternative header generation systems that are within the scope of the following claims either literally or under the Doctrine of Equivalents.
Claims (28)
1. A computer-readable medium having computer-executable instructions for providing access to a computer network by performing steps comprising:
receiving a request from a user to access a resource on the computer network;
checking a first memory to determine if the user may access the resource;
providing the user with access to the resource if the first memory indicates that the user may access the resource;
checking a second memory to determine if the user may access the resource if the first memory does not indicate that the user may access the resource;
providing the user with access to the resource if the second memory indicates that the user may access the resource; and
storing information in the first memory indicating that the user may access the resource if, after checking the second memory, the second memory indicates that the user may access the resource.
2. The computer-readable medium of claim 1 wherein the first memory indicates that the user may access the resource by indicating that access to the resource has been previously provided to the user.
3. The computer-readable medium of claim 1 wherein the user is represented in the first memory by a token.
4. The computer-readable medium of claim 3 wherein the token also represents a plurality of other users.
5. The computer-readable medium of claim 3 wherein the token represents anonymous users.
6. The computer-readable medium of claim 3 further comprising:
authorizing fs to check the first memory.
7. The computer-readable medium of claim 1 wherein the resource is a file.
8. The computer-readable medium of claim 1 wherein the resource is a volume of files.
9. The computer-readable medium of claim 1 wherein the resource is a memory device.
10. The computer-readable medium of claim 1 wherein storing the information in the first memory comprises overwriting other information associated with the resource in the first memory.
11. The computer-readable medium of claim 10 wherein storing the information in the first memory comprises writing a token for the user in the first memory over another token for another user that had last previous access to the resource.
12. The computer-readable medium of claim 1 further comprising, if the resource is altered, removing indications from the first memory allowing access to the resource.
13. The computer-readable medium of claim 1 further comprising, if rights of the user are altered, removing indications from the first memory allowing access by the user.
14. The computer-readable medium of claim 1 wherein the request from the user indicates an operation to perform with respect to the resource, and further comprising:
checking the first memory to determine if the user may perform the operation with respect to the resource;
providing the user with access to the resource to perform the operation if the first memory indicates that the user may perform the operation with respect to the resource;
checking a second memory to determine if the user may perform the operation with respect to the resource if the first memory does not indicate that the user may perform the operation with respect to the resource;
providing the user with access to the resource if the second memory indicates that the user may perform the operation with respect to the resource; and
storing information in the first memory indicating that the user may perform the operation with respect to the resource if, after checking the second memory, the second memory indicates that the user may perform the operation with respect to the resource.
15. A method for providing access to a computer network, the method comprising:
receiving a request from a user to access a resource on the computer network;
checking a first memory to determine if the user may access the resource;
providing the user with access to the resource if the first memory indicates that the user may access the resource;
checking a second memory to determine if the user may access the resource if the first memory does not indicate that the user may access the resource;
providing the user with access to the resource if the second memory indicates that the user may access the resource; and
storing information in the first memory indicating that the user may access the resource if, after checking the second memory, the second memory indicates that the user may access the resource.
16. The method of claim 15 wherein the first memory indicates that the user may access the resource by indicating that access to the resource has been previously provided to the user.
17. The method of claim 15 wherein the user is represented in the first memory by a token.
18. The method of claim 17 wherein the token also represents a plurality of other users.
19. The method of claim 17 wherein the token represents anonymous users.
20. The method of claim 17 further comprising:
authorizing the user by checking a password provided by the user;
associating the token with the user after authorizing the user; and
using the token to check the first memory.
21. The method of claim 15 wherein the resource is a file.
22. The method of claim 15 wherein the resource is a volume of files.
23. The method of claim 15 wherein the resource is a memory device.
24. The method of claim 15 wherein storing the information in the first memory comprises overwriting other information associated with the resource in the first memory.
25. The method of claim 24 wherein storing the information in the first memory comprises writing a token for the user in the first memory over another token for another user that had last previous access to the resource.
26. The method of claim 15 further comprising, if the resource is altered, removing indications from the first memory allowing access to the resource.
27. The method of claim 15 further comprising, if rights of the user are altered, removing indications from the first memory allowing access by the user.
28. The method of claim 15 wherein the request from the user indicates an operation to perform with respect to the resource, and further comprising:
checking the first memory to determine if the user may perform the operation with respect to the resource;
providing the user with access to the resource to perform the operation if the first memory indicates that the user may perform the operation with respect to the resource;
checking a second memory to determine if the user may perform the operation with respect to the resource if the first memory does not indicate that the user may perform the operation with respect to the resource;
providing the user with access to the resource if the second memory indicates that the user may perform the operation with respect to the resource; and
storing information in the first memory indicating that the user may perform the operation with respect to the resource if, after checking the second memory, the second memory indicates that the user may perform the operation with respect to the resource.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/224,918 US20030191846A1 (en) | 1996-08-14 | 1999-01-04 | Access check system utilizing cached access permissions |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US08/689,838 US5889952A (en) | 1996-08-14 | 1996-08-14 | Access check system utilizing cached access permissions |
US09/224,918 US20030191846A1 (en) | 1996-08-14 | 1999-01-04 | Access check system utilizing cached access permissions |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US08/689,838 Continuation US5889952A (en) | 1996-08-14 | 1996-08-14 | Access check system utilizing cached access permissions |
Publications (1)
Publication Number | Publication Date |
---|---|
US20030191846A1 true US20030191846A1 (en) | 2003-10-09 |
Family
ID=24770072
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US08/689,838 Expired - Lifetime US5889952A (en) | 1996-08-14 | 1996-08-14 | Access check system utilizing cached access permissions |
US09/224,918 Abandoned US20030191846A1 (en) | 1996-08-14 | 1999-01-04 | Access check system utilizing cached access permissions |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US08/689,838 Expired - Lifetime US5889952A (en) | 1996-08-14 | 1996-08-14 | Access check system utilizing cached access permissions |
Country Status (1)
Country | Link |
---|---|
US (2) | US5889952A (en) |
Cited By (30)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020099671A1 (en) * | 2000-07-10 | 2002-07-25 | Mastin Crosbie Tanya M. | Query string processing |
US20020112185A1 (en) * | 2000-07-10 | 2002-08-15 | Hodges Jeffrey D. | Intrusion threat detection |
US20020116642A1 (en) * | 2000-07-10 | 2002-08-22 | Joshi Vrinda S. | Logging access system events |
US20020156844A1 (en) * | 2001-04-24 | 2002-10-24 | Square Co., Ltd. | Status notifying method in communication system, status notifying server and communication system |
US20040015585A1 (en) * | 2002-05-30 | 2004-01-22 | International Business Machines Corporation | Tokens utilized in a server system that have different access permissions at different access times and method of use |
US20040073631A1 (en) * | 2000-01-04 | 2004-04-15 | Keorkunian Gary S. | System and method for anonymous observation and use of premium content |
US20040193607A1 (en) * | 2003-03-25 | 2004-09-30 | International Business Machines Corporation | Information processor, database search system and access rights analysis method thereof |
US20040236852A1 (en) * | 2003-04-03 | 2004-11-25 | International Business Machines Corporation | Method to provide on-demand resource access |
US20060026263A1 (en) * | 2002-06-06 | 2006-02-02 | Microsoft Corporation | Managing stored data on a computer network |
US7124203B2 (en) * | 2000-07-10 | 2006-10-17 | Oracle International Corporation | Selective cache flushing in identity and access management systems |
US20070005961A1 (en) * | 2005-06-30 | 2007-01-04 | Microsoft Corporation | Providing user on computer operating system with full privileges token and limited privileges token |
US20070061325A1 (en) * | 2005-09-09 | 2007-03-15 | Konica Minolta Business Technologies, Inc. | File managing apparatus and file managing method |
US7464162B2 (en) * | 2000-07-10 | 2008-12-09 | Oracle International Corporation | Systems and methods for testing whether access to a resource is authorized based on access information |
US20090055907A1 (en) * | 2007-08-20 | 2009-02-26 | Goldman, Sachs & Co | Authentification Broker for the Securities Industry |
US20090174891A1 (en) * | 2008-01-09 | 2009-07-09 | Fuji Xerox Co., Ltd. | Right information managing device, information processing system, and computer readable medium |
US7814536B2 (en) | 2000-07-10 | 2010-10-12 | Oracle International Corporation | User authentication |
US7882132B2 (en) | 2003-10-09 | 2011-02-01 | Oracle International Corporation | Support for RDBMS in LDAP system |
US7904487B2 (en) | 2003-10-09 | 2011-03-08 | Oracle International Corporation | Translating data access requests |
US7925751B1 (en) * | 2002-03-25 | 2011-04-12 | Netapp, Inc. | Mechanism for controlled sharing of files in a clustered application environment |
US20130047215A1 (en) * | 2011-08-15 | 2013-02-21 | Bank Of America Corporation | Method and apparatus for token-based reassignment of privileges |
US8620955B2 (en) | 2009-03-17 | 2013-12-31 | Novell, Inc. | Unified file access across multiple protocols |
US8639895B2 (en) | 2011-07-14 | 2014-01-28 | Freescale Semiconductor, Inc. | Systems and methods for memory region descriptor attribute override |
US8700771B1 (en) | 2006-06-26 | 2014-04-15 | Cisco Technology, Inc. | System and method for caching access rights |
US20140173753A1 (en) * | 2012-12-18 | 2014-06-19 | Adobe Systems Incorporated | Controlling consumption of hierarchical repository data |
US8935418B2 (en) | 2001-02-26 | 2015-01-13 | Oracle International Corporation | Access system interface |
US8949551B2 (en) | 2011-02-23 | 2015-02-03 | Freescale Semiconductor, Inc. | Memory protection unit (MPU) having a shared portion and method of operation |
US9116845B2 (en) | 2011-02-23 | 2015-08-25 | Freescale Semiconductor, Inc. | Remote permissions provisioning for storage in a cache and device therefor |
US9674180B2 (en) | 2006-01-11 | 2017-06-06 | Oracle International Corporation | Using identity/resource profile and directory enablers to support identity management |
WO2017127054A1 (en) * | 2016-01-19 | 2017-07-27 | Hewlett Packard Enterprise Development Lp | Accessing objects via object references |
WO2022055722A1 (en) * | 2020-09-09 | 2022-03-17 | Oracle International Corporation | Surrogate cache for optimized service access with compact user objects and offline database updates |
Families Citing this family (91)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8079086B1 (en) | 1997-11-06 | 2011-12-13 | Finjan, Inc. | Malicious mobile code runtime monitoring system and methods |
US7058822B2 (en) | 2000-03-30 | 2006-06-06 | Finjan Software, Ltd. | Malicious mobile code runtime monitoring system and methods |
US9219755B2 (en) | 1996-11-08 | 2015-12-22 | Finjan, Inc. | Malicious mobile code runtime monitoring system and methods |
US6041390A (en) * | 1996-12-23 | 2000-03-21 | International Business Machines Corporation | Token mechanism for cache-line replacement within a cache memory having redundant cache lines |
US6182122B1 (en) * | 1997-03-26 | 2001-01-30 | International Business Machines Corporation | Precaching data at an intermediate server based on historical data requests by users of the intermediate server |
US5944825A (en) * | 1997-05-30 | 1999-08-31 | Oracle Corporation | Security and password mechanisms in a database system |
US6917962B1 (en) | 1997-10-22 | 2005-07-12 | Brokercom Inc. | Web-based groupware system |
US5941972A (en) * | 1997-12-31 | 1999-08-24 | Crossroads Systems, Inc. | Storage router and method for providing virtual local storage |
USRE42761E1 (en) | 1997-12-31 | 2011-09-27 | Crossroads Systems, Inc. | Storage router and method for providing virtual local storage |
JPH11313102A (en) * | 1998-02-27 | 1999-11-09 | Fujitsu Ltd | Access control list generation method and its device |
US7165152B2 (en) * | 1998-06-30 | 2007-01-16 | Emc Corporation | Method and apparatus for managing access to storage devices in a storage system with access control |
US7756986B2 (en) | 1998-06-30 | 2010-07-13 | Emc Corporation | Method and apparatus for providing data management for a storage system coupled to a network |
US6959288B1 (en) * | 1998-08-13 | 2005-10-25 | International Business Machines Corporation | Digital content preparation system |
US6158010A (en) * | 1998-10-28 | 2000-12-05 | Crosslogix, Inc. | System and method for maintaining security in a distributed computer network |
US6154741A (en) * | 1999-01-29 | 2000-11-28 | Feldman; Daniel J. | Entitlement management and access control system |
US6601171B1 (en) | 1999-02-18 | 2003-07-29 | Novell, Inc. | Deputization in a distributed computing system |
US6665714B1 (en) | 1999-06-30 | 2003-12-16 | Emc Corporation | Method and apparatus for determining an identity of a network device |
US6845395B1 (en) * | 1999-06-30 | 2005-01-18 | Emc Corporation | Method and apparatus for identifying network devices on a storage network |
US6499031B1 (en) * | 1999-07-26 | 2002-12-24 | Microsoft Corporation | Systems and methods for using locks with computer resources |
US7171567B1 (en) | 1999-08-02 | 2007-01-30 | Harris Interactive, Inc. | System for protecting information over the internet |
JP2001093226A (en) * | 1999-09-21 | 2001-04-06 | Sony Corp | Information communication system and method, and information communication device and method |
DE60038448T2 (en) * | 1999-10-14 | 2009-04-02 | Bluearc Uk Ltd. | DEVICE AND METHOD FOR HARDWARE DEVELOPMENT OR HARDWARE ACCELERATION OF OPERATING SYSTEM FUNCTIONS |
US7013485B2 (en) * | 2000-03-06 | 2006-03-14 | I2 Technologies U.S., Inc. | Computer security system |
US7249369B2 (en) * | 2000-07-10 | 2007-07-24 | Oracle International Corporation | Post data processing |
GB2366013B (en) * | 2000-08-17 | 2002-11-27 | Sun Microsystems Inc | Certificate validation mechanism |
US7024454B1 (en) * | 2000-08-25 | 2006-04-04 | Practicefirst.Com L.L.C. | Work sharing and communicating in a web site system |
US7039612B1 (en) * | 2000-09-07 | 2006-05-02 | Sprint Communications Company L.P. | Intranet platform system |
JP2003044297A (en) * | 2000-11-20 | 2003-02-14 | Humming Heads Inc | Information processing method and device controlling computer resource, information processing system, control method therefor, storage medium and program |
US7260636B2 (en) * | 2000-12-22 | 2007-08-21 | Emc Corporation | Method and apparatus for preventing unauthorized access by a network device |
US6934853B2 (en) * | 2001-01-18 | 2005-08-23 | International Business Machines Corporation | Method, system and program for sharing the ability to set configuration parameters in a network environment |
US7031962B2 (en) * | 2001-03-27 | 2006-04-18 | Bea Systems, Inc. | System and method for managing objects and resources with access rights embedded in nodes within a hierarchical tree structure |
US7640582B2 (en) * | 2003-04-16 | 2009-12-29 | Silicon Graphics International | Clustered filesystem for mix of trusted and untrusted nodes |
US7231661B1 (en) | 2001-06-21 | 2007-06-12 | Oracle International Corporation | Authorization services with external authentication |
US6988280B2 (en) * | 2001-06-29 | 2006-01-17 | International Business Machines Corporation | System and method for enhancing authorization request in a computing device |
US7325064B2 (en) * | 2001-07-17 | 2008-01-29 | International Business Machines Corporation | Distributed locking protocol with asynchronous token prefetch and relinquish |
US20030097582A1 (en) * | 2001-11-19 | 2003-05-22 | Yves Audebert | Method and system for reducing personal security device latency |
US7225256B2 (en) * | 2001-11-30 | 2007-05-29 | Oracle International Corporation | Impersonation in an access system |
US7912971B1 (en) | 2002-02-27 | 2011-03-22 | Microsoft Corporation | System and method for user-centric authorization to access user-specific information |
US7076558B1 (en) | 2002-02-27 | 2006-07-11 | Microsoft Corporation | User-centric consent management system and method |
US7457822B1 (en) | 2002-11-01 | 2008-11-25 | Bluearc Uk Limited | Apparatus and method for hardware-based file system |
US8041735B1 (en) | 2002-11-01 | 2011-10-18 | Bluearc Uk Limited | Distributed file system and method |
JP4365612B2 (en) * | 2003-04-15 | 2009-11-18 | 白光株式会社 | Electrical component attachment / detachment device |
KR100559025B1 (en) * | 2003-05-30 | 2006-03-10 | 엘지전자 주식회사 | Home network management system |
US7478094B2 (en) * | 2003-06-11 | 2009-01-13 | International Business Machines Corporation | High run-time performance method for setting ACL rule for content management security |
JP4729844B2 (en) * | 2003-10-16 | 2011-07-20 | 富士ゼロックス株式会社 | Server apparatus, information providing method, and program |
US7590705B2 (en) | 2004-02-23 | 2009-09-15 | Microsoft Corporation | Profile and consent accrual |
US7549171B2 (en) * | 2004-06-10 | 2009-06-16 | Hitachi, Ltd. | Method and apparatus for validation of application data on a storage system |
US20070208946A1 (en) * | 2004-07-06 | 2007-09-06 | Oracle International Corporation | High performance secure caching in the mid-tier |
US7702730B2 (en) | 2004-09-03 | 2010-04-20 | Open Text Corporation | Systems and methods for collaboration |
US7630974B2 (en) | 2004-09-28 | 2009-12-08 | Oracle International Corporation | Multi-language support for enterprise identity and access management |
US7395552B2 (en) * | 2004-10-22 | 2008-07-01 | Sugarcrm, Inc. | Team based row level security system and method |
US20060288050A1 (en) * | 2005-06-15 | 2006-12-21 | International Business Machines Corporation | Method, system, and computer program product for correlating directory changes to access control modifications |
US9137227B2 (en) * | 2005-08-24 | 2015-09-15 | International Business Machines Corporation | Matching entitlement information for multiple sources |
US7974395B2 (en) * | 2005-09-28 | 2011-07-05 | Avaya Inc. | Detection of telephone number spoofing |
US8775586B2 (en) * | 2005-09-29 | 2014-07-08 | Avaya Inc. | Granting privileges and sharing resources in a telecommunications system |
US7506102B2 (en) * | 2006-03-28 | 2009-03-17 | Cisco Technology, Inc. | Method and apparatus for local access authorization of cached resources |
US8015215B2 (en) * | 2006-08-24 | 2011-09-06 | Oracle America, Inc. | Delegation in a file system with distributed components |
US8082230B1 (en) * | 2006-12-22 | 2011-12-20 | Symantec Operating Corporation | System and method for mounting a file system on multiple host computers |
KR101321369B1 (en) * | 2007-03-21 | 2013-10-28 | 삼성전자주식회사 | Method and apparatus of processing an access to a disk block |
US9336387B2 (en) * | 2007-07-30 | 2016-05-10 | Stroz Friedberg, Inc. | System, method, and computer program product for detecting access to a memory device |
US20100131600A1 (en) * | 2008-11-24 | 2010-05-27 | Ibm Corporation | Message masking in middleware environments |
US9641334B2 (en) * | 2009-07-07 | 2017-05-02 | Varonis Systems, Inc. | Method and apparatus for ascertaining data access permission of groups of users to groups of data elements |
US10229191B2 (en) | 2009-09-09 | 2019-03-12 | Varonis Systems Ltd. | Enterprise level data management |
US8578507B2 (en) | 2009-09-09 | 2013-11-05 | Varonis Systems, Inc. | Access permissions entitlement review |
WO2011030324A1 (en) * | 2009-09-09 | 2011-03-17 | Varonis Systems, Inc. | Enterprise level data management |
US20110061093A1 (en) * | 2009-09-09 | 2011-03-10 | Ohad Korkus | Time dependent access permissions |
US9038168B2 (en) * | 2009-11-20 | 2015-05-19 | Microsoft Technology Licensing, Llc | Controlling resource access based on resource properties |
US9088580B2 (en) * | 2009-12-31 | 2015-07-21 | Microsoft Technology Licensing, Llc | Access control based on user and service |
WO2011148375A1 (en) | 2010-05-27 | 2011-12-01 | Varonis Systems, Inc. | Automation framework |
US10037358B2 (en) | 2010-05-27 | 2018-07-31 | Varonis Systems, Inc. | Data classification |
US10296596B2 (en) | 2010-05-27 | 2019-05-21 | Varonis Systems, Inc. | Data tagging |
US9870480B2 (en) | 2010-05-27 | 2018-01-16 | Varonis Systems, Inc. | Automatic removal of global user security groups |
US8533787B2 (en) | 2011-05-12 | 2013-09-10 | Varonis Systems, Inc. | Automatic resource ownership assignment system and method |
US9147180B2 (en) | 2010-08-24 | 2015-09-29 | Varonis Systems, Inc. | Data governance for email systems |
US8595821B2 (en) | 2011-01-14 | 2013-11-26 | International Business Machines Corporation | Domains based security for clusters |
US8832389B2 (en) | 2011-01-14 | 2014-09-09 | International Business Machines Corporation | Domain based access control of physical memory space |
US8631123B2 (en) | 2011-01-14 | 2014-01-14 | International Business Machines Corporation | Domain based isolation of network ports |
US8429191B2 (en) | 2011-01-14 | 2013-04-23 | International Business Machines Corporation | Domain based isolation of objects |
CN103348316B (en) | 2011-01-27 | 2016-08-24 | 瓦欧尼斯系统有限公司 | Access rights management system and method |
US9680839B2 (en) | 2011-01-27 | 2017-06-13 | Varonis Systems, Inc. | Access permissions management system and method |
US8909673B2 (en) | 2011-01-27 | 2014-12-09 | Varonis Systems, Inc. | Access permissions management system and method |
US20120215989A1 (en) * | 2011-02-23 | 2012-08-23 | Freescale Semiconductor, Inc. | Memory protection in a data processing system |
US20120227098A1 (en) * | 2011-03-03 | 2012-09-06 | Microsoft Corporation | Sharing user id between operating system and application |
US8375439B2 (en) | 2011-04-29 | 2013-02-12 | International Business Machines Corporation | Domain aware time-based logins |
US9183361B2 (en) | 2011-09-12 | 2015-11-10 | Microsoft Technology Licensing, Llc | Resource access authorization |
JP6056384B2 (en) * | 2012-10-31 | 2017-01-11 | 株式会社リコー | System and service providing apparatus |
US9189643B2 (en) | 2012-11-26 | 2015-11-17 | International Business Machines Corporation | Client based resource isolation with domains |
US9251363B2 (en) | 2013-02-20 | 2016-02-02 | Varonis Systems, Inc. | Systems and methodologies for controlling access to a file system |
JP6287401B2 (en) * | 2014-03-18 | 2018-03-07 | 富士ゼロックス株式会社 | Relay device, system and program |
JP2015201030A (en) | 2014-04-08 | 2015-11-12 | 富士通株式会社 | Terminal device, information management server, terminal program, information management program, and system |
US10205631B1 (en) * | 2015-10-30 | 2019-02-12 | Intuit Inc. | Distributing an access control service to local nodes |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5560008A (en) * | 1989-05-15 | 1996-09-24 | International Business Machines Corporation | Remote authentication and authorization in a distributed data processing system |
JPH087709B2 (en) * | 1989-05-15 | 1996-01-29 | インターナシヨナル・ビジネス・マシーンズ・コーポレーシヨン | Access privilege control method and system |
US5577209A (en) * | 1991-07-11 | 1996-11-19 | Itt Corporation | Apparatus and method for providing multi-level security for communication among computers and terminals on a network |
-
1996
- 1996-08-14 US US08/689,838 patent/US5889952A/en not_active Expired - Lifetime
-
1999
- 1999-01-04 US US09/224,918 patent/US20030191846A1/en not_active Abandoned
Cited By (49)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7111078B2 (en) * | 2000-01-04 | 2006-09-19 | Steven B. Hirst | System and method for anonymous observation and use of premium content by indirect access through portal |
US20040073631A1 (en) * | 2000-01-04 | 2004-04-15 | Keorkunian Gary S. | System and method for anonymous observation and use of premium content |
US8204999B2 (en) | 2000-07-10 | 2012-06-19 | Oracle International Corporation | Query string processing |
US20020116642A1 (en) * | 2000-07-10 | 2002-08-22 | Joshi Vrinda S. | Logging access system events |
US9038170B2 (en) | 2000-07-10 | 2015-05-19 | Oracle International Corporation | Logging access system events |
US20020099671A1 (en) * | 2000-07-10 | 2002-07-25 | Mastin Crosbie Tanya M. | Query string processing |
US7464162B2 (en) * | 2000-07-10 | 2008-12-09 | Oracle International Corporation | Systems and methods for testing whether access to a resource is authorized based on access information |
US7814536B2 (en) | 2000-07-10 | 2010-10-12 | Oracle International Corporation | User authentication |
US20020112185A1 (en) * | 2000-07-10 | 2002-08-15 | Hodges Jeffrey D. | Intrusion threat detection |
US8661539B2 (en) | 2000-07-10 | 2014-02-25 | Oracle International Corporation | Intrusion threat detection |
US7124203B2 (en) * | 2000-07-10 | 2006-10-17 | Oracle International Corporation | Selective cache flushing in identity and access management systems |
US8935418B2 (en) | 2001-02-26 | 2015-01-13 | Oracle International Corporation | Access system interface |
US8103736B2 (en) * | 2001-04-24 | 2012-01-24 | Kabushiki Kaisha Square Enix | Status notifying method in communication system, status notifying server and communication system |
US20020156844A1 (en) * | 2001-04-24 | 2002-10-24 | Square Co., Ltd. | Status notifying method in communication system, status notifying server and communication system |
US7925751B1 (en) * | 2002-03-25 | 2011-04-12 | Netapp, Inc. | Mechanism for controlled sharing of files in a clustered application environment |
US20040015585A1 (en) * | 2002-05-30 | 2004-01-22 | International Business Machines Corporation | Tokens utilized in a server system that have different access permissions at different access times and method of use |
US7028090B2 (en) * | 2002-05-30 | 2006-04-11 | International Business Machines Corporation | Tokens utilized in a server system that have different access permissions at different access times and method of use |
US20060026263A1 (en) * | 2002-06-06 | 2006-02-02 | Microsoft Corporation | Managing stored data on a computer network |
US20040193607A1 (en) * | 2003-03-25 | 2004-09-30 | International Business Machines Corporation | Information processor, database search system and access rights analysis method thereof |
US7672946B2 (en) * | 2003-03-25 | 2010-03-02 | International Business Machines Corporation | Information processor, database search system and access rights analysis method thereof |
US20040236852A1 (en) * | 2003-04-03 | 2004-11-25 | International Business Machines Corporation | Method to provide on-demand resource access |
US8135795B2 (en) * | 2003-04-03 | 2012-03-13 | International Business Machines Corporation | Method to provide on-demand resource access |
US7882132B2 (en) | 2003-10-09 | 2011-02-01 | Oracle International Corporation | Support for RDBMS in LDAP system |
US7904487B2 (en) | 2003-10-09 | 2011-03-08 | Oracle International Corporation | Translating data access requests |
US7636851B2 (en) * | 2005-06-30 | 2009-12-22 | Microsoft Corporation | Providing user on computer operating system with full privileges token and limited privileges token |
US20070005961A1 (en) * | 2005-06-30 | 2007-01-04 | Microsoft Corporation | Providing user on computer operating system with full privileges token and limited privileges token |
US20070061325A1 (en) * | 2005-09-09 | 2007-03-15 | Konica Minolta Business Technologies, Inc. | File managing apparatus and file managing method |
US9674180B2 (en) | 2006-01-11 | 2017-06-06 | Oracle International Corporation | Using identity/resource profile and directory enablers to support identity management |
US8700771B1 (en) | 2006-06-26 | 2014-04-15 | Cisco Technology, Inc. | System and method for caching access rights |
US8839383B2 (en) * | 2007-08-20 | 2014-09-16 | Goldman, Sachs & Co. | Authentification broker for the securities industry |
US20150007301A1 (en) * | 2007-08-20 | 2015-01-01 | Goldman, Sachs & Co. | Identity-independent authentication tokens |
US20090055907A1 (en) * | 2007-08-20 | 2009-02-26 | Goldman, Sachs & Co | Authentification Broker for the Securities Industry |
US9426138B2 (en) * | 2007-08-20 | 2016-08-23 | Goldman, Sachs & Co. | Identity-independent authentication tokens |
AU2008212074B2 (en) * | 2008-01-09 | 2010-03-25 | Fujifilm Business Innovation Corp. | Right information managing device, information processing system, information processing method, and information processing program |
US20090174891A1 (en) * | 2008-01-09 | 2009-07-09 | Fuji Xerox Co., Ltd. | Right information managing device, information processing system, and computer readable medium |
US8089651B2 (en) | 2008-01-09 | 2012-01-03 | Fuji Xerox Co., Ltd. | Right information managing device, information processing system, and computer readable medium |
KR101054319B1 (en) * | 2008-01-09 | 2011-08-05 | 후지제롯쿠스 가부시끼가이샤 | Rights information management device, information processing system and computer readable storage medium |
US8620955B2 (en) | 2009-03-17 | 2013-12-31 | Novell, Inc. | Unified file access across multiple protocols |
US8949551B2 (en) | 2011-02-23 | 2015-02-03 | Freescale Semiconductor, Inc. | Memory protection unit (MPU) having a shared portion and method of operation |
US9116845B2 (en) | 2011-02-23 | 2015-08-25 | Freescale Semiconductor, Inc. | Remote permissions provisioning for storage in a cache and device therefor |
US8639895B2 (en) | 2011-07-14 | 2014-01-28 | Freescale Semiconductor, Inc. | Systems and methods for memory region descriptor attribute override |
US8752143B2 (en) * | 2011-08-15 | 2014-06-10 | Bank Of America Corporation | Method and apparatus for token-based reassignment of privileges |
US20130047215A1 (en) * | 2011-08-15 | 2013-02-21 | Bank Of America Corporation | Method and apparatus for token-based reassignment of privileges |
US20140173753A1 (en) * | 2012-12-18 | 2014-06-19 | Adobe Systems Incorporated | Controlling consumption of hierarchical repository data |
US10069838B2 (en) * | 2012-12-18 | 2018-09-04 | Adobe Systems Incorporated | Controlling consumption of hierarchical repository data |
WO2017127054A1 (en) * | 2016-01-19 | 2017-07-27 | Hewlett Packard Enterprise Development Lp | Accessing objects via object references |
US10380025B2 (en) | 2016-01-19 | 2019-08-13 | Hewlett Packard Enterprise Development Lp | Accessing objects via object references |
WO2022055722A1 (en) * | 2020-09-09 | 2022-03-17 | Oracle International Corporation | Surrogate cache for optimized service access with compact user objects and offline database updates |
US11824955B2 (en) | 2020-09-09 | 2023-11-21 | Oracle International Corporation | Surrogate cache for optimized service access with compact user objects and offline database updates |
Also Published As
Publication number | Publication date |
---|---|
US5889952A (en) | 1999-03-30 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US5889952A (en) | Access check system utilizing cached access permissions | |
EP0794479B1 (en) | Method and apparatus for providing dynamic network file system client authentication | |
US6122631A (en) | Dynamic server-managed access control for a distributed file system | |
US7222150B1 (en) | Network server card and method for handling requests received via a network interface | |
US6453354B1 (en) | File server system using connection-oriented protocol and sharing data sets among data movers | |
US6324581B1 (en) | File server system using file system storage, data movers, and an exchange of meta data among data movers for file locking and direct access to shared file systems | |
US6973455B1 (en) | File server system providing direct data sharing between clients with a server acting as an arbiter and coordinator | |
US5740367A (en) | Method and apparatus for improving the throughput of a local area network | |
US5689638A (en) | Method for providing access to independent network resources by establishing connection using an application programming interface function call without prompting the user for authentication data | |
US7120631B1 (en) | File server system providing direct data sharing between clients with a server acting as an arbiter and coordinator | |
US7200862B2 (en) | Securing uniform resource identifier namespaces | |
US6381602B1 (en) | Enforcing access control on resources at a location other than the source location | |
KR960002030B1 (en) | Method and system for open file caching in a networked computer | |
US6556995B1 (en) | Method to provide global sign-on for ODBC-based database applications | |
US8127222B2 (en) | Latches-links as virtual attachments in documents | |
US7346774B2 (en) | Encrypted key cache | |
US5913025A (en) | Method and apparatus for proxy authentication | |
US7974985B1 (en) | System and method for duplication of virtual server files | |
US20060248343A1 (en) | Apparatus and method for using a directory service for authentication and authorization to access resources outside of the directory service | |
US6988280B2 (en) | System and method for enhancing authorization request in a computing device | |
US20080244711A1 (en) | System and Method for Specifying Access to Resources in a Mobile Code System | |
US7016897B2 (en) | Authentication referral search for LDAP | |
US7308481B2 (en) | Network storage system | |
JP4084850B2 (en) | Safety device and safety management method for data processing system | |
US6442654B1 (en) | Operating system support for in-server caching of documents |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034766/0001 Effective date: 20141014 |