Methods and systems for imaging device credential submission and consolidation

• US 8,006,292 B2
• Filed: 07/29/2005
• Issued: 08/23/2011
• Est. Priority Date: 10/08/2004
• Status: Expired due to Fees

• Current Assignee: Sharp Kabushiki Kaisha (Hon Hai Precision Industry Co., Ltd.)
• Original Assignee: Sharp Laboratories of America Incorporated (Hon Hai Precision Industry Co., Ltd.)
• Inventors: Lovat, David J., Zhang, Hanzhong
• Primary Examiner(s): Simitoski; Michael J
• Application Number:
  US11/192,868
• Publication Number:
  US 20060077434A1
• Time in Patent Office: 2,216 Days
• Field of Search: 726/8, 358/1.15, 380/51, 713/186, 705/18
• US Class Current: 726/8
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04N 1/00204 with a digital computer or a digital computer system, e.g. an internet server programmed control between transmitter and receiver or between image input and image output device H04N1/32561
• CPC Class Codes: H04N 1/00244 with a server, e.g. an internet server fax-servers or the like for store and forward H04N1/324
• CPC Class Codes: H04N 1/00352 Input means H04N1/00411 takes precedence; input arrangements for computers G06F3/00
• CPC Class Codes: H04N 1/00464 using browsers, i.e. interfaces based on mark-up languages
• CPC Class Codes: H04N 1/00503 Customising to a particular machine or model, machine function or application
• CPC Class Codes: H04N 2201/0039 Connection via a network
• CPC Class Codes: H04N 2201/0049 By wire, cable or the like
• CPC Class Codes: H04N 2201/0075 by a user operated remote control device, e.g. receiving instructions from a user via a computer terminal or mobile telephone handset
• CPC Class Codes: H04N 2201/0094 Multifunctional device, i.e. a device capable of all of reading, reproducing, copying, facsimile transception, file transception

Abstract

Embodiments of the present invention comprise systems, methods and devices for eliminating multiple submission of user credential data in a system with multiple distinct restricted sub-systems wherein a unique credential is required for each sub-system.

Claims

1. A method for providing single-credential access to multiple, distinct, restricted services wherein a unique credential is required for each service, said method comprising:

displaying sign-on credential menu content on a display of said IDev;

receiving user input comprising a sign-on credential at a user interface (UI) of said IDev;

sending said sign-on credential to a single-sign-on server application (SSOSA) from said IDev;

receiving a sign-on token, at said IDev, from said SSOSA, wherein said sign-on token is related to a user credential data table, which relates said sign-on token to a plurality of unique sign-on credentials for each of a plurality of IDev functions, services or applications and wherein said user credential data table and said credential are stored and maintained by said single-sign-on server application (SSOSA);

sending said sign-on token to one of said plurality of IDev functions, services or applications for exchange by said one of said plurality of IDev functions, services or applications for a corresponding one of said unique sign-on credentials maintained at said SSOSA; and

receiving access, at said IDev, to said one of said plurality of IDev functions, services or applications in response to said exchange.

2. A method as described in claim 1 wherein said SSOSA is an application running on a remote computing device (RCD).

3. A method as described in claim 1 wherein said service is an application running on a remote computing device (RCD).

4. A method as described in claim 1 wherein said service is a local IDev function.

5. A method as described in claim 1 wherein said sending user sign-on credentials is accomplished with an XML/SOAP message.

6. A method for providing single-credential access to multiple, distinct, restricted services wherein a unique credential is required for each service, said method comprising:

displaying sign-on credential menu content on a display of said IDev;

receiving user input comprising a sign-on credential at a user interface (UI) of said IDev;

sending said sign-on credentials to a single-sign-on server application (SSOSA) from said IDev;

receiving a sign-on token, at said IDev, from said SSOSA when said user credential complies with authentication restrictions, wherein said sign-on token is related to a user credential data table, which relates said sign-on token to a plurality of unique sign-on credentials for each of a plurality of IDev functions, services or applications and wherein said user credential data table and said credential are stored and maintained by said single-sign-on server application (SSOSA);

requesting access to a service by sending said sign-on token to said service, wherein receipt of said sign-on token causes said service to forward said sign-on token to said SSOSA and exchange said sign-on token for the unique sign-on credentials maintained at said SSOSA that correspond to said service; and

receiving access to said service based on said unique sign-on credentials stored in said SSOSA.

7. A method as described in claim 6 wherein said service is an IDev function.

8. A method as described in claim 6 wherein said service is a remote application.

9. A method as described in claim 6 wherein said requesting is accomplished with an XML/SOAP message.

10. An apparatus for eliminating multiple submission of user credential data in a system with multiple, distinct, restricted services wherein a unique credential is required for each service, said apparatus comprising:

an IDev display for displaying sign-on credential menu content on a display of said IDev;

an IDev user interface (UI) for receiving user input comprising a sign-on credential at said IDev;

a credential sender for sending said user sign-on credentials to a single-sign-on server application (SSOSA);

a token receiver for receiving a sign-on token from said SSOSA when said user sign-on credential complies with authentication restrictions, wherein said token is related to a user credential data table, which relates said sign-on token to a plurality of unique sign-on credentials for each of a plurality of IDev functions, services or applications and wherein said user credential data table and said unique sign-on credentials are stored and maintained by said single-sign-on server application (SSOSA);

a token sender for sending said sign-on token to one of said plurality of IDev functions, services or applications, wherein said sending causes said one of said plurality of IDev functions, services or applications to exchange said sign-on token for a corresponding one of said unique user service credentials maintained at said SSOSA, thereby gaining access to said one of said plurality of IDev functions, services or applications;

a service connection receiver for receiving access to said one of said plurality of IDev functions, services or applications; and

token storage for storing said sign-on token at said IDev.

11. An apparatus as described in claim 10 wherein said SSOSA is an application running on a remote computing device (RCD).

12. An apparatus as described in claim 10 wherein said service is an application running on a remote computing device (RCD).

13. An apparatus as described in claim 10 wherein said service is a local IDev function.