KR20210051817A - System and method for providing an authentication information service based an open api - Google Patents

Abstract

The present invention relates to a system for providing an authentication verification information service based on an open interface. The system for providing the authentication verification information service based on the open interface comprises: a linkage equipment management module registering and managing linkage equipment provided in each linkage institution; a linkage status management module searching linkage status information in accordance with a search request for each linkage equipment registered through the linkage equipment management module; and an authentication information management module requesting authentication information to each linkage equipment registered through the linkage equipment management module, receiving the authentication information transmitted from each linkage equipment in accordance with the request, verifying consistency of the authentication information received from each linked equipment, and determining whether there is an error.

Description

Open interface based authentication verification information service provision system and method {SYSTEM AND METHOD FOR PROVIDING AN AUTHENTICATION INFORMATION SERVICE BASED AN OPEN API}

The present invention relates to a system and method for providing an open interface-based authentication confirmation information service for checking authentication information on connected equipments provided in each connected organization in an authentication management server.

As the role and proportion of SMEs in each country's economy continues to expand, the importance of certification and management of SMEs is increasing. For example, professional evaluation of each SME is required, and management and evaluation of certification and implementation of various national policy projects are required.

Authentication and management of such small and medium enterprises can be performed in various ways, and authentication according to various authentication systems for numerous small and medium enterprises and related organizations is efficiently performed through an open API (application programming interface). There is a need for methods that can be done.

Meanwhile, the open interface refers to a standardized open interface between the communication service logic and the communication network. The open interface is a core technology that enables the provision of various integrated services regardless of the characteristics and types of the underlying transport network, and accesses a simple object and an open interface based on Common Object Request Broker Architecture (CORBA), led by the Parlay group. It is standardized as an open interface based on Simple Object Access Protocol (SOAP).

Accordingly, there is a need for a method capable of effectively performing authentication through a linkage equipment provided in a linkage organization such as each small and medium enterprise using the open interface.

[Document 1] Korean Patent Laid-Open Publication No. 10-2012-0058649 RESTful Open API System and Method (Korea) 2012.06.08

Accordingly, an object of the present invention is to provide a system and method for providing an open interface-based authentication verification information service capable of effectively checking and managing authentication information on connected equipments provided in each connected organization in an authentication management server using an open interface. Is in.

An open interface-based authentication confirmation information service providing system of the present invention for achieving the above object includes: a linked equipment management module for registering and managing linked equipment provided in each linked organization; A linkage state management module for searching linkage state information according to a search request for each linkage device registered through the linkage device management module; And requesting authentication information to each connected device registered through the connected device management module, receiving authentication information transmitted from each connected device according to the request, and verifying the consistency of the authentication information received from each connected device. And an authentication information management module that determines whether or not there is an error.

Preferably, the authentication information management module is characterized in that it requests the authentication information in the form of an API.

Preferably, the authentication information management module is characterized in that it sets an authentication cycle for each of the associated equipment.

Preferably, the authentication information received from each associated device is characterized in that the XML (extensible markup language) format.

Preferably, the system further comprises a linkage item management module for managing linkage items for each linkage equipment, and the linkage item managed by the linkage item management module, wherein the linkage item is an interface name, a physical name , Logical name, data type, length, and item attribute.

Preferably, the linked equipment information stored through the linked equipment management module includes: equipment ID, linked organization, installation location, installation location manager, installation location contact information, installation date, connection server connection information, screen display order, and whether or not to use. It characterized in that it includes at least one.

Preferably, the linked equipment management module is characterized in that it searches for pre-stored authentication system information and sets an authentication system for each of the linked equipment.

In order to achieve the above object, the method for providing an open interface-based authentication confirmation information service of the present invention includes the steps of registering linkage equipment provided in each linkage organization; Searching for link status information according to a search request for each registered linked device, and outputting a search result; Requesting authentication information from each of the registered linked devices; Receiving authentication information transmitted from each associated device according to the request; And verifying the integrity of the authentication information received from each of the associated devices, and determining whether there is an error.

Preferably, in the method of providing an open interface-based authentication confirmation information service, the method comprising: registering linkage equipment provided in each linkage organization; Searching for link status information according to a search request for each registered linked device, and outputting a search result; Requesting authentication information from each of the registered linked devices; Receiving authentication information transmitted from each associated device according to the request; And verifying the integrity of the authentication information received from each of the associated devices, and determining whether there is an error.

Preferably, the step of requesting the authentication information is characterized in that the authentication information is requested in the form of an API.

