JP6518302B2 - INFORMATION PROCESSING APPARATUS, CONTROL METHOD THEREOF, AND PROGRAM - Google Patents

Description

The present invention relates to an information processing apparatus , a control method therefor, and a program .

  A multi-function peripheral (MFP) having functions such as copying, printing, scanning, and fax transmission / reception is known. By further providing the user authentication function to such an MFP, it becomes possible to restrict the use of the MFP. That is, only a user who has been authenticated as a legitimate user of the MFP can use the MFP.

  There is a demand for customization that the function for authenticating the user, that is, the login function is to be changed from the standard function of the MFP according to the customer's operation environment. For example, there is a device that wants to use an IC card reader or a vein authentication device as an authentication device. In addition, there are also requests for changing the design of the login screen for allowing the user to input authentication information, and for changing the database to which the authentication information of the input user is compared to a dedicated server other than the MFP. is there.

  As a method for coping with such various needs, for example, Patent Document 1 proposes a method of customizing the login function of the MFP.

Patent No. 4409970

  However, in the method of customizing the login function shown in Patent Document 1, there is a problem that the number of development steps for customization becomes large because it is necessary to implement a set of login functions.

  In addition, there is a demand that, when the login function is customized, a program module created by the conventional customization method is also operated.

  An object of the present invention is to solve the above-mentioned problems of the prior art.

  A feature of the present invention is to provide a technique for customizing a program with a small number of development steps while maintaining compatibility with applications customized by the conventional customization method.

In order to achieve the above object, an information processing apparatus according to an aspect of the present invention has the following configuration. That is,
An information processing apparatus,
Memory for storing an embedded login application having a plurality of functions including at least a display function for displaying a login screen and an authentication function for performing user authentication based on login information input through the login screen Means,
When a login plug-in module having a display function for displaying the login screen or an authentication function for controlling user authentication is added to the information processing apparatus, the plurality of functions included in the embedded login application are included. Control means for disabling a function corresponding to the function possessed by the login plug-in module and controlling a function corresponding to the function not possessed by the login plug-in module among the plurality of functions to be effective Yes, and
When the function of the embedded login application is a function that does not need to be replaced, the function of the embedded login application corresponding to the function of the login plug-in module is not invalidated, and it relates to one function related to login It is characterized in that both functions are enabled .

  According to the present invention, it is possible to provide a technique for customizing a program with a small number of development steps while maintaining compatibility with applications customized by the conventional customization method.

