Third party application centralized safety management method and system and corresponding communication system

Abstract

The invention provides a third party application centralized safety management method and a system and a communication system comprising more than one authorization server, more than one asset server, a user agent, a third party application and a centralized safety management system, wherein the third party application centralized safety management system is responsible for confirming safety of the third party application, conducting digital signature to the third party application, sending authentication credentials capable of enabling the centralized safety management system to confirm the third party application. The method includes: the third party application sends identity, authentication credentials and access permission to the centralized safety management system in a distinguishable method; after successful confirmation, the centralized safety management system sends the identity, the authentication credentials and the access permission to the authorization server; if the access permission is valid, the authorization server sends access token for accessing to a protected resource to the third party application through the centralized safety management system.

Description

technical field [0001] The present invention relates to the communication field, and in particular, relates to a technology for centralized security management of third-party applications / clients that want to access user's protected resources. Background technique [0002] At present, the integration between Internet services has become an inevitable trend. In order to provide better services to their users, many service providers allow third-party applications / clients to provide users with more applications by calling an "open network API (Application Programming Interface)". The core issue of an open platform is user authentication, authorization, and third-party applications / clients safely using open network API interfaces. For users, it is generally not expected that a third party will directly use their user name and password to access the user's protected network resources, unless the two parties have a strong trust relationship. The OAuth (Open Authorization) protoc...

AI Technical Summary

Problems solved by technology

[0017] 3. Before the user authorizes the third-party application / client, the user must be authenticated by the authorization server, and the user may also need to authenticate the authorization server;

[0024] In addition, since there are many third-party applications / clients, some of which may be developed and provided by individuals, it is possible for attackers to develop malicious network APIs to abuse network APIs for illegal access to user resources

Images