IMPERSONATION IN AN ACCESS SYSTEM

• US 20070089167A1
• Filed: 11/16/2006
• Published: 04/19/2007
• Est. Priority Date: 11/30/2001
• Status: Active Grant

• Current Assignee: Campbell-ERS LLC
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Villavicencio, Francisco
• Granted Patent: US 7,765,298 B2
• Time in Patent Office: Days
• US Class Current: 726/5
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 63/168 above the transport layer
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

The present invention pertains to a system for managing network access to resources that allows a first entity to impersonate a second entity. In one embodiment, the first entity can impersonate the second entity without knowing the second entity'"'"'s password and/or without altering anything in the entity'"'"'s set of personal information. This invention provides the first entity with the ability to troubleshoot in a live production system without disrupting the users or the system. In one embodiment, the first entity authenticates as itself. Access to resources is provided in response to an authorization process based on the identity of the entity being impersonated.

Claims

1-48. -48. (canceled)

49. A method of allowing a first user to impersonate a second user, the method comprising the steps of:

receiving authentication credentials for the first user and an identification of the second user;

authenticating said first user based on said authentication credentials for said first user;

creating a cookie that stores an indication of said second user if said step of authenticating is performed successfully; and

authorizing said first user to access a first resource as said second user based on said cookie.

50. A method according to claim 49, further comprising the step of:

providing a form for said authentication credentials, said form includes a request for a user identification, a password and an impersonates identification, said user identification and said password correspond to said authentication credentials for said first user, said impersonatee identification corresponds to said identification of said second user.

51. A method according to claim 49, wherein:

said step of receiving is performed by an access system;

said access system protects said first resource; and

said first resource is separate from said access system.

52. A method according to claim 49, wherein:

said step of receiving is performed by an access system;

said access system protects a plurality of resources; and

said plurality of resources includes said first resource.

53. A method according to claim 49, wherein:

said cookie stores a distinguished name of said second user and an IP address for said first user.

54. A method according to claim 49, further comprising the steps of:

receiving a request to access said first resource;

providing a form for said authentication credentials, said form includes a request for a user identification, a password and an impersonatee identification, said user identification and said password correspond to said authentication credentials for said first user, said impersonatee identification corresponds to said identification of said second user; and

transmitting said cookie for storage on a device being used by said first user to send said request to access said first resource.

55. A method according to claim 49, wherein:

said steps of receiving, authenticating and authorizing are performed by an access system;

said access system provides access management services and identity management services; and

said first resource is protected by, but separate from, said access system.

56. A method according to claim 49, wherein:

said authentication credentials include an ID and a password;

said step of authenticating includes the steps of;

searching a directory server for a first user identity profile that matches said ID,

verifying said password based on said user identity profile,

searching said directory server for a second user identity profile that matches said identification of said second user, and

accessing one or more attributes of said second user identity profile; and

said cookie includes said one or more attributes of said second user identity profile.

57. A method according to claim 56, wherein:

said steps of searching a directory server for a first user identity profile and verifying said password based on said user identity profile are performed by a first authentication plug-in; and

said steps of searching said directory server for a second user identity profile and accessing one or more attributes of said second user identity profile are performed by a second authentication plug-in.

58. A method according to claim 49, wherein:

said cookie stores a distinguished name for said second user; and

said step of authorizing includes the steps of;

accessing said distinguished name stored in said cookie,

accessing a user identity profile for said second user based on said distinguished name,

accessing a set of one or more authorization rules for said first resource, and

comparing attributes of said user identity profile for said second user to said set of one or more authorization rules for said first resource.

59. A method according to claim 49, wherein:

said authentication credentials correspond to a set of attributes for said first user;

said identification of said second user corresponds to a set of attributes for said second user;

said step of authorizing is based on one or more of said attributes for said first user; and

said step of authorizing is based on one or more of said attributes for said second user.

60. A method according to claim 49, wherein:

said authentication credentials correspond to a set of attributes for said first user; and