Preferably, the method further comprises the step of setting an authentication cycle for each of the associated equipment.

Preferably, the authentication information received from each associated device is characterized in that the XML (extensible markup language) format.

Preferably, the method further comprises the step of managing a linkage item for each linkage device, wherein the linkage item includes an interface name, a physical name, a logical name, a data type, a length, an item attribute, and the like. It is characterized.

Preferably, the information related to the registered linked equipment includes at least one of equipment ID, a linked agency, an installation place, an installation site manager, an installation site contact information, an installation date, connection server access information, a screen display order, and whether or not to use. Characterized in that.

Preferably, the method further comprises linking an authentication system to each of the linked equipment.

According to the present invention, the authentication management server can effectively check and manage authentication information for connected equipments provided in each connected organization by using an open interface.

1 is a diagram illustrating a system for providing an authentication verification information service based on an open interface according to the present invention.
2 is a block diagram showing a detailed module of an authentication management server according to an embodiment of the present invention.
3 is a flowchart illustrating a procedure for providing an open interface-based authentication confirmation information service according to an embodiment of the present invention.
4 is a diagram illustrating an example of information transmitted and received according to an embodiment of the present invention.
5 is a diagram showing detailed configurations of an open interface-based authentication confirmation information service providing system according to the present invention.
6 to 13 are diagrams showing examples of execution screens of an authentication management system according to an embodiment of the present invention.
14 is a diagram illustrating a screen for issuing a confirmation document issued based on an authentication result according to an embodiment of the present invention.
15 is a diagram illustrating an example of new registration of authentication information according to an embodiment of the present invention.
16 is a diagram illustrating a linkage error management screen according to an embodiment of the present invention.
17 to 19 are views showing an authentication data input screen according to an embodiment of the present invention.
20 is a diagram illustrating an authentication data input status screen according to an embodiment of the present invention.

Hereinafter, specific details for carrying out the present invention will be described based on embodiments with reference to the drawings. These embodiments are described in detail sufficient to enable a person skilled in the art to practice the present invention. It should be understood that the various embodiments of the present invention are different from each other, but need not be mutually exclusive. For example, specific shapes, structures, and characteristics described herein may be implemented in other embodiments without departing from the spirit and scope of the present invention in relation to one embodiment. In addition, it should be understood that the location or arrangement of individual components in each disclosed embodiment may be changed without departing from the spirit and scope of the present invention. Accordingly, the detailed description to be described below is not intended to be taken in a limiting sense, and the scope of the present invention, if properly described, is limited only by the appended claims, along with all scopes equivalent to those claimed by the claims. Like reference numerals in the drawings refer to the same or similar functions over several aspects.

Unless otherwise defined, all terms (including technical and scientific terms) used in the present specification may be used with meanings that can be commonly understood by those of ordinary skill in the art to which the present invention belongs. In addition, terms defined in a commonly used dictionary are not interpreted ideally or excessively unless explicitly defined specifically.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings in order to enable those of ordinary skill in the art to easily implement the present invention.

1 is a diagram illustrating a system for providing an authentication verification information service based on an open interface according to the present invention. Referring to FIG. 1, the system according to the present invention may be configured to include an authentication management server 111, a linkage authority server 121, and a linkage equipment 122. The authentication management server 111 may operate in conjunction with the administrative network linking server 113 or the general network linking server 114. The system administrator may access the authentication management server 111 through the administrative network connection server 113. The person in charge of the linked organization manages the linked equipment 122 and may install programs necessary for authentication on the linked equipment 122 or the linked organization server 121 through the linked organization server 121. For example, in the case of adding, changing, or deleting a linkage item for each linked agency, a table of an application or a database may be changed through the linked agency server 121.

The authentication management server 111 may additionally include a database 112 internally or externally. A VPN (virtual private network) 115 and 123 may be connected between the general network linking server 114 and the linking device 122, respectively. The authentication management server 111 and the associated authority server 121 may transmit and receive data to and from each other through the VPNs 115 and 123.

According to the present invention, a person in charge of a linked organization may register authentication information in the linked equipment 122 (or linked device database) through the linked organization server 121. The authentication information may be periodically registered or updated.

The system administrator may set an authentication cycle for each associated equipment 122 through the authentication management server 111. When the set authentication cycle arrives, authentication information may be requested from each associated device 122 registered in the authentication management server 111. The authentication information request may be requested in the form of an API as shown in FIG. 4 to be described later. The API may include a URL (uuniform resource locator) as shown in FIG. 1.