FIG. 1 is a view showing an example of the arrangement of a system including a multifunction peripheral (MFP) according to the first embodiment of the present invention. FIG. 2 is a block diagram for explaining the hardware configuration of the MFP according to the first embodiment. FIG. 2 is a block diagram for explaining the software configuration of the MFP according to the first embodiment. FIG. 2 is a block diagram for explaining the software configuration when a custom login application is operating in the MFP according to the first embodiment. FIG. 8A shows an example of a login application selection table, FIG. 8B shows an example of an attribute file, and FIG. 7C shows an example of a custom module state table. 6 is a flowchart illustrating processing of enabling a custom module in the MFP according to the first embodiment. 6 is a flowchart for describing user authentication processing when the MFP according to the first embodiment is performing a custom local login. 7 is a flowchart for explaining processing of the MFP according to the third embodiment.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. The following embodiments do not limit the present invention according to the claims, and all combinations of the features described in the embodiments are not necessarily essential to the solution means of the present invention. . In the present embodiment, the information processing apparatus according to the present invention is described using a multifunction peripheral (MFP) as an example, but the present invention is not limited to such a multifunction peripheral.

  FIG. 1 is a view showing an example of the arrangement of a system including a multifunction peripheral (MFP) 101 according to the first embodiment of the present invention.

  In this system, an MFP 101 and a PC 102 are connected to a LAN 100. The PC 102 remotely operates the MFP 101. The MFP 101 and a PBX (Private Branch exchange) 103 are connected via a telephone line 105. The PBX 103 is connected to the public switched telephone network 104, and is used in the FAX function of the MFP 101. The MFP 101 may be directly connected to the public switched telephone network 104.

  FIG. 2 is a block diagram for explaining the hardware configuration of the MFP 101 according to the first embodiment.

  A control unit 200 including the CPU 201 controls the overall operation of the MFP 101. The CPU 201 reads a control program stored in the ROM 202 and performs various controls such as read control and transmission control. The RAM 203 is used as a main memory of the CPU 201 and a temporary storage area such as a work area. The HDD 204 stores image data and various programs. The operation unit I / F 205 connects the operation unit 210 and the control unit 200. The printer I / F 206 connects the printer 211 and the control unit 200. Image data to be printed by the printer 211 is transferred from the control unit 200 to the printer 211 via the printer I / F 206, and is printed on a recording medium by the printer 211. The scanner I / F 207 connects the scanner 212 and the control unit 200. The scanner 212 reads an image on a document, generates image data of the image, and inputs the image data to the control unit 200 via the scanner I / F 207. The FAX I / F 208 connects the control unit 200 to the telephone line 105. A fax I / F 208 transmits / receives fax data to / from the PBX 103 or public switched telephone network 104 connected to the telephone line 105. The network I / F 209 connects the control unit 200 to the LAN 100. The network I / F 209 receives a request from an external device (for example, the PC 102) on the LAN 100 and transmits a response to the request.

  FIG. 3 is a block diagram for explaining the software configuration of the MFP 101 according to the first embodiment. Here, unless otherwise noted, each processing unit is a control program stored in the ROM 202, and these control programs are executed by the CPU 201.

  The operating system 300 has various functions as a basis to operate the control program stored in the ROM 202, but here, parts relevant to the essence of the present invention will be described. The application activation unit 301 activates an application operating on the operating system 300. The login application selection unit 302 selects, for the user of the MFP 101, a login application (to be described later) to be activated. As a method of selecting a login application, there is a method of displaying a UI screen on the operation unit 210 or a web browser operating on the PC 102 and allowing the user to select it by the operation of the user via the UI screen. The selected state of the login application selected by the user is registered in the login application selection table 303.

  A login application (built-in login application 330, default login application 310, custom login application 390) is a control program that executes a login function in the MFP 101. The login application to be launched is either the default login application 310 or the custom login application 390. The default login application 310 is a login application that always exists in the MFP 101. The custom login application 390 is a login application created according to the conventional customization method, and must have a single login function. Also, a plurality of custom login applications 390 can be installed on the MFP 101.

  The selection result of the login application by the login application selection unit 302 is stored in the login application selection table 303 (FIG. 5A) of the HDD 204.

  FIG. 5A shows an example of the login application selection table 303. As shown in FIG.

  FIG. 5A shows that the login application (the “default login application” in FIG. 5A) in which the “use” column is “1” is selected.

  The default login application 310 is a special login application. The default login application 310 itself does not have a login function, and has a role of enabling a login function implemented as a custom module in the login plug-in module 320 (described later). For that purpose, the custom module validation unit 311 refers to the attribute file 322 (FIG. 5B) present in the login plug-in module 320, and the custom module implemented in the login plug-in module 320 according to the content thereof. Activate the The custom module created in this embodiment is implemented in the login plug-in module 320.

  FIG. 5B shows an example of the attribute file 322. As shown in FIG.

  Here, the activation means reading out the module from the HDD 204 to the RAM 203 and making the CPU 201 executable. The process of instantiating the class indicated by the class name described in the “name” column of FIG. 5B corresponds to the process of validation, in the case of construction using the Java language as an example.

  The login plug-in module 320 is a module that is dynamically installed (added) in the MFP 101 and stored in the HDD 204. The developer customizes the login function of the MFP 101 by creating a custom module, which is the minimum unit of the login function, and implementing the module in the login plug-in module 320. The custom module includes, for example, a local login screen processing unit, a web browser login screen processing unit, and a user authentication processing unit. The login plug-in module 320 comprises one or more of these.

  FIG. 3 shows the case where a custom local login screen processing unit 321 exists as an example of the custom module. The custom module validation unit 311 writes the result of validation of the custom module in the custom module status table 312 (FIG. 5C) of the HDD 204.

  FIG. 5C shows an example of the custom module state table 312. As shown in FIG.

  The custom module state table 312 contains information of one module per line. The information includes a module name, "validation type", and "state", and the description thereof will be described later.

  The embedded login application 330 is intrinsic to the MFP 101 and is a login application that is always activated regardless of the user's selection. The use module determination unit 331 refers to the custom module state table 312 to validate the built-in login module corresponding to the custom module not implemented by the login plug-in module 320. In the example of FIG. 3, since the login plug-in module 320 includes the custom local login image processing unit 321, only the local login image processing unit 332 of the embedded login application 330 is not activated.

  The embedded login module includes, for example, a local login screen processing unit 332, a web browser login screen processing unit 333, and a user authentication processing unit 334. In the first embodiment, the above-described three examples are given as the built-in login module, but there may be other modules. In addition, a module not to be customized (for example, the web service login processing unit 335) is also validated.

  The copy application 340, the print application 350, the scan application 360, and the fax application 370 are control programs that execute the copy function, the print function, the scan function, and the fax function, respectively. The event detection unit 380 detects whether the event indicated by the “unavailable event” of the attribute file 322 has occurred. For example, when detecting that the PC 102 is connected to the MFP 101 by VNC (Virtual Network Computing), the event detection unit 380 notifies the usage module determination unit 331 and the custom module validation unit 311 that the VNC connection is detected.

  FIG. 4 is a block diagram for explaining the software configuration when the custom login application 390 is operating in the MFP 101 according to the first embodiment. The difference from FIG. 3 is only in the area indicated by dotted line 400. Also, the difference in function is only the part related to module activation of the embedded login application 330. In the following, only differences from FIG. 3 will be described. The state shown in FIG. 4 corresponds to the case where the “Use” column of the custom login application is set to “1” in the login application selection table of FIG. 5 (A).

  When the custom login application 390 is launched from the application launch unit 301, the custom module validation unit 401 validates all custom modules. Here, all custom modules are the custom local login screen processing unit 402, the custom web browser login screen processing unit 403, and the custom user authentication processing unit 404. When the custom login application 390 is operating, the use module determination unit 331 does not activate the login module of the embedded login application 330.

  In the first embodiment, it is possible to activate the default login application 310, activate a custom login module implemented in the login plug-in module 320, and perform login processing via the screen of the custom login module.

  The custom login application 390 created according to the conventional customization method can be executed as shown in FIG. 4 by setting the “use” column of the custom login application in the login application selection table 303 to “1”.

  Next, custom module validation processing of the MFP 101 according to the first embodiment will be described using the flowchart of FIG.

  FIG. 6 is a flowchart illustrating processing for validating a custom module in the MFP 101 according to the first embodiment. A program for executing this process is stored in the ROM 202, expanded on the RAM 203 at the time of execution, and executed under the control of the CPU 201. Here, it will be described according to the software configuration of FIG. 3 and FIG.

  This process is started by activating the MFP 101. First, in step S601, the application activation unit 301 activates the built-in login application 330. Next, in step S602, the application activation unit 301 refers to the login application selection table 303. Then, in step S603, it is determined whether the login application selected in the login application selection table 303 is the default login application 310. Here, as shown in FIG. 5A, when the default login application 310 is selected, the process proceeds to S604, the application activation unit 301 activates the default login application 310, and the process proceeds to S605. On the other hand, if it is determined in step S604 that something other than the default login application is selected, the process advances to step S613, and the application activation unit 301 activates the login application selected in the login application selection table 303. Here, for example, when the custom login application 390 is selected, the custom login application 390 is launched as shown in FIG.

  In step S605, the custom module validation unit 311 refers to the attribute file 322, and when “local login screen processing unit” is described in “module” of the attribute file 322, the process proceeds from step S606 to step S607. In step S607, the custom module validation unit 311 validates the custom local login screen processing unit 321, and proceeds to step S608. In step S608, the custom module validation unit 311 writes “valid” in the “state” column of the “local login screen processing unit” of the custom module state table 312, and the process advances to step S620. The custom module validation unit 311 checks in step S620 whether all the modules registered in the attribute file 322 have been checked. If YES in step S620, the process advances to step S615; otherwise, the process returns to step S606.

  If “web browser login screen processing unit” is described in “module” of the attribute file 322 in step S606, the process advances to step S609. In step S609, the custom module validation unit 311 validates the custom web browser login screen processing unit (not shown), and proceeds to step S610. In step S610, the custom module validation unit 311 writes “valid” in the “status” of the “web browser login screen processing unit” in the custom module status table 312, and proceeds to step S620.

  If the “user authentication processing unit” is described in the “module” of the attribute file 322 in S606, the process proceeds to S611, and the custom module validation unit 311 validates the custom user authentication processing unit (not shown). Go to S612. In step S612, the custom module validation unit 311 sets the "status" of the "user authentication processing unit" in the custom module status table 312 to "valid", and proceeds to step S620.

  On the other hand, when the login application selected in the login application selection table 303 in S603 is not the default login application 310, the processing proceeds to S613. In step S613, the application activation unit 301 activates, for example, the custom login application 390 selected in the login application selection table 303. Then, in step S614, the custom module validation unit 401 of the custom login application 390 validates all the custom modules of the custom login application 390, and proceeds to step S615. Here, all custom modules are the custom local login screen processing unit 402, the custom web browser login screen processing unit 403, and the custom user authentication processing unit 404 in FIG.

  In step S615, the use module determination unit 331 determines whether the default login application 310 has been activated. As a method of this activation confirmation, there is a method of judging based on whether or not the use module determination unit 331 can access the custom module state table 312. Then, the process proceeds to step S616, and the use module determination unit 331 determines whether the started login application is the default login application 310. This is to determine whether the login plug-in module 320 can be executed under the default login application 310.

  If the default login application 310 has not been activated, the process advances to step S619. If the default login application 310 is activated, the process advances to step S617. In step S617, the use module determination unit 331 refers to the custom module state table 312, and the local of the same function as the module (the local login screen processing unit in FIG. 5C) in which the “state” column is “valid”. The login screen processing unit 332 is not activated. Also, a module whose “status” column is “invalid” is determined, and the process proceeds to step S618. In step S618, the use module determination unit 331 enables the web browser login screen processing unit 333 and the user authentication processing unit 334 set to “invalid” in the example of FIG. 5C, and proceeds to step S619. This is to allow the display function of the web browser login screen and the authentication function of the user to be executed when the custom login module of the login plug-in module 320 is executed. Then, in step S619, the embedded login application 330 validates the web service login processing unit 335, and ends this processing.

  In the above description, although the custom module status table 312 is used to determine whether the custom module is enabled, any method may be used as long as it can be determined whether the customization module is enabled. The confirmation method may be used. For example, the determination method may be such that the default login application 310 includes an API that responds to a query as to whether a custom module has been activated.

  As described above, according to the first embodiment, the default login application 310 can be activated to execute the custom login module of the login plug-in module 320. At this time, the custom module activation unit of the default login application refers to the custom module state table to determine the custom module to be activated. At this time, the login module corresponding to the custom module in the built-in login application is invalidated.

  Also, by launching a custom login application, it is possible to operate the custom login application 390 created in accordance with the conventional customization method.

  Next, processing in the case where the user actually performs a login operation with the custom module activated is described with reference to the flowchart in FIG. In the first embodiment, a case where the user operates the operation unit 210 is described as an access path to the MFP 101 by the user. Even when another access path, for example, a user accesses from a Web browser, the flow of processing is the same as the case where the user operates the operation unit, except for the processing unit of the login screen.

  FIG. 7 is a flowchart for describing user authentication processing when the MFP 101 according to the first embodiment is performing a custom local login. A program for executing this process is stored in the ROM 202, expanded on the RAM 203 at the time of execution, and executed under the control of the CPU 201.

  First, in step S701, the custom local login image processing unit 321 receives a user ID and a password input by operating the local login screen displayed on the operation unit 210 by the user. Here, the local login screen is displayed by any of the local login screen processing unit 332, the custom local login screen processing unit 321, and the custom local login screen processing unit 402. Hereinafter, these processing units will be collectively referred to as “local login screen processing unit”.

  Next, in step S702, the custom local login screen processing unit 321 passes the user ID and password input by the user in step S701 to the user authentication processing unit. The user authentication processing unit is any of a user authentication processing unit 334, a custom user authentication processing unit (not shown) in the login plug-in module 320, and a custom user authentication processing unit 404 of the custom login application 390.

  Next, in step S703, the user authentication processing unit authenticates the user based on the user ID and password passed in step S702. In step S704, it is determined whether the user authentication has succeeded. If it is determined that the user authentication has succeeded, the process advances to step S705, and the user authentication processing unit instructs the custom local login screen processing unit 321 that the user authentication has succeeded. Tell. As a result, the process advances to step S706, and the custom local login screen processing unit 321 turns off the display of the local login screen of the operation unit 210, ends the process in which the user can use the function (application) of the MFP 101.

  On the other hand, if it is determined in S704 that the user authentication has failed, the process advances to S707, and the user authentication processing unit notifies the custom local login screen processing unit 321 that the user authentication has failed. Then, the process proceeds to step S708, and the custom local login screen processing unit 321 displays on the operation unit 210 that the authentication fails and the login can not be performed, and the process ends. In this case, the user can not use the function (application) of the MFP 101.

  As described above, in the first embodiment, the web browser login screen processing unit and the user authentication processing unit of the embedded login application are enabled in the state where the custom module is activated. Therefore, even when the user performs a login operation, authentication of the user can be performed to determine whether the user can use the application of the MFP.

