IP Library Granted Patent US 9,124,575
Granted Patent B2
US 9,124,575 · App. 14/092,283 · Granted Sep 1, 2015

Self-single sign-on

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,124,575
App. No.
14/092,283
Granted
Sep 1, 2015
Kind
B2
Abstract

Techniques are described for providing sign-on within a trusted environment across multiple application servers. For example, a method can be provided for a single sign-on within a trusted environment across application servers. The method comprises, by a first application operating within the trusted environment, connecting to a first application server via a first access channel, and retrieving an authentication token from the first application server via the first access channel. The method further comprises, by a second application operating within the trusted environment, connecting to a second application server via a second access channel, and authenticating with the second application server with the authentication token.

Claims (42)

1. A method of providing a single sign-on within a trusted environment across application servers comprising:

by a first application operating within the trusted environment;

connecting to a first application server via a first access channel;

retrieving an authentication token from the first application server via the first access channel;

connecting to a second application server via a fourth access channel; and

authenticating with the second application server with the authentication token; and

by a second application operating within the trusted environment:

receiving the authentication token from the first application server via a third access channel;

connecting to the second application server via a second access channel; and

authenticating with the second application server with the authentication token.

2. The method of claim 1 , wherein connecting to the first application server comprises authenticating a user with the first application server using, at least in part, a username and password.

3. The method of claim 1 , wherein the authentication token comprises a user name and a certificate of an issuing system of the first application server.

4. The method of claim 1 , wherein the authentication token includes a validity period.

5. The method of claim 1 , wherein the first access channel and the second access channel use different network protocols.

6. The method of claim 1 , wherein the first application server comprises a web server, and wherein the first access channel comprises a network connection between the first application and the web server using a web server protocol.

7. The method of claim 1 , wherein the second application server comprises a database server, and wherein the second access channel comprises a network connection between the second application and the database server that communicates using at least one of an Open Database Connectivity (ODBC) application programming interface (API) and a Java Database Connectivity (JDBC) API.

8. The method of claim 1 , further comprising passing the authentication token from the first application to the second application via a fifth access channel between the first application and the second application.

9. A computing environment comprising one or more computer servers adapted to provide a single sign-on within a trusted environment across application servers, comprising:

a first application server operating within the trusted environment, the first application server configured to perform operations comprising:

receiving sign-on information via a first access channel from a first application; and

returning an authentication token to the first application via the first access channel;

connecting to a second application via a third access channel; and

returning the authentication token to the second application via the third access channel; and

a second application server operating within the trusted environment, the second application server configured to perform operations comprising:

receiving the authentication token via a second access channel from the second application;

authenticating the second application with the authentication token; and

receiving the authentication token from the first application via a fourth access channel.

10. The computing device of claim 9 , wherein the sign-on information is used to create the authentication token.

11. The computing device of claim 9 , wherein the authentication token comprises a user name and a certificate of an issuing system of the first application server.

12. The computing device of claim 9 , wherein the first application server and the second application server are on a computing platform, and the computing platform generates the authentication token.

13. The computing device of claim 9 , wherein the first application server comprises a web server, and wherein the first access channel comprises a network connection between the first application and the web server using a web server protocol.

14. The computing device of claim 9 , wherein the second application server is a database server, and wherein the second access channel comprises a network connection between the second application and the database server that communicates using at least one of an Open Database Connectivity (ODBC) application programming interface (API) and a Java Database Connectivity (JDBC) API.

15. The computing device of claim 9 , wherein the first application is on one device and the second application is on a different device.

16. A non-transitory computer-readable medium storing computer-executable instructions for providing a single sign-on within a trusted environment across application servers comprising:

by a first application server operating within the trusted environment:

connecting to a first application using an authentication method via a first access channel;

connecting to a second application via a second access channel;

passing an authentication token to the second application via the second access channel; and

passing the authentication token to the first application via the first access channel; and

by a second application server operating within the trusted environment:

receiving the authentication token from the second application via a third access channel; and

receiving the authentication token from the first application via a fourth access channel.

Assignments (2)
CHANGE OF NAME Recorded Aug 26, 2014
From: SAP AG
To: SAP SE
Reel/Frame 033625/0223 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 4, 2014
From: FRIEDMANN, BJOERN; KITTEL, MARTIN; MACK, HOLGER; ZORN, SASCHA
To: SAP AG
Reel/Frame 032347/0681 →