Method and system for authenticating a surrounding web application by a web application that is to be embedded

1. A method for authenticating a surrounding first Web application by a second Web application before embedding the second Web application in the surrounding first Web application, the surrounding first Web application being executed in a browser, the second Web application after being embedded in the surrounding first Web application being executed in a separate execution and display area of the surrounding first Web application, the surrounding first Web application being provided by at least one first Web server, and the second Web application subsequent to being embedded in the surrounding first Web application being provided by at least one second Web server, the method comprising:

authenticating the surrounding first Web application to the second Web application before embedding the second Web application in the first Web application, a first key utilized during the authentication being stored in the at least one first Web server, the first key utilized during the authentication being allocated to the surrounding first Web application the first key being utilized to sign the authentication messages utilized by the at least one second Web server, and the first key remaining within the at least one first Web server at all times;

exchanging the authentication messages signed via the first key between the at least one first Web server and the at least one second Web server via the browser; and

activating the second Web application only in an event of successful authentication or authorization.

2. The method as claimed in claim 1 , wherein an inline frame (“iframe”) in a Web window of the surrounding first Web application serves as the separate execution and display area.

3. The method as claimed in claim 1 , wherein an interface is utilized to exchange authentication messages between the separate execution and display area and the surrounding first Web application.

4. The method as claimed in claim 2 , wherein an interface is utilized to exchange authentication messages between the separate execution and display area and the surrounding first Web application.

5. The method as claimed in claim 1 , wherein a domain of the first Web application is determined during the authentication or authorization; and wherein the activation is performed only if a domain provided for this purpose has been determined.

6. The method as claimed in claim 1 , wherein the second Web application that is to be embedded includes a basic part having modules for communicating with at least one of (i) the first Web application and (ii) the browser, and for communicating with the second Web server;

wherein the second Web application that is to be embedded additionally includes an application-specific application part;

wherein the basic part is loaded into the separate execution and display area before the authentication or authorization is started; and

wherein the application part is loaded into the separate execution and display area and started or placed into operation for the activation.

7. The method as claimed in claim 6 , wherein the second Web application that is to be embedded is authenticated to the surrounding first Web application in a similar manner;

wherein a second key allocated to the second Web application is stored on the second Web server and is utilized by the first Web server via exchange of authentication messages via the browser; and

wherein the second Web application is activated only in the event of successful authentication or authorization of the second Web application that is to be embedded.

8. The method as claimed in claim 7 , wherein the basic part is loaded into the separate execution and display area and is started before the authentication or authorization of the first Web application; and

wherein the first Web application is authenticated or its authorization is checked before loading the application part into the separate execution and display area.

9. The method as claimed in claim 1 , wherein before the authentication or authorization of at least one of (i) the first Web application and (ii) the second Web application, a secure communication link, based on the HTTPS protocol, is established in each case between the first Web server and the first Web application and between the second Web application and the second Web server.

10. The method as claimed in patent claim 9 , wherein the secure communication link is based on the Hypertext Transfer Protocol, established in each case between the first Web server and the first Web application and between the second Web application and the second Web server.

11. A system for authenticating a surrounding first Web application by a second Web application before embedding the second Web application in the surrounding first web application, the system comprising:

a computer;

a browser running on the computer for executing the surrounding first Web application, the second application that is to be embedded being executed in the surrounding first web application in a separate execution and display area of the surrounding first Web application;

a first Web server for providing the surrounding first Web application; and

a second Web server for providing the second Web application that is to be embedded in the surrounding first web application;

wherein the system is configured to:

authenticate the surrounding first Web application to the second Web application before embedding the second Web application in the surrounding first web application, a first key utilized during the authentication being stored in the at least one first Web server, the first key utilized during the authentication being allocated to the surrounding first Web application, the first key being utilized to sign authentication messages utilized by the at least one second Web server, and the first key remaining within the first Web server at all times;

exchange the authentication messages signed via the first key between the first Web server and the second Web server via the browser; and

activate the second Web application only in an event of successful authentication or authorization.