Second Embodiment
Embodiment 2 of the present invention will be described. In the first embodiment described above, only the modules disabled in the custom module state table 312 are validated in S617 and S618. This is a mechanism to ensure that only one module of the same type is activated. However, there is also a module having a property that a plurality of users may exist in the system, such as the user authentication processing unit 334. Thus, in the second embodiment, a method for validating a plurality of modules of the same type will be described. The configuration and system configuration of the MFP 101 according to the second embodiment are the same as those of the first embodiment described above, and thus the description thereof is omitted.

  As shown in FIG. 5C, the module for which the “validation type” is “replacement” in the custom module state table 312 is validated in step S618 as described in the first embodiment.

  On the other hand, when the “activation type” is “co-existence”, the module is activated regardless of whether “ineffective” or “effective” in the custom module state table 312.

  As a result, for a module whose activation type is "co-existing", an effect is obtained that both the custom module implemented by the login plug-in module and the built-in login module are activated.

Third Embodiment
Embodiment 3 of the present invention will be described. In the first embodiment described above, when the custom user authentication processing unit 404 is validated, the user can use the custom user authentication processing unit regardless of the access path for operating the MFP 101. Examples of the access path include a path for operating the MFP 101 via the operation unit 210, a path for operating the MFP 101 through a web browser operating on the PC 102, and the like. However, when there is a demand for not using the custom user authentication processing unit depending on the access path, the above operation becomes a problem.

  Thus, in the third embodiment, a method will be described in which the custom user authentication processing unit can be used only when the MFP 101 is operated in a specific access path. The configuration of the MFP 101 according to the third embodiment and the system configuration are the same as those of the first embodiment described above, and thus the description thereof is omitted.

  As shown in FIG. 5B, when the “access path” of the attribute file 322 is “local”, a UI is displayed on the local login screen so that the user authentication process can be used. As the method, for example, there is a method of displaying “login destination” on the login screen and displaying the name of the custom user authentication processing unit as the option.

  When the “access path” of the attribute file 322 is “Web browser”, a UI is displayed on the Web browser login screen so that the authentication process of the user can be used.

  By the above-described processing, it is possible to obtain an effect that the custom user authentication processing unit can be used only when the MFP 101 is accessed through a specific access path.