said step of authorizing is not based on attributes for said first user.

61. A method according to claim 49, further comprising the steps of:

receiving a request for a login form; and

providing said login form, said login form includes a request for a user identification, a password and an impersonatee identification, said user identification and said password correspond to said authentication credentials for said first user, said impersonatee identification corresponds to said identification of said second user.

62. A method according to claim 49, further comprising the steps of:

receiving a request from said first user to access a second resource after said step of creating said cookie;

accessing contents of said cookie and determining not to authenticate said first user in response to said request to access said second resource; and

authorizing said first user to access said second resource as said second user based on said cookie, said step of authorizing said first user to access said second resource is performed without authenticating said first user in response to said request to access said second resource.

63. A method according to claim 49, wherein:

said steps of authenticating and authorizing are performed without knowing a password for said second user.

64. A method for impersonating, comprising the steps of:

receiving authentication credentials for an impersonator and an identification of an impersonatee at an access system, wherein said access system protects a first resource that is separate from said access system;

authenticating said impersonator based on said authentication credentials for said impersonatee, wherein said step of authenticating is performed by said access system; and

authorizing said impersonator to access said first resource as said impersoriatee, wherein said step of authorizing is performed by said access system.

65. A method according to claim 64, wherein:

said steps of authenticating and authorizing are performed without knowing a password for said impersonatee.

66. A method according to claim 64, wherein:

said access system protects a plurality of resources that are separate from said access system; and

said plurality of resources includes said first resource.

67. A method according to claim 64, wherein:

said authentication credentials include an ID and a password;

said step of authenticating includes the steps of;

searching a directory server for a first user identity profile that matches said ID,

verifying said password based on said user identity profile,

searching said directory server for a second user identity profile that matches said identification of said impersonatee, and

accessing one or more attributes of said second user identity profile; and

said step of authorizing uses said one or more attributes of said second user identity profile.

68. A method according to claim 64, wherein:

said steps of searching a directory server for a first user identity profile and verifying said password based on said user identity profile are performed by a first authentication plug-in; and

said steps of searching said directory server for a second user identity profile and accessing one or more attributes of said second user identity profile are performed by a second authentication plug-in.

69. A method according to claim 64, wherein:

said step of authenticating provides a name for said impersonatee; and

said step of authorizing includes the steps of;

accessing said name,

accessing a user identity profile for said impersonatee based on said name,

accessing a set of one or more authorization riles for said resource, and

comparing attributes of said user identity profile for said impersonatee to said set of one or more authorization rules for said resource.

70. A method according to claim 64, wherein:

said authentication credentials correspond to a set of attributes for said impersonator;

said identification of said impersonatee corresponds to a set of attributes for said impersonates;

said step of authorizing is based on one or more of said attributes for said impersonator; and

said step of authorizing is based on one or more of said attributes for said impersonatee.

71. A method according to claim 64, further comprising the steps of:

receiving a request to access a second resource from said impersonator after said step of authenticating said impersonator, wherein said access system protects said second resource; and

authorizing said impersonator to access said second resource as said impersonatee, wherein said step of authorizing said impersonator to access said second resource is performed without authenticating said impersonator in response to said request to access said second resource.

72. A method of allowing a first entity to impersonate a second entity, the method comprising the steps of:

receiving authentication credentials for the first entity and an identification of the second entity at an access system, wherein said access system protects a plurality of resources;

receiving an indication of one or more of said plurality of resources;

authenticating said first entity based on said authentication credentials for said first entity, wherein said step of authenticating is performed by said access system; and

authorizing said first entity to access said one or more of said plurality of resources as said second entity, wherein said step of authorizing is performed by said access system.

73. A method according to claim 72, wherein:

said authentication credentials include an ID and a password;

said step of authenticating includes the steps of;

searching a directory server for a first user identity profile that matches said ID,

verifying said password based on said user identity profile,

searching said directory server for a second user identity profile that matches said identification of said second entity, and

accessing one or more attributes of said second user identity profile; and

