Method and apparatus for secure cross-site scripting

1. A method comprising:

causing, at least in part, reception of an initiation request from at least a first inline frame of at least one web page, the initiation request specifying a developer identifier associated with a domain of the at least one web page;

determining a callback resource identifier based on the developer identifier; and

determining to cause, at least in part, transmission of the callback resource identifier to the at least the first inline frame for use in creation of at least a second inline frame associated with the at least the first inline frame.

2. A method of claim 1 , wherein the initiation request further specifies a secure user identifier, the method further comprising:

associating the initiation request with an account based on the secure user identifier;

generating a token based on the secure user identifier; and

determining to cause, at least in part, transmission of the token to the at least the first inline frame for use in the creation of the at least the second inline frame.

3. A method of claim 2 , further comprising:

causing, at least in part, reception of a user identifier and authentication information;

generating the secure user identifier based on the user identifier and the authentication information; and

determining to cause, at least in part, transmission of the secure user identifier to the at least one web page.

4. A method of claim 2 , further comprising:

causing, at least in part, reception of another request from the at least the first inline frame via a connection based, at least in part, on the token, wherein the request is for access to service data; and

authenticating the token to allow access to the service data.

5. A method of claim 1 , wherein the callback resource identifier further includes a revocation status of the developer identifier.

6. An apparatus comprising:

at least one processor; and

at least one memory including computer program code,

the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to perform at least the following,

cause, at least in part, reception of an initiation request from at least a first inline frame of at least one web page, the initiation request specifying a developer identifier associated with a domain of the at least one web page;

determine a callback resource identifier based on the developer identifier; and

determine to cause, at least in part, transmission of the callback resource identifier to the at least the first inline frame for use in creation of at least a second inline frame associated with the at least the first inline frame.

7. An apparatus of claim 6 , wherein the initiation request further specifies a secure user identifier, and wherein the apparatus is further caused, at least in part, to:

associate the initiation request with an account based on the secure user identifier;

generate a token based on the secure user identifier; and

determine to cause, at least in part, transmission of the token to the at least the first inline frame for use in the creation of the at least the second inline frame.

8. An apparatus of claim 7 , wherein the apparatus is further caused, at least in part, to:

cause, at least in part, reception of a user identifier and authentication information;

generate the secure user identifier based on the user identifier and the authentication information; and

determine to cause, at least in part, transmission of the secure user identifier to the at least one web page.

9. An apparatus of claim 7 , wherein the apparatus is further caused, at least in part, to:

cause, at least in part, reception of another request from the at least the first inline frame via a connection based, at least in part, on the token, wherein the request is for access to service data; and

authenticate the token to allow access to the service data.

10. An apparatus of claim 6 , wherein the callback resource identifier further includes a revocation status of the developer identifier.

11. A method comprising:

causing, at least in part, creation of an inline frame within a web page of a first domain associated with a developer identifier, wherein the inline frame is associated with a second domain;

determining to cause, at least in part, transmission of the developer identifier to a platform associated with the second domain;

causing, at least in part, reception at the inline frame of a callback resource identifier from the platform, wherein the callback resource identifier is determined based, at least in part, on the developer identifier; and

causing, at least in part, creation of another inline frame within the inline frame, wherein the other inline frame is based, at least in part, on the callback resource identifier.

12. A method of claim 11 , wherein the content of the other inline frame is associated with the first domain.

13. A method of claim 12 , wherein the other inline frame includes service data, the method further comprising:

causing, at least in part, accessing the service data at the web page of the first domain, wherein the service data includes a token for authenticating communications to the second domain.

14. A method of claim 12 , further comprising:

determining content information to send to the second domain;

generating another resource identifier based, at least in part, on the token and the content information; and

updating a location identifier of the inline frame with the other resource identifier to send the content information.

15. A method of claim 11 , wherein the content of the other inline frame is associated with a third domain different from the first domain and wherein the other inline frame includes service data, the method further comprising:

detecting an attempt to access the service data at the web page; and

returning an error message associated with the attempt.

16. An apparatus comprising:

at least one processor; and

at least one memory including computer program code,

the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to perform at least the following,

cause, at least in part, creation of an inline frame within a web page of a first domain associated with a developer identifier, wherein the inline frame is associated with a second domain;

determine to cause, at least in part, transmission of the developer identifier to a platform associated with the second domain;

cause, at least in part, reception at the inline frame of a callback resource identifier from the platform, wherein the callback resource identifier is determined based, at least in part, on the developer identifier; and

cause, at least in part, creation of another inline frame within the inline frame, wherein the other inline frame is based, at least in part, on the callback resource identifier.

17. An apparatus of claim 16 , wherein the content of the other inline frame is associated with the first domain.

18. An apparatus of claim 17 , wherein the other inline frame includes service data, and wherein the apparatus is further caused, at least in part, to:

cause, at least in part, accessing the service data at the web page of the first domain, wherein the service data includes a token for authenticating communications to the second domain.

19. An apparatus of claim 17 , wherein the apparatus is further caused, at least in part, to:

determine content information to send to the second domain;

generate another resource identifier based, at least in part, on the token and the content information; and

update a location identifier of the inline frame with the other resource identifier to send the content information.

20. An apparatus of claim 16 , wherein the content of the other inline frame is associated with a third domain different from the first domain and wherein the other inline frame includes service data, and wherein the apparatus is further caused, at least in part, to:

detect an attempt to access the service data at the web page; and

return an error message associated with the attempt.