Fourth Embodiment
A fourth embodiment of the present invention will be described. In the first embodiment described above, custom modules implemented by the login plug-in module are always enabled. However, depending on the situation, it may not be desirable to enable. For example, the custom local login screen is designed to urge the IC card reader to touch the IC card, and the user performs a VNC connection from the PC 102 to the MFP 101. In this case, since the user can not touch with the IC card, such a login screen is meaningless.

  Therefore, in the fourth embodiment, a method of disabling a custom module and enabling a module in the corresponding embedded login application 330 in some situations will be described with reference to FIG. The configuration of the MFP 101 according to the fourth embodiment and the system configuration are the same as those of the first embodiment described above, and thus the description thereof will be omitted.

  FIG. 8 is a flowchart for explaining the process of the MFP 101 according to the third embodiment. A program for executing this process is stored in the ROM 202, expanded on the RAM 203 at the time of execution, and executed under the control of the CPU 201.

  First, in step S801, the event detection unit 380 refers to the attribute file 322 to confirm “unavailable event”. In the case of FIG. 5B, the "unavailable event" is the "VNC connection". Next, in step S802, the event detection unit 380 periodically checks whether the “VNC connection” confirmed in step S801 has occurred. If the event detection unit 380 detects a VNC connection in step S802, the process advances to step S803 to notify the usage module determination unit 331 and the custom module validation unit 311 that the VNC connection has been detected. Next, in step S804, the custom module validation unit 311 that has received this notification invalidates the custom local login screen processing unit 321. In step S805, the use module determination unit 331 validates the local login screen processing unit 332. Now, for the user who has made the VNC connection, the login screen possessed by the built-in login application 330 is displayed, not the login screen possessed by the login plug-in module 320.

  After that, the process proceeds to S 807 to detect that the VNC connection is ended in S 806, the event detection unit 380 detects that the VNC connection is ended, and the use module determination unit 331 and the custom module validation unit 311 To notify that it has finished. Then, in step S808, the use module determination unit 331 that has received the notification invalidates the local login screen processing unit 332. In step S809, the custom module validation unit 311 validates the custom local login screen processing unit 321. As a result, the login screen by the custom login module of the login plug-in module 320 is displayed on the operation unit 210 of the MFP 101. Thereafter, the process returns to step S802 to repeat the above-described processing.

  As described above, according to the third embodiment, depending on the situation, the user can use the login function of the login module possessed by the embedded login application 330 instead of the custom login module possessed by the login plug-in module 320. As a result, when an “unavailable event” occurs in the custom login module, the login module possessed by the built-in login application can be executed to prevent the occurrence of a failure due to the custom login module.

  In the third embodiment, the VNC connection is described as an example of the event, but the enabling / disabling may be switched according to the occurrence of another event. Other events include, for example, USB cable disconnection and network failure.