said step of authorizing uses said one or more attributes of said second user identity profile.

74. A method according to claim 72, wherein:

said step of authenticating provides a name for said second entity; and

said step of authorizing includes the steps of;

accessing said name,

accessing a user identity profile for said second entity based on said name,

accessing a set of one or more authorization rules for said resource, and

comparing attributes of said user identity profile for said second entity to said set of one or more authorization rules.

75. A method according to claim 72, wherein:

said authentication credentials correspond to a set of attributes for said first entity;

said identification of said second entity corresponds to a set of attributes for said second entity;

said step of authorizing is based on one or more attributes for said first entity; and

said step of authorizing is not based on attributes for said first entity.

76. One or more processor readable storage devices having processor readable code embodied on said processor readable storage devices, said processor readable code for programming one or more processors to perform a method comprising the steps of:

receiving authentication credentials for a first user and an identification of a second user;

authenticating said first user based on said authentication credentials for said first user;

creating a cookie that stores an indication of said second user if said step of authenticating is performed successfully; and

authorizing said first user to access a first resource as said second user based on said cookie.

77. One or more processor readable storage devices according to claim 76, wherein:

said steps of receiving, authenticating and authorizing are performed by an access system;

said access system protects a plurality of resources separate from said access system; and

said plurality of resources includes said first resource.

78. One or more processor readable storage devices according to claim 76, wherein:

said cookie stores a distinguished name of said second user and an IP address for said first user.

79. One or more processor readable storage devices according to claim 76, wherein:

said authentication credentials include an ID and a password;

said step of authenticating includes the steps of;

searching a directory server for a first user identity profile that matches said ID,

verifying said password based on said user identity profile,

searching said directory server for a second user identity profile that matches said identification of said second user, and

accessing one or more attributes of said second user identity profile; and

said cookie includes said one or more attributes of said second user identity profile.

80. One or more processor readable storage devices according to claim 76, wherein:

said cookie stores a distinguished name for said second user; and

said step of authorizing includes the steps of;

accessing said distinguished name stored in said cookie,

accessing a user identity profile for said second user based on said distinguished name,

accessing a set of one or more authorization rules for said first resource, and

comparing attributes of said user identity profile for said second user to said set of one or more authorization rules for said first resource.

81. One or more processor readable storage devices according to claim 76, wherein:

said authentication credentials correspond to a set of attributes for said first user;

said identification of said second user corresponds to a set of attributes for said second user;

said step of authorizing is based on one or more of said attributes for said first user; and

said step of authorizing is based on one or more of said attributes for said second user.

82. One or more processor readable storage devices according to claim 76, wherein:

receiving a request from said first user to access a second resource after said step of creating said cookie;

accessing contents of said cookie and determining not to authenticate said first user in response to said request to access said second resource; and

authorizing said first user to access said second resource as said second user based on said cookie, said step of authorizing said first user to access said second resource is performed without authenticating said first user in response to said request to access said second resource.

83. An apparatus for providing access management that allows for impersonating, comprising:

a communication interface;

a storage device; and

a processing unit in communication with said communication interface and said storage device, said processing unit performs a method comprising the steps of;

receiving authentication credentials for a first user and an identification of a second user,

authenticating said first user based on said authentication credentials for said first user,

creating a cookie that stores an indication of said second user if said step of authenticating is performed successfully, and

authorizing said first user to access a first resource as said second user based on said cookie.

84. An apparatus according to claim 83, wherein:

said steps of receiving, authenticating and authorizing are performed by an access system;

said access system protects a plurality of resources separate from said access system; and

said plurality of resources includes said first resource.

85. An apparatus according to claim 83, wherein:

said authentication credentials include an ID and a password;

said step of authenticating includes the steps of;

searching a directory server for a first user identity profile that matches said ID,

verifying said password based on said user identity profile,

searching said directory server for a second user identity profile that matches said identification of said second user, and

accessing one or more attributes of said second user identity profile; and

said cookie includes said one or more attributes of said second user identity profile.