The associated device 122 may receive the URL requested from the authentication management server 111 and transmit authentication information to the authentication management server 111. The authentication information transmitted from the associated device 122 may be transmitted in an extensible markup language (XML) format.

The authentication management server 111 may verify the consistency of authentication information received from the associated device 122 and determine whether there is an error. The authentication management server 111 may generate error authentication information in an XML format according to a result of verifying the integrity of the authentication information, and transmit the generated error authentication information in the XML format to the associated device 122.

The error authentication information transmitted to the linkage device 122 may be stored in a database, and the linkage agency person in charge may use the linkage agency server 121 to query the stored error authentication information through a pre-installed program.

2 is a block diagram showing a detailed module of an authentication management server according to an embodiment of the present invention. Referring to FIG. 2, the authentication management server 111 may include a control unit 210, a communication interface 220, an input unit 230, and a memory 240.

The controller 210 may include a linked equipment management module 211, a linked state management module 212, a linked item management module 213, and an authentication information management module 214. The memory 240 may include authentication system information 241, information on a related organization 242, information on a related equipment 243, and information on a related state 244.

The linked equipment management module 211 serves to manage the linked equipment 122 provided in each linked institution, and can be managed through a program previously installed as shown in FIGS. 6 to 9 to be described later. According to an embodiment of the present invention, the linked equipment management module 211 receives various related information on each of the linked equipment 122 through the input unit 230 and converts the related equipment information 243 to the memory 240 as the linked equipment information 243. Can be saved.

Linked equipment information 243 stored through the linked equipment management module 211 includes: equipment ID, linked organization, installation location, installation location manager, installation location contact information, installation date, connection server access information, screen display order, and usage It may include whether or not. In addition, the linked equipment management module 211 may modify, delete, or initialize pre-stored information.

According to an embodiment of the present invention, the linked device management module 211 may search for authentication system information 241 stored in the memory 240 and set an authentication system for each linked device. In addition, the linkage equipment management module 211 may set a linkage period, a linkage date, and a linkage time for the set authentication system.

The linkage state management module 212 searches the linkage state information 244 stored in the memory according to the ID search request for the linkage equipment or the linkage organization through the input unit 230, and the result is as shown in FIG. You can print it on the screen.

The linkage item management module 213 may select an authentication type for each linkage device through the input unit 230, and then register a specific linkage item according to a request for addition of the linkage item. The association item may include an interface name, a physical name, a logical name, a data type, a length, and an item attribute. The linkage item management module 213 may delete a corresponding item stored in the memory 240 in response to a request for deletion processing of the registered linkage item.

The authentication information management module 214 may set an authentication cycle for each associated device 122 through the input unit 230. When the set authentication cycle arrives, the authentication information management module 214 checks each associated equipment information 243 registered in the memory 240, and authenticates with the corresponding associated equipment 122 through the communication interface 220. You can request information. The authentication information request may be requested in the form of an API as shown in FIG. 4 to be described later. The API may include a URL (uuniform resource locator) as shown in FIG. 1.

The authentication information management module 214 may receive authentication information transmitted from each associated device 122 through the communication interface 220. The authentication information transmitted from the associated device 122 may be transmitted in an extensible markup language (XML) format. The authentication information management module 214 may verify the consistency of the authentication information received from the associated device 122 and determine whether there is an error. The authentication information management module 214 generates error authentication information in an XML format according to a result of verifying the integrity of the authentication information, and transmits the generated error authentication information in the XML format through the communication interface 220 to a corresponding associated device ( 122).

3 is a flowchart illustrating a procedure for providing an open interface-based authentication confirmation information service according to an embodiment of the present invention. Referring to FIG. 3, the system administrator may log in to the authentication management server 111 (310).

Then, the authentication management server 111 may register the associated equipment through the input of the system administrator. (320)

Next, the authentication management server 111 may register 330 a linkage authentication system connected to the registered linkage device. In addition, the authentication management server 111 may set the linkage time and linkage period for each linkage authentication system registered above.

The authentication management server 111 may monitor a linkage state (eg, linkage equipment status, linkage number, etc.) according to the set linkage cycle.

Accordingly, when the set linkage period arrives (350), the authentication management server 111 may request an API from each linkage device (360).

The authentication management server 111 may receive a monitoring result from each associated device according to the request. (370)

