Method and system for discovering and logging new microservices for a platform for unified governance of a plurality of intensive computing solutions

Patent metadata

Field	Value
Publication number	US-2021306321-A1
Application number	US-202117213566-A
Country	US
Kind code	A1
Filing date	Mar 26, 2021
Priority date	Mar 27, 2020
Publication date	Sep 30, 2021
Grant date	—

Abstract

A method (800) for logging microservices in a platform for unified governance of a plurality of intensive computing solutions (70) comprising: a proxy microservice (20), a token security microservice (30), at least one security repository (35,36,37), a logging module (90), a service register (91), and comprising the steps of:Reception (820) of a join request from a new microservice (60),Verification (830) of the unique identifier of the new microservice (IDMS),Generation (840) of an authentication token and transmission to the new microservice,Reception (850) of a logging request from a new microservice, comprising data that provides access to the resources of the new microservice and the generated authentication token,Verification (860) of the authentication token with the token security microservice (30),Logging (870), when the authentication token is validated, data that provides access to the resources of the new microservice on the service register (91).

First claim

1 - 10 . (canceled)

11 . A method ( 800 ) for logging microservices in a unified governance platform of a plurality of intensive computing solutions ( 70 ), comprising at least two solutions selected from:
a first server comprising a high performance computing server ( 71 ), a second server dedicated to supervised or unsupervised learning ( 72 ), and a third server dedicated to quantum computations ( 73 );
wherein the unified governance platform comprises:
a token security microservice ( 30 ),
at least one security repository ( 35 , 36 , 37 ),
a logging element ( 90 ),
a service register ( 91 );

wherein said method for logging microservices comprises:
receiving ( 820 ), by the token security microservice ( 30 ), of a join request from a new microservice ( 60 ), said join request comprising a unique identifier of the new microservice (IDMS);
verifying ( 830 ), by the token security microservice ( 30 ), of the unique identifier of the new microservice (IDMS) from information memorised in the at least one security repository ( 35 , 36 , 37 ),
generating ( 840 ) of an authentication token (token1) and transmission of the authentication token (token1) to the new microservice by the token security microservice ( 30 ), and
receiving ( 850 ), by the logging element ( 90 ), of a logging request from a new microservice, said logging request comprising data that provides access to resources of the new microservice and the authentication token (token1);
verifying ( 860 ) of the authentication token with the token security microservice ( 30 ), and
logging ( 870 ), by the logging element ( 90 ), when the authentication token is validated, the data that provides access to the resources of the new microservice on the service register ( 91 ).

12 . The method ( 800 ) for logging microservices according to claim 11 , further comprising continuously updating the service register ( 91 ) and in particular the data that provides access to the resources of the new microservice.

13 . The method ( 800 ) for logging microservices according to claim 11 , wherein the join request further comprises a password of the new microservice and in that the token security microservice also verifies the password of the new microservice.

14 . The method ( 800 ) for logging microservices according to claim 11 , wherein the join request further comprises an identifier of an administrator of the unified governance platform and a password for said administrator of the unified governance platform and in that the token security microservice also verifies the identifier of the administrator of the unified governance platform and its password.

15 . The method ( 800 ) for logging microservices according to claim 11 , wherein the method further comprises:
receiving by the logging element ( 90 ) of the logging request (REQE) sent by the new microservice ( 60 ); sending, by the logging element ( 90 ), the authentication token (token1) to the token security microservice ( 30 ); then verifying ( 860 ) of the authentication token with the token security microservice ( 30 ).

16 . The method ( 800 ) for logging microservices according to claim 11 , wherein the unified governance platform comprises a proxy microservice ( 20 ) and wherein the method further comprises:
receiving by the proxy microservice ( 20 ) of the logging request (REQE) sent by the new microservice ( 60 ); sending, by the proxy microservice ( 20 ), the authentication token (token1) to the token security microservice ( 30 ); transmitting ( 865 ), by the proxy microservice ( 20 ), of the logging request (REQE) to the logging element ( 90 ) when the authentication token (token1) is validated.

17 . The method ( 800 ) for logging microservices according to claim 11 , wherein the new microservice is made accessible to a user client ( 2 ) at a level of an aggregated interface ( 10 ) and wherein the method further comprising transmitting content data from the new microservice to the aggregated interface ( 10 ).

18 . The method ( 800 ) for logging microservices according to claim 11 , wherein the unified governance platform comprises a proxy microservice ( 20 ) and in that the method further comprises transmitting ( 890 ) of data that provides access to the resources of the new microservice, by the logging element ( 90 ), to the proxy microservice ( 20 ).

19 . The method ( 800 ) for logging microservices according to claim 18 , wherein the proxy microservice ( 20 ) is configured, on reception of a service request (SREQ) from a user client ( 2 ), to transmit to the new microservice ( 60 ) a request (EREQ) concerning access data received then to transmit the resources or contents (RES) obtained to the user client ( 2 ).

20 . The method ( 800 ) for logging microservices according to claim 11 configured to execute on a system ( 1 ) comprising:
a security repository ( 35 , 36 , 37 ) configured to memorise identification information of new microservices;
a service register ( 91 ) configured to memorise data that provides access to the resources of new microservices;
a token security microservice ( 30 );

wherein the method further comprises executing steps on said token security microservice ( 30 ) comprising:
receiving a join request from a new microservice ( 60 ), said join request comprising a unique identifier of the new microservice (IDMS),
verifying the unique identifier of the new microservice (IDMS) from information memorised in the security repository ( 35 , 36 , 37 ),
generating an authentication token and transmit said authentication token to the new microservice; and

wherein the method further comprises executing steps on said logging element ( 30 ) comprising:
receiving a logging request from a new microservice, said logging request comprising data that provides access to the resources of the new microservice and the authentication token; and
logging, when the authentication token is validated, data that provides access to the resources of the new microservice on the service register ( 91 ).

Assignees

• Bull Sas

Inventors

• Calegari Patrice
• Levrier Marc

Classifications

• H04L67/51

  Discovery or management thereof, e.g. service location protocol [SLP] or web services · CPC title

• G06F9/5072 Primary

  Grid computing · CPC title

• H04L63/0807 Primary

  using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213) · CPC title

• H04L63/0815

  providing single-sign-on or federations · CPC title

• H04L63/108

  when the policy decisions are valid for a limited amount of time · CPC title