86. An apparatus according to claim 83, wherein:

said cookie stores a distinguished name for said second user; and

said step of authorizing includes the steps of;

accessing said distinguished name stored in said cookie,

accessing a user identity profile for said second user based on said distinguished name,

accessing a set of one or more authorization rules for said first resource, and

comparing attributes of said user identity profile for said second user to said set of one or more authorization rules for said first resource.

87. One or more processor readable storage devices having processor readable code embodied on said processor readable storage devices, said processor readable code for programming one or more processors to perform a method comprising the steps of:

receiving authentication credentials for an impersonator and an identification of an impersonatee at an access system, said access system protects a first resource that is separate from said access system;

authenticating said impersonator based on said authentication credentials for said impersonator, said step of authenticating is performed by said access system; and

authorizing said impersonator to access said first resource as said impersonatee, said step of authorizing is performed by said access system.

88. One or more processor readable storage devices according to claim 87, wherein:

said access system protects a plurality of resources that are separate from said access system; and

said plurality of resources includes said first resource.

89. One or more processor readable storage, devices according to claim 87, wherein:

said authentication credentials include an ID and a password;

said step of authenticating includes the steps of;

searching a directory server for a first user identity profile that matches said ID,

verifying said password based on said user identity profile,

searching said directory server for a second user identity profile that matches said identification of said impersonatee, and

accessing one or more attributes of said second user identity profile; and

said step of authorizing uses said one or more attributes of said second user identity profile.

90. One or more processor readable storage devices according to claim 87, wherein:

said step of authenticating provides a name for said impersonatee; and

said step of authorizing includes the steps of;

accessing said name,

accessing a user identity profile for said impersonatee based on said name,

accessing a set of one or more authorization rules for said resource, and

comparing attributes of said user identity profile for said impersonatee to said set of one or more authorization rules for said resource.

91. One or more processor readable storage devices according to claim 87, wherein:

said authentication credentials correspond to a set of attributes for said impersonator;

said identification of said impersonatee corresponds to a set of attributes for said impersonatee;

said step of authorizing is based on one or more of said attributes for said impersonator; and

said step of authorizing is based on one or more of said attributes for said impersonatee.

92. One or more processor readable storage devices according to claim 87, wherein said method further comprises the steps of:

receiving a request to access a second resource from said impersonator after said step of authenticating said impersonator, said access system protects said second resource; and

authorizing said impersonator to access said second resource as said impersonatee, said step of authorizing said impersonator to access said second resource is performed without authenticating said impersonator in response to said request to access said second resource.

93. An apparatus for providing access management that allows for impersonating, comprising:

a communication interface;

a storage device; and

a processing unit in communication with said communication interface and said storage device, said processing unit performs a method comprising the steps of;

receiving authentication credentials for an impersonator and an identification of an impersonates at an access system, said access system protects a first resource that is separate from said access system,

authenticating said impersonator based on said authentication credentials for said impersonator, said step of authenticating is performed by said access system, and

authorizing said impersonator to access said first resource as said impersonatee, said step of authorizing is performed by said access system.

94. An apparatus according to claim 93, wherein:

said access system protects a plurality of resources that are separate from said access system; and

said plurality of resources includes said first resource.

95. An apparatus according to claim 93, wherein:

said authentication credentials include an ID and a password;

said step of authenticating includes the steps of;

searching a directory server for a first user identity profile that matches said ID,

verifying said password based on said user identity profile,

searching said directory server for a second user identity profile that matches said identification of said impersonatee, and

accessing one or more attributes of said second user identity profile; and

said step of authorizing uses said one or more attributes of said second user identity profile.

96. An apparatus according to claim 93, wherein:

said step of authenticating provides a name for said impersonatee; and

said step of authorizing includes the steps of;

accessing said name,

accessing a user identity profile for said impersonatee based on said name,

accessing a set of one or more authorization rules for said resource, and

comparing attributes of said user identity profile for said impersonates to said set of one or more authorization rules for said resource.