4 is a diagram illustrating an example of information transmitted and received according to an embodiment of the present invention. Referring to FIG. 4, the authentication management server 111 may have an API request and processing program installed. According to the execution of the program, the authentication management server 111 may request an API from the linkage authority server 121 according to a set linkage period. In addition, the authentication management server 111 is linked schedule management, linked monitoring, linked log management, linked agency management (eg, key issuance management, etc.), linked company information management (eg, company information, approval key, linked server/API) Address, etc.), authorization key management (create, modify, delete), etc. can be additionally performed.

The associated authority server 121 may receive an API request from the authentication management server 111 and transmit a monitoring result to the authentication management server 111 in an XML format. In addition, the linkage institution server 121 may be installed with a web service program, and may set various linkage information (eg, query, DB access information, DB query, authorization key value, allowable IP, etc.). In addition, the linkage institution server 121 may monitor the linkage state and manage the linkage log.

5 is a diagram showing detailed configurations of an open interface-based authentication confirmation information service providing system according to the present invention. 5 illustrates an example of managing the authentication management server 111 as an example managed by a small and medium-sized business researcher.

The system linked by the authentication management server 111 may manage a company information database, a schedule information database, a linked log database, and a standard linked database. Accordingly, the authentication management server 111 may manage a linked company, set a linked company server, manage an approval key, and manage a link schedule through the company information database. The authentication management server 111 manages an association table, and may store information related thereto in a standard association database. The authentication management server 111 may perform API log management using linkage log information stored in the linkage log database, and may perform linkage monitoring.

Meanwhile, the linkage target organization may manage a linkage setting database, a linkage log database, and a standard linkage database through the linkage agency server 121.

The authentication management server 111 may request authentication information from the association authority server 121 by executing an API program for each association information according to a schedule stored in the schedule information database. The associated agency server 121 may operate an API program to receive an API request from the authentication management server 111 and process the received API request.

6 to 13 are diagrams showing examples of execution screens of an authentication management system according to an embodiment of the present invention. Referring to FIG. 6, after logging in to the authentication management system, a linked equipment management screen may be executed.

On the linked equipment management screen, an equipment ID, a linked organization, an installation location, an installation location manager, an installation location contact information, installation date, connection service access information, screen display order, usage, etc. may be set or inquired.

For example, if an inquiry button is clicked on the screen shown in FIG. 6 and an organization name is selected from an organization search pop-up, the organization selected by the related organization may be registered. Then, you can enter the IP address and PORT information of the associated server.

7 is a detailed inquiry screen for managing linked equipment. By executing the detailed inquiry of the associated equipment, the equipment ID, the associated organization, the installation location, the installation site manager, the installation location contact information, the installation date, the connection server access information, the screen display order, and whether or not to be used can be viewed and modified.

8 is a modified screen of linked equipment management. When the list button is clicked on the linked equipment management modification screen, the screen moves to the linked equipment list screen, and when the inquiry button is clicked, an institution search pop-up may be displayed. Linked equipment information is saved when the save button is clicked, and linked equipment information can be initialized when the reset button is clicked.

9 is a screen for setting an authentication system linkage. When the add button is clicked on the screen, a pop-up search for a certification system may be displayed, and a row may be added to the list of linked certification systems by clicking the name of the certification system and clicking the select button.

Then, it is possible to select a linkage period (eg, day, week, month, year) and a linkage date and select a linkage time. Then, clicking the save button saves the authentication system linkage setting information.

10 shows the linkage status management inquiry screen. Referring to FIG. 10, when a search condition such as an affiliated organization or equipment ID is input on the screen and the inquiry button is clicked, a list of linked status is inquired. At this time, if a connection state error occurs, it may be necessary to block the network and firewall, and check whether the associated equipment is operating.

11 and 12 show a linked item management registration screen. Referring to FIGS. 11 and 12, when an authentication type (eg, company, technology, product, etc.) is selected and an add button is clicked, a row may be added at the bottom of the list of authentication items. Then, input the physical name, logical name, and data length and click the save button to register the linked item.

13 shows the linked item management change screen. Referring to FIG. 13, it is possible to select an authentication type (eg, company, service, facility, product, technology, etc.), and change a physical name, logical name, data length, and the like. According to a request for modification and deletion, the changed association item may be modified, or the current row of the authentication item list may be deleted.

14 is a diagram illustrating a screen for issuing a confirmation document issued based on an authentication result according to an embodiment of the present invention. Referring to FIG. 14, when a confirmation of the certification system is requested from the related organization through the related authority server 121, the certification management server 111 generates a certification system confirmation based on the information stored in the database 112. I can.

