Privacy-aware ID gateway
View Patent ↗A method includes, for a first user having been authenticated on a first application with a first user identification (ID) using a first ID federation between the first application and a federation server, determining that the first user is authorized to access information of a second user on a second application based on the first user ID, the second user being associated with a second user ID, and sending a second authentication request for authenticating the first user to the second application with the second user ID using a second ID federation between the federation server and the second application.
1. A method comprising:
for a first user having been authenticated on a first application with a first user identification (ID) using a first ID federation between the first application and a federation server, determining that the first user is authorized to access information of a second user on a second application based on the first user ID, the second user being different from the first user and being associated with a second user ID obtained based on the first user ID; and
sending a second authentication request for authenticating the first user to the second application with the second user ID using a second ID federation between the federation server and the second application.
2. The method according to claim 1 , wherein:
receiving the first authentication request further includes receiving an identification of the second application with the first authentication request; and
sending the second authentication request further includes sending authority information of the first user ID.
3. The method according to claim 1 , wherein the first user ID includes at least one of a user ID of the first user, and an identification of the first application.
4. The method according to claim 1 , wherein determining that the first user is authorized to access the information on the second user further includes:
obtaining condition information defining a condition; and
determining that the first user ID, the second application, and the second user ID satisfy the condition.
5. The method according to claim 4 , wherein the condition information includes at least one of a time when the information of the second user ID is recorded on the second application, and a record of the information of the second user ID on the second application.
6. The method according to claim 4 , further comprising:
receiving an authorization of the second user from a client computer of the second user; and
updating the condition information to reflect the authorization of the second user.
7. The method according to claim 6 , wherein the first authentication request is received from the first application.
8. The method according to claim 1 , further comprising receiving an authorization of the second user from the first application.
9. The method according to claim 8 , wherein the authorization of the second user includes a password input by the second user.
10. A method comprising:
receiving, from a first application, a first authentication request for authenticating a first user, the first user having been authenticated on the first application with a first user identification (ID) using a first ID federation between the first application and a federation server;
determining that the first user is authorized to access information of a second user on a second application based on the first user ID, the second user being different from the first user and being associated with a second user ID obtained based on the first user ID; and
sending a second authentication request for authenticating the first user to the second application with the second user ID using a second ID federation between the federation server and the second application.
11. The method according to claim 10 , wherein:
receiving the first authentication request further includes receiving an identification of the second application with the first authentication request; and
sending the second authentication request further includes sending authority information of the first user ID.
12. The method according to claim 10 , wherein the first user ID includes at least one of a user ID of the first user, and an identification of the first application.
13. The method according to claim 10 , wherein determining that the first user is authorized to access the information on the second user further includes:
obtaining condition information defining a condition; and
determining that the first user ID, the second application, and the second user ID satisfy the condition.
14. The method according to claim 13 , wherein the condition information includes at least one of a time when the information of the second user ID is recorded on the second application, and a record of the information of the second user ID on the second application.
15. The method according to claim 13 , further comprising:
receiving an authorization of the second user including a password input by the second user, the authorization being received from a client computer of the second user or the first application; and
updating the condition information to reflect the authorization of the second user.
16. A method comprising:
receiving, from a first application, a first authentication request for authenticating a first user, the first user having been authenticated on the first application with a first user identification (ID) using a first ID federation between the first application and a federation server;
determining that the first user is authorized to access information of a second user on a second application based on the first user ID, the second user being different from the first user and being associated with a second user ID obtained based on the first user ID, including:
obtaining condition information defining a condition; and
determining that the first user ID, the second application and the second user ID satisfy the condition; and
sending a second authentication request for authenticating the first user to the second application with the second user ID using a second ID federation between the federation server and the second application.
17. The method according to claim 16 , wherein:
receiving the first authentication request further includes receiving an identification of the second application with the first authentication request; and
sending the second authentication request further includes sending authority information of the first user ID.
18. The method according to claim 16 , wherein the first user ID includes at least one of a user ID of the first user, and an identification of the first application.
19. The method according to claim 16 , wherein the condition information includes at least one of a time when the information of the second user ID is recorded on the second application, and a record of the information of the second user ID on the second application.
20. The method according to claim 16 , further comprising:
receiving an authorization of the second user including a password input by the second user, the authorization being received from a client computer of the second user or the first application; and
updating the condition information to reflect the authorization of the second user.