(Other embodiments)
The present invention is also realized by executing the following processing. That is, software (program) for realizing the functions of the above-described embodiment is supplied to a system or apparatus via a network or various storage media, and a computer (or CPU, MPU or the like) of the system or apparatus reads the program. It is a process to execute.

  DESCRIPTION OF SYMBOLS 101 ... MFP, 102 ... PC, 103 ... PBX, 201 ... CPU, 210 ... Operation part, 330 ... Built-in login application, 390 ... Custom login application

Claims (5)

An information processing apparatus,
Memory for storing an embedded login application having a plurality of functions including at least a display function for displaying a login screen and an authentication function for performing user authentication based on login information input through the login screen Means,
When a login plug-in module having a display function for displaying the login screen or an authentication function for controlling user authentication is added to the information processing apparatus, the plurality of functions included in the embedded login application are included. Control means for disabling a function corresponding to the function possessed by the login plug-in module and controlling a function corresponding to the function not possessed by the login plug-in module among the plurality of functions to be effective Yes, and
When the function of the embedded login application is a function that does not need to be replaced, the function of the embedded login application corresponding to the function of the login plug-in module is not invalidated, and it relates to one function related to login An information processing apparatus characterized by enabling both functions .   The login plug-in module having a display function for displaying the login screen or an authentication function for performing control for user authentication is dynamically added to the information processing apparatus. Information processing device.   The information processing apparatus according to claim 1, wherein the information processing apparatus is an image forming apparatus having a printing unit. A built-in login application having a plurality of functions including at least a display function for displaying a login screen and an authentication control function for performing user authentication based on login information input through the login screen is stored. A control method of the information processing apparatus,
When a login plug-in module having a display function for displaying the login screen or an authentication function for controlling user authentication is added to the information processing apparatus, the plurality of functions included in the embedded login application are included. A control step of disabling a function corresponding to a function of the login plug-in module and controlling a function corresponding to a function not included in the login plug-in module among the plurality of functions to be valid ;
When the function of the embedded login application is a function that does not need to be replaced, the function of the embedded login application corresponding to the function of the login plug-in module is not invalidated, and it relates to one function related to login Enabling both features, and
A control method characterized by comprising: A built-in login application having a plurality of functions including at least a display function for displaying a login screen and an authentication control function for performing user authentication based on login information input through the login screen is stored. In a computer that controls an information processing apparatus,
When a login plug-in module having a display function for displaying the login screen or an authentication function for controlling user authentication is added to the information processing apparatus, the plurality of functions included in the embedded login application are included. A control procedure for disabling a function corresponding to a function of the login plug-in module and controlling a function corresponding to a function not included in the login plug-in module among the plurality of functions to be valid ;
When the function of the embedded login application is a function that does not need to be replaced, the function of the embedded login application corresponding to the function of the login plug-in module is not invalidated, and it relates to one function related to login Steps to enable both features,
A program to run a program.

Images