Source: http://patents.com/us-9832185.html
Timestamp: 2018-07-19 04:21:06
Document Index: 26894873

Matched Legal Cases: ['Application No. 08732419', 'Application No. 200880012470', 'Application No. 200880012470', 'Application No. 200880012470', 'Application No. 200880012470', 'Application No. 2010', 'Application No. 2010', 'Application No. 08732419', 'Application No. 60']

US Patent # 9,832,185. Request-specific authentication for accessing web service resources - Patents.com
United States Patent 9,832,185
McMurtry , et al. November 28, 2017
Family ID: 1000002978379
15/412,866
US 20170134368 A1 May 11, 2017
14936362 Nov 9, 2015 9590994
14165133 Nov 10, 2015 9183366
Current CPC Class: H04L 63/083 (20130101); H04L 63/06 (20130101); H04L 63/10 (20130101); H04L 63/0861 (20130101); H04L 63/0869 (20130101)
7516483 April 2009 Brennan
2005/0204168 September 2005 Johnston et al.
2005/0228984 October 2005 Edery et al.
2007/0005967 January 2007 Mister
2007/0038525 February 2007 Waldvogel et al.
2008/0229251 September 2008 Davies
"Non Final Office Action Issued in U.S. Appl. No. 14/936,362", dated Jun. 17, 2016, 28 pages. cited by applicant .
"Notice of Allowance Issued in U.S. Appl. No. 14/936,362", dated Oct. 21, 2016, 16 pages. cited by applicant .
"Web Services Policy 1.2--Attachment (WS-Policy Attachment)", Retrieved from <<https://www.w3.org/Submission/WS-Policy/>>, Apr. 25, 2006, 16 Pages. cited by applicant .
"Supplementary Search Report Issued in European Patent Application No. 08732419.0", dated Apr. 15, 2014, 7 Pages. cited by applicant .
"Final Office Action Issued in U.S Appl. No. 12/024,901", dated May 12, 2011, 21 Pages. cited by applicant .
"Final Office Action Issued in U.S. Appl. No. 12/024,901", dated May 24, 2012, 28 Pages. cited by applicant .
"Non-Final Office Action Issued in U.S. Appl. No. 12/024,901", dated Sep. 21, 2011, 29 Pages. cited by applicant .
"Non-Final Office Action Issued in U.S. Appl. No. 12/024,901", dated Dec. 6, 2010, 15 Pages. cited by applicant .
"Notice of Allowance Issued in U.S. Appl. No. 12/024,901", dated Oct. 7, 2013, 13 Pages. cited by applicant .
"Notice of Allowance Issued in U.S. Appl. No. 12/024,901", dated Jun. 26, 2013, 13 Pages. cited by applicant .
"Notice of Allowance Issued in U.S. Appl. No. 12/024,901", dated Jun. 19, 2013, 2 Pages. cited by applicant .
"Notice of Allowance Issued in U.S. Appl. No. 12/024,901", dated Apr. 24, 2013, 18 Pages. cited by applicant .
"Final Office Action Issued in U.S. Appl. No. 14/165,133", dated Mar. 3, 2015, 23 Pages. cited by applicant .
"Non-Final Office Action Issued in U.S. Appl. No. 14/165,133", dated Jun. 18, 2014, 23 Pages. cited by applicant .
"Notice of Allowance Issued in U.S. Appl. No. 14/165,133", dated Jun. 25, 2015, 21 Pages. cited by applicant .
"First Office Action Issued in Chinese Patent Application No. 200880012470.2", dated May 25, 2011, 17 Pages. cited by applicant .
"Office Action Issued in Chinese Patent Application No. 200880012470.2", dated Jun. 19, 2012, 25 Pages. cited by applicant .
"Notice of Reexamination Issued in Chinese Patent Application No. 200880012470.2", dated Dec. 17, 2014, 11 Pages. cited by applicant .
"Second Office Action Issued in Chinese Patent Application No. 200880012470.2", dated Jan. 18, 2012, 19 Pages. cited by applicant .
"Notice of Allowance Issued in Japanese Patent Application No. 2010-504132", dated Jun. 28, 2013, 6 Pages. cited by applicant .
"Office Action Issued in Japanese Patent Application No. 2010-504132", dated Mar. 1, 2013, 9 Pages. cited by applicant .
Angal, et al., "Building Identity-Enabled Web Services", Retrieved from <<http://web.archive.org/web/20070607151743/http://developers.sun.c- om/identity/reference/techart/id-enabled-ws.html>>, Oct. 18, 2005, 10 Pages. cited by applicant .
O'Gorman, et al., "Comparing Passwords, Tokens, and Biometrics for User Authentication", In Proceedings of the IEEE, vol. 91, Issue: Dec. 12, 2003, 20 Pages. cited by applicant .
"International Search Report & Written Opinion Issued in PCT Application No. PCT/US2008/057375", dated Aug. 21, 2008, 12 Pages. cited by applicant .
Wong, et al., "A Web Services Security Testing Framework", In Sift Special Publication, Information Security Services, Version 1.00, Oct. 11, 2006, 103 Pages. cited by applicant .
European Patent Office, Office Action for European Patent Application No. 08732419.0, dated Feb. 28, 2017, 5 Pages. cited by applicant.
This application is a Continuation of U.S. application Ser. No. 14/936,362, filed on Nov. 9, 2015, which is a Continuation of U.S. Pat. No. 9,183,366, filed on Jan. 27, 2014, which is a Continuation of U.S. Pat. No. 8,656,472, filed on Feb. 1, 2008, which claims priority to U.S. Provisional Application No. 60/912,986, filed on Apr. 20, 2007, titled "MESSAGE-SPECIFIC AUTHENTICATION PROTOCOL FOR WEB SERVICES," the disclosures of which are hereby incorporated by reference in their entireties. To the extent appropriate, a claim of priority is made to each of the above disclosed applications.
1. A computing system for controlling access to a protected Web service resource, the computing system comprising: a communication device for communicating across a communication network; a processor communicatively connected to the communication device; and memory storing program instructions, which when executed by the processor cause the computing system to: receive a first request from a client to access the protected Web service resource from the communication network; determine that the client has been authenticated according to a first factor; grant the first request to access the protected Web service resource based on authentication according to the first factor; receive a second request from the client to access the protected Web service resource from the communication network; deny the second request to access the protected Web service resource based on the authentication according to the first factor being insufficient to grant the second request, including to send a message to the client directing the client to an authentication service to be authenticated according to a second factor; determine that the client has been authenticated according to the second factor, and grant the second request to access the protected Web service resource based on authentication according to the second factor including an evaluation of an authentication token.
5. The computing system of claim 4, wherein the program instructions that determine that the client has been authenticated further causes the computing system to: decrypt the first authentication token with a public key of the authentication service; and determine that a claim made by the authentication service in the first authentication token satisfies a condition for access.
7. A method of controlling access to a protected Web service resource, the method comprising: receiving at a processing device a first request from a client to access the protected Web service resource from the communication network; determining, using the processing device, that the client has been authenticated according to a first factor; granting the first request to access the protected Web service resource, using the processing device, based on authentication according to the first factor; receiving a second request from the client to access the protected Web service resource from the communication network; denying the second request to access the protected Web service resource, using the processing device, based on the authentication according to the first factor being insufficient to grant the second request, wherein denying the second request further comprises sending a message to the client directing the client to an authentication service to be authenticated according to a second factor; determining that the client has been authenticated according to the second factor; and granting the second request to access the protected Web service resource based on authentication according to the second factor including an evaluation of an authentication token.
11. The method of claim 10, wherein determining that the client has been authenticated comprises: decrypting the first authentication token with a public key of the authentication service; and determining that a claim made by the authentication service in the first authentication token satisfies a condition for access.
13. A computing system for controlling access to a protected Web service resource, the computing system comprising: a communication device for communicating across a communication network; a processor communicatively connected to the communication device; and memory storing program instructions, which when executed by the processor cause the computing system to: receive a first request from a client to access the protected Web service resource from the communication network; receive a first authentication token from the client after the client has been authenticated by an authentication service according to the first factor; determine that the client has been authenticated according to a first factor using the first authentication token, wherein the program instructions that determine that the client has been authenticated according to the first factor further causes the computing system to: decrypt the first authentication token with a public key of the authentication service; and determine that a claim made by the authentication service in the first authentication token satisfies a condition for access; grant the first request to access the protected Web service resource based on authentication according to the first factor; receive a second request from the client to access the protected Web service resource from the communication network; deny the second request to access the protected Web service resource based on the authentication according to the first factor being insufficient to grant the second request; determine that the client has been authenticated according to the second factor; and grant the second request to access the protected Web service resource based on authentication according to the second factor.
19. A method of controlling access to a protected Web service resource, the method comprising: receiving at a processing device a first request from a client to access the protected Web service resource from the communication network; receiving at the processing device a first authentication token from the client after the client has been authenticated by an authentication service according to the first factor; determining, using the processing device, that the client has been authenticated according to a first factor using the first authentication token, by: decrypting the first authentication token with a public key of the authentication service; and determining that a claim made by the authentication service in the first authentication token satisfies a condition for access; granting the first request to access the protected Web service resource, using the processing device, based on authentication according to the first factor; receiving a second request from the client to access the protected Web service resource from the communication network; denying the second request to access the protected Web service resource, using the processing device, based on the authentication according to the first factor being insufficient to grant the second request; determining that the client has been authenticated according to a second factor; and granting the second request to access the protected Web service resource based on authentication according to the second factor.
TABLE-US-00001 TABLE 1 Authentication Challenge Schema <?xml version=`1.0`encoding=`utf-8`?> <xs:schema elementFormDefault=`qualified` targetNamespace=`http://schemas.microsoft.com/2006/11/IdentityManagement- ` xmlns:xs=`http://www.w3.org/2001/XMLSchema` xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/08/addressing xmlns:idm=`http://schemas.microsoft.com/2006/11/IdentityManagement`> <xs:import namespace=`http://schemas.xmlsoap.org/ws/2004/08/addressing`/> <xs:complexType name=`AuthenticationChallengeType`> <xs:sequence> <xs:element name=`Challenge` nillable=`true` minOccurs=`0`> <xs:complexType> <xs:sequence> <xs:any minOccurs=`0` processContents=`lax` /> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> <xs:element name=`AuthenticationChallenge` nillable=`true` type=`idm:AuthenticationChallengeType` /> </xs:schema>
TABLE-US-00002 TABLE 2 Authentication Challenge Response Schema <?xml version=`1.0` encoding=`utf-8`?> <xs:schema elementFormDefault=`qualified` targetNamespace=`http://schemas.microsoft.com/2006/11/IdentityManagement- ` xmlns:xs=`http://www.w3.org/2001/XMLSchema` xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/08/addressing xmlns:idm=`http://schemas.microsoft.com/2006/11/IdentityManagement`> <xs:import namespace=`http://schemas.xmlsoap.org/ws/2004/08/addressing`/> <xs:complexType name=`AuthenticationChallengeResponseType`> <xs:sequence> <xs:element name=`Response` nillable=`true` minOccurs=`0`> <xs:complexType> <xs:sequence> <xs:any minOccurs=`0` processContents=`lax` /> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> <xs:element name=`AuthenticationChallengeResponse` nillable=`true` type=`idm:AuthenticationChallengeResponseType` /> </xs:schema>
Previous Patent US 9,832,184 | Next Patent US 9,832,186