User authentication

• US 7,194,764 B2
• Filed: 02/26/2001
• Issued: 03/20/2007
• Est. Priority Date: 07/10/2000
• Status: Expired due to Term

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Martherus, Robin E., Ramamurthy, Srinivasagopalan
• Primary Examiner(s): Jung; David
• Application Number:
  US09/793,658
• Publication Number:
  US 20020112155A1
• Time in Patent Office: 2,213 Days
• Field of Search: 713/202, 713/200, 713/150, 713/155, 713/156, 713/175, 726/8, 726/4, 726/3
• US Class Current: 726/8
• CPC Class Codes: G06F 21/41 where a single sign-on provides access to a plurality of computers
• CPC Class Codes: H04L 63/0815 providing single-sign-on or federations
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226

Abstract

The present invention authenticates a user for multiple resources distributed across multiple domains through the performance of a single authentication. User access requests for a protected resource in a first domain are received and redirected to a second domain. User authentication is performed at the second domain. In one embodiment, the system transmits an authentication cookie for the second domain to the user after authentication at the second domain. In another embodiment, the system further redirects subsequent resource requests for resources in the first domain or a third domain to the second domain. The second domain confirms the user'"'"'s authentication for applicable portions of the first, second, and third domains using the cookie.

Claims

1. A method for authenticating a user for a plurality of domains in a network-based system, comprising:

receiving at said first domain a request from said user, for a protected resource, said resource is in said first domain;

redirecting said user to a second domain for authentication; and

authenticating said user for said first domain at said second domain.

2. The method of claim 1, further comprising the step of:

determining whether said first and second domains reside on a single Web Server.

3. The method of claim 1, further comprising the step of:

transmitting an authentication cookie for said second domain to said user after said step of authentication.

4. The method of claim 3, further comprising the step of:

authorizing said user for said resource.

5. The method of claim 3, further comprising the steps of:

redirecting a subsequent resource request for a resource in a third domain to said second domain;

transmitting said cookie to said second domain; and

confirming authentication of said user for said third domain using said cookie.

6. The method of claim 5, wherein:

said first and third domains are one domain.

7. The method of claim 6, wherein:

said first, second, and third domains reside on a single Web Server.

8. The method of claim 6, wherein:

said step of redirecting a subsequent resource request is transparent to said user.

9. The method of claim 3, wherein:

said cookie is encrypted.

10. The method of claim 3, wherein:

said cookie is encrypted using RC4 encryption, said cookie comprising;

an authentication level,

a user id,

a user ip address,

a session start time,

an idle start time, and

a secured hash.

11. The method of claim 1, wherein:

said system is an Access System.

12. The method of claim 11, wherein:

said Access System includes an access management system and an identity management system.

13. The method of claim 1, wherein:

said first and second domains reside on a single Web Server.

14. The method of claim 1, wherein:

said step of authenticating is performed according to an authentication rule of said second domain.

15. The method of claim 14, wherein:

said authentication rule is a default rule for verifying user identities to authenticate users for resources in said second domain.

16. The method of claim 14, wherein:

said authentication rule is a policy rule for verifying user identities to authenticate users for resources matched to a policy of said second domain.

17. The method of claim 1, wherein:

said second domain is a preferred host.

18. The method of claim 1, wherein:

said step of redirecting is transparent to said user.

19. The method of claim 1, wherein:

said system is an Access Management System.

20. The method of claim 1, wherein:

said step of authenticating comprises the steps of;

receiving entered user data;

accessing user identity profile information for a Directory Server; and

comparing said entered user data with said user identity profile information.

21. The method of claim 1, wherein:

said network is the Internet.

22. The method of claim 1, wherein:

said resource is a web page.

23. The method of claim 1, wherein:

said resource is an application.

24. The method of claim 1, wherein:

said step of redirecting is performed by a Web Server plug-in.

25. The method of claim 24, wherein:

said plug-in is an NSAPI Web Server plug-in.

26. The method of claim 24, wherein:

said plug-in is an ISAPI Web Server plug-in.

27. 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:

receiving a user request for a protected resource, said resource is in a first domain;

redirecting said request to a second domain; and

authenticating said user at said second domain, wherein said authenticating includes;

receiving user data at said second domain, said user data is received at said second domain from said user,

accessing user identify profile information for said user from a Directory Server, said user identity profile information including a plurality of attributes having attribute values, wherein at least one of said attribute values includes information other than an authentication certificate, and

comparing said received user data with said user identity profile information, said comparing includes comparing said received user data with said information other than an authentication certificate.

28. One or more processor readable storage devices according to claim 27, wherein said method further comprises the step of:

determining whether said first and second domains reside on a single Web Server.

29. One or more processor readable storage devices according to claim 27, wherein said method further comprises the step of:

transmitting an authentication cookie for said second domain to said user after said step of authentication.

30. One or more processor readable storage devices according to claim 29, wherein said method further comprises the step of:

authorizing said user for said resource.

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

redirecting a subsequent resource request for a resource in a third domain to said second domain;

transmitting said cookie to said second domain; and

authenticating said user at said second domain using said cookie.

32. One or more processor readable storage devices according to claim 27, wherein:

said second domain is a preferred host.

33. One or more processor readable storage devices according to claim 29, wherein:

said cookie is encrypted.

34. One or more processor readable storage devices according to claim 27, wherein:

said system is an Access Management System.

35. One or more processor readable storage devices according to claim 27, wherein:

said system is an Access System.

36. One or more processor readable storage devices according to claim 35, wherein:

said Access System includes an access management system and an identity management system.