For example, in the certification management server 111, the certification system name, business number, business name, certification number, certification period, etc. of the related agency stored in the database 112 in response to the certification system confirmation request from the related agency server 121 It is possible to extract the information of the certificate and generate a certification system confirmation letter according to a preset form.

The generated authentication system confirmation may be transmitted to the associated institution server 121 and output on a screen or a printer as shown in FIG. 14.

15 is a diagram illustrating an example of new registration of authentication information according to an embodiment of the present invention. Referring to FIG. 15, after logging in to the authentication management server 111 through the linking authority server 121, the person in charge of the related organization may register authentication information as shown in FIG. 15.

For example, the authentication information registered through the associated institution server 121 includes an authentication information ID, an authentication system ID, an associated equipment ID, an authentication system field code, a business registration number, an authentication number, an authentication date, a corporation registration number, a company name, Information such as the name of the representative, certification authority code, certification start date, certification end date, certification cancellation date, certification system status code, certification system classification code, whether or not to use, creator ID, creation time, modifier ID, revision time, etc. I can.

16 is a diagram illustrating a linkage error management screen according to an embodiment of the present invention. Referring to FIG. 16, the person in charge of the linked organization may log in to the linked organization server 121 and check whether there is an error in authentication-related information registered for the linked device 122.

For example, as described above, the authentication management server 111 may check authentication-related information registered for the associated device 122 and check for errors. When an error occurs as a result of the error checking, the authentication management server 111 may transmit the error occurrence information to the associated device 122 or the associated institution server 121.

The person in charge of the linked organization may access the linked organization server 121 and check the error occurrence information transmitted from the authentication management server 111 as shown in FIG. 16. The error occurrence information may include a reception date and time, an error content, an authentication information ID, an authentication authority code, an authentication start date, an authentication end date, an authentication cancellation date, an authentication system classification code, and the like.

On the other hand, when the authentication information is corrected by checking the error authentication information, it is registered in the database of the linked device 122, and the corrected authentication information may be automatically reflected when the next authentication information is linked. That is, when the next authentication information linkage cycle comes, the authentication management server 111 checks the corrected authentication information by accessing the database of the linking device 122, and checks whether an error has occurred according to the corrected authentication information. You can judge again.

17 to 19 are views showing an authentication data input screen according to an embodiment of the present invention. Referring to FIG. 17, each person in charge of management of authentication information may log into the authentication management server 111 to each authentication system and input authentication data contents for each authentication system. The authentication data may include information such as an authentication field, a competent authority, a name of a certification system, a performing institution, a linkage classification, a number of normal input data, a number of online input data, a web input file, an Excel input file, and the like.

According to various embodiments, when the number of authentication data inputs is relatively small, as shown in FIG. 18, by selecting a web input, web input of a corresponding authentication system may be started. In addition, when the number of authentication data inputs is relatively large, as shown in FIG. 19, Excel upload may be selected to start the Excel upload of the corresponding authentication system. Referring to FIG. 19, the authentication management server 111 automatically performs data verification on input authentication data, and through the data verification, a list of authentication data and error details may be checked. For example, in FIG. 19, items indicated in yellow are verification result items, and items indicated in red indicate items in which an error has occurred among verification result items.

20 is a diagram illustrating an authentication data input status screen according to an embodiment of the present invention. Referring to FIG. 20, after inputting authentication data according to FIGS. 18 and 19, the input completion status and error status for each authentication system can be collectively checked through the authentication data input status screen.

The present invention has been described above with the purpose of method steps representing the performance of specific functions and their relationships. The boundaries and order of these functional components and method steps have been arbitrarily defined herein for convenience of description. Alternative boundaries and orders may be defined as long as the specific functions and relationships are properly performed. Any such alternative boundaries and sequences are therefore within the scope and spirit of the claimed invention. In addition, the boundaries of these functional components have been arbitrarily defined for convenience of description. Alternative boundaries can be defined as long as certain important functions are performed properly. Likewise, flowchart blocks may also have been arbitrarily defined herein to indicate any significant functionality. For extended use, the flow diagram block boundaries and order may have been defined and still perform some important function. Alternative definitions of both functional elements and flowchart blocks and sequences are therefore within the scope and spirit of the claimed invention.

The present invention may also have been described, at least in part, in terms of one or more embodiments. Embodiments of the invention are used herein to represent the invention, its aspects, its features, its concepts, and/or examples thereof. A physical embodiment of an apparatus, article of manufacture, machine, and/or process embodying the present invention refers to one or more aspects, features, concepts, examples, etc. described with reference to one or more embodiments described herein. Can include. Moreover, in the overall drawing, embodiments may incorporate the same or similarly named functions, steps, modules, etc., which may use the same or different reference numbers, and as such, the functions, Steps, modules, etc. may be the same or similar functions, steps, modules, etc. or others.

As described above, in the present invention, specific matters such as specific components, etc., and limited embodiments and drawings have been described, but these are provided only to help a more general understanding of the present invention, and the present invention is not limited to the above embodiments. , If a person of ordinary skill in the field to which the present invention belongs, various modifications and variations are possible from these descriptions.

Therefore, the spirit of the present invention is limited to the described embodiments and should not be defined, and all things that are equivalent or equivalent to the claims as well as the claims to be described later fall within the scope of the inventive concept. .

111: authentication management server 112: database
113: administrative network connection server 114: general network connection server
115: VPN 121: affiliated organization server
122: connected equipment 123: VPN
210: control unit 211: linked equipment management module
212: linkage status management module 213: linkage item management module
214: authentication information management module 220: communication interface
230: input unit 240: memory
241: Certification system information 242: Linked organization information
243: Linked equipment information 244: Linked state information

Claims (15)

In the open interface-based authentication verification information service providing system,
A linked equipment management module for registering and managing linked equipment provided in each linked organization;
A linkage state management module for searching linkage state information according to a search request for each linkage device registered through the linkage device management module; And
Request authentication information to each linked device registered through the linked device management module, receive authentication information transmitted from each linked device according to the request, and verify the consistency of the authentication information received from each linked device, Authentication information management module for determining whether or not an error; including, an open interface-based authentication verification information service providing system.
The method of claim 1, wherein the authentication information management module,
An open interface-based authentication confirmation information service providing system, characterized in that the authentication information is requested in the form of an application programming interface (API).
The method of claim 1, wherein the authentication information management module,
An open interface-based authentication confirmation information service providing system, characterized in that an authentication cycle for each of the associated equipment is set.
The system of claim 1, wherein the authentication information received from each associated device is in an XML (extensible markup language) format.
The method of claim 1, wherein the system,
Further comprising a linkage item management module for managing linkage items for each of the linked equipment,
The linkage item managed by the linkage item management module,
The association item comprises at least one of an interface name, a physical name, a logical name, a data type, a length, and an item attribute.
The method of claim 1, wherein the linked equipment information stored through the linked equipment management module comprises:
Provides an open interface-based authentication verification information service, characterized in that it includes at least one of equipment ID, association organization, installation site, installation site manager, installation site contact information, installation date, connection server access information, screen display order, and usage status system.
The method of claim 1, wherein the linked equipment management module,
Retrieving pre-stored authentication system information, and setting an authentication system for each of the associated equipment.
In the open interface-based authentication verification information service provision method,
Registering linkage equipment provided in each linkage organization;
Searching for link status information according to a search request for each registered linked device, and outputting a search result;
Requesting authentication information from each of the registered linked devices;
Receiving authentication information transmitted from each associated device according to the request; And
Comprising, verifying the integrity of the authentication information received from each of the associated equipment, and determining whether there is an error; including, open interface-based authentication verification information service providing method.
The method of claim 8, wherein the requesting the authentication information comprises:
A method of providing an open interface-based authentication confirmation information service, characterized in that requesting the authentication information in the form of an application programming interface (API).
The method of claim 8, wherein the method comprises:
The method of providing an open interface-based authentication confirmation information service, further comprising the step of setting an authentication period for each of the associated equipment.
The method of claim 8, wherein the authentication information received from each associated device is in an XML (extensible markup language) format.
The method of claim 8, wherein the method comprises:
It further comprises the step of managing the linkage items for each of the linked equipment,
The association item comprises at least one of an interface name, a physical name, a logical name, a data type, a length, and an item attribute.
The method of claim 8, wherein the information related to the registered linked equipment,
Provides an open interface-based authentication verification information service, characterized in that it includes at least one of equipment ID, association organization, installation site, installation site manager, installation site contact information, installation date, connection server access information, screen display order, and usage status Way.
The method of claim 8, wherein the method comprises:
The method of providing an open interface-based authentication confirmation information service, further comprising linking an authentication system to each of the associated equipment.
A computer-readable recording medium on which a program for performing the method according to any one of claims 8 to 14 on a computer is recorded.

Images