Classifications

• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
  • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
  • G06F21/31—User authentication
  • G06F21/34—User authentication involving the use of external additional devices, e.g. dongles or smart cards
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
  • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
  • G06F21/31—User authentication
  • G06F21/33—User authentication using certificates
  • G06F21/335—User authentication using certificates for accessing specific resources, e.g. using Kerberos tickets
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
  • G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
  • G06F21/52—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity ; Preventing unwanted data erasure; Buffer overflow
  • G06F21/53—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity ; Preventing unwanted data erasure; Buffer overflow by executing in a restricted environment, e.g. sandbox or secure virtual machine
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
  • G06F21/60—Protecting data
  • G06F21/606—Protecting data by securing the transmission between two devices or processes
  • G06F21/608—Secure printing
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
  • G06F21/60—Protecting data
  • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
  • G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
  • G06F21/60—Protecting data
  • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
  • G06F21/629—Protecting access to data via a platform, e.g. using keys or access control rules to features or functions of an application
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F9/00—Arrangements for program control, e.g. control units
  • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
  • G06F9/46—Multiprogramming arrangements
  • G06F9/468—Specific access rights for resources, e.g. using capability register
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
  • G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
  • G06F2221/2101—Auditing as a secondary aspect
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
  • G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
  • G06F2221/2117—User registration
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
  • G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
  • G06F2221/2119—Authenticating web pages, e.g. with suspicious links
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
  • G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
  • G06F2221/2141—Access rights, e.g. capability lists, access control lists, access tables, access matrices

Definitions

• the present invention relates to a
• administrator through a user authentication process can execute functions related to system administration.
• a user is made to input a user name and password for the authentication process when a system is used interactively and the system then determines the validity of the user. In other words, if the input user name and password matches the user name and password of the system administrator, the user is recognized as a system administrator.
• Japanese Patent Laid-Open No. 11-259426 an operation method to set a start-up user, which determines which application is executed by what user authority, will be needed. For example, if an application is to be executed using system administration authority, the system administrator must be set as a start-up when installing the application. In this way, there is a problem when using an application in that a significant amount of time is taken to carry out installation of the application, since setting operation of a start-up user of the application is required when installing the application .
• An aspect of the present invention is to eliminate the above-mentioned problems with the conventional technology.
• a special feature of the present invention is that settings of a user who starts up an application do not need, which makes using an application more convenient .
• an information processing apparatus capable of non-interactively executing an application, comprising: storage means for storing an application and a definition file describing a user type having execution authority of the application; issuance means for issuing an access control token according to a user type in response to an issuance request of the access control . token from the
• execution means for causing the application to execute a process in a case that the user type of the access control token issued by the issuance means is included in the user type that possesses the execution authority for the process by the application.
• Fig. 1 is a diagram describing the overall system according to an embodiment of the present invention .
• Fig. 2 is a block diagram that describes the architecture of the MFP and PC according to the embodiment .
• Fig. 3 is a block diagram describing a software configuration of the MFP according to the embodiment .
• Fig. 4 is a diagram describing the MFP process flow as a block diagram, according to the embodiment .
• Fig. 5 is a flowchart describing an
• Fig. 6 is a flowchart describing the process execution and issuing of ACT by MFP 101, according to the embodiment.
• Fig. 7A is a diagram showing an example of an application definition file.
• Fig. 7B depicts a view illustrating an example of a user type list, and
• Fig. 7C depicts a view illustrating an example of an execution authority administrator
• Fig. 1 is a diagram describing the entire system according to an embodiment of the invention.
• An MFP (multi function peripheral) 101 and a PC 102 is connected with a LAN 103, and these devices are connected through the LAN 103, and can communicate both ways.
• a PC 102 is an information processing apparatus such as a personal computer.
• devices that are arranged as the MFP 101 and the PC 102 in the present invention are not limited to MFPs or PCs, for example, a PC may be placed in the position of the MFP 101, and another information terminal may be placed in- the position of the PC 102. Also, many other devices and equipment can be connected to the LAN 103.
• Fig. 2 is a block diagram that describes the architecture of the FP 101 and the PC 102
• a control unit 210 including a CPU 211 controls all operations of the MFP 101.
• Various controls such as a read control of an original that uses a scanner unit 221 whereby a control program stored in a ROM 212 is read out, and a printer control that uses a printer unit 220 are carried out by the CPU 211.
• a RAM 213 is used as a temporary memory space, such as a work area or main memory for CPU 211.
• An HDD 214 stores image data and various programs, or an execute authority management database 341 (Figs. 3, 4).
• a console unit interface unit 215 connects to a console unit 219 and the control unit 210.
• a printer I/F 216 connects to the printer unit 220 and the control unit 210.
• the image data to be printed by the printer unit 220 is forwarded from the control unit 210 to the printer unit 220 via the printer I/F 216, and printed on a sheet (recording medium) by the printer unit 220.
• a scanner I/F 217 connects to the scanner unit 221 and the control unit 210.
• the scanner unit 221 generates image data by reading an image from an original, and then supplies the image data to the control unit 210 via the scanner I/F 217.
• a network I/F 218 connects the control unit 210 (MFP 101) to the LAN 103.
• the network I/F 218 sends image data and various images and various images and various images and various images.
• a network I/F 250 connects the PC 102 with the LAN 103.
• a Web browser 251 connects with the MFP 101 and various equipment on the LAN 103 via the network I/F 250, and displays a Web page based on received HTML data, and transmits data to the MFP 101 and various equipment on the LAN 103.
• Fig. 3 is a block diagram that explains the software configuration of the MFP 101 according to the present embodiment.
• ACT is an abbreviation of Access Control Token, and functions of the MFP 101 that can be used by an application are specified. The following explanation is an explanation in the case where the MFP 101 non-interactively executes an application.
• An application processor 300 is software that exists on the MFP 101, and is achieved by using each component of the control unit 210.
• An application 310 operates on an application execution platform 330. The relationship between the application 310 and the application
• execution platform 330 is similar to the relationship between a Java application and a Java Virtual machine.
• the application 310 can be substituted, and by
• the application 310 can be placed on the application processor 300.
• application 310 is comprised of a request section 311 that requests processing towards an execution section 340, an ACT request section 312 that issues an ACT issuance request towards an ACT generator 321, and an application definition file 314 that describes
• the application definition file 314 describes information concerning under what user authority an application should operate.
• Fig. 7A is a diagram describing an example of the application definition file.
• item "user type,” value
• An ACT issuance unit 320 carries out
• the ACT generator 321 generates an ACT from the ACT request section 312 based on the ACT issuance request.
• An application attribute obtaining section 322 acquires application attributes for the application 310 that are described in the application definition file 314, based on an
• ACT generator 321 When the ACT generator 321 generates an ACT, a user type list '323 is displayed.
• Fig. 7B depicts a view illustrating an example of a user type list.
• the execution section 340 carries out various processing based on a request from the
• the setting section 342 displays and carries out various settings of settings values for the MFP 101.
• the log section 343 writes and acquires logs. When executing processing, the execution authority for each section is checked, and information in the execute authority management database 341 is used.
• Fig. 7C depicts a view illustrating an example of data in the execute authority management database 341.
• processing by the execution section 340 is defined.
• the example in Fig. 7C shows that an Administrator authority is required as a user type in order for the setting section 342 and the log section 343 to carry out processing.
• Fig. 5 is a flowchart describing
• step S501 the Web browser 251 of the PC 102 connects to the application execution platform 330 of the MFP 101.
• user authentication is carried out in step S502.
• any user authentication method may be used, but if the authentication fails, the process proceeds to step S508, and the process is treated as a failed installation, and the process ends.
• step S502 once the user authentication succeeds, the process proceeds to step S503, and installation of the application 310 is carried out via the Web browser 251.
• step S504 the application execution platform 330 installs and emplaces the application 310 on the HDD 214 of MFP 101.
• the application definition file 314 contained in the application 310 can exist as a part of the data that makes up the application 310, or placed in the RAM 213 or the HDD 214 of the MFP 101.
• step S505 a commencement operation of the application 310 is carried out through the Web browser 251.
• the application execution platform 330 deploys the application 310 in the RAM 213 of the MFP 101 in step S506. This allows the
• step S507 the application 310 is executed. The above concludes the installation process flow for the
• Fig. 4 is a block diagram illustrating a process flow of the MFP 101 as a block diagram according to, and Fig. 6 is a flowchart of the same.
• Fig. 6 is a flowchart describing the
• step S601 the ACT request section
• the ACT generator 321 which receives the ACT issuance request then requests the application attribute obtaining section 322 to acquire application attributes (401 in Fig. 4) which are
• the application attribute obtaining section 322 that receives the request to acquire the application attributes then displays the application definition file 314 in step S603, and the application attributes for the
• step S604 the application attribute obtaining section 322 determines whether or not the attributes were able to be obtained, and if they were not obtained, the process proceeds to step S614, and the process ends as if the execution of the process has failed.
• step S604 the process proceeds to step S605, and the application attribute obtaining section 322 returns the obtained application attributes to the ACT generator 321 (403 i Fig. 4).
• step S606 the ACT generator 321 that received the application attributes extracts the user type from the application attributes, and
• step S614 determines whether or not that the extracted user type exists in the user type list 323 (Fig. 7B) . If it is determined that the user type does not exist in the user type list 323, then the process proceeds to step S614 as it cannot issue an ACT, and ends the process a if execution of the process has failed.
• step S606 if the user type exists in the user type list 323, then the process proceeds to step S607, and the ACT generator 321 generates an ACT that corresponds to the user type that is described in the user type list 323 (404 in Fig. 4) .
• step S608 the generated ACT is returned to the ACT request section 312 (405 in Fig. 4) .
• step S609 the process proceeds to step S609, and the ACT request section 312 that receives the ACT saves the ACT 313 in the RAM 213 related to the application 310 (406 in Fig. 4) . This ends the issuance of the ACT.
• the execution process flow that uses the ACT 313 will be explained.
• step S610 the request section 311 requests (issues a process execution request) the execution of the process that is to be executed on the application 310 for the execution section 340 (407 in Fig. 4). At this time, the request section 311 hands the acquired ACT 313 to the execution section 340.
• step S611 the log section 343 that receives the process execution request accesses the execute authority management database 341 (Fig. 7C) , and determines the required user type for the log section 343 to carry out processing.
• step S612 the log section 343
• step S614 determines whether or not the required user type is contained in the received ACT (408 in Fig. 4) . If the required user type is not contained in the ACT, or in other words, if there is no execution authority for the application 310, then the process proceeds to step S614, and the process ends as a failed execution. On the other hand, in step S612, if the user type required to carry out the processing is contained in the ACT 313, or in other words, if the execution authority for the application 310 exists, then the process proceeds to step S613, and the log section 343 executes acquisition of logs and writing of logs (409 in Fig. 4) . While it is not shown here, a specific example of processes such as, the log section 343 acquiring logs, then returning the logs to the application 310, and the application 310 outputting the acquired logs to a file, is given.
• an ACT according to a user type that possesses execution authority for a variety of operations is generated when a plurality of user types are described in the
• application definition file 314. A user type that possesses execution authority for a variety of
• operations includes user types which possess stronger execution authority, or, which can execute limited processes.
• the process is carried out in detail as follows .
• generator 321 receives a plurality of user types
• the user types are compared with the user types described in the user type list 323, and those user types (in Fig. 7B, number "1" is an administrator) that possess execution authority for a wide variety of operations are selected (for instance, the number is smaller in Fig. 7B) .
• the ACT generator 321 generate an ACT according to the selected user types .
• aspects of the present invention can also be realized by a computer of a system or apparatus (or devices such as a CPU or MPU) that read out and execute a program recorded on a memory device to perform the functions of the above-described embodiment ( s ) , and by a method, the steps of which are performed by a
• the computer of a system or apparatus by, for example, reading out and executing a program recorded on a memory device to perform the functions of the above- described embodiment (s) .
• the program is provided to the computer for example via a network or from a recording medium of various types serving as the memory device (for example, computer-readable medium) .

Landscapes

• Engineering & Computer Science (AREA)
• Theoretical Computer Science (AREA)
• Computer Security & Cryptography (AREA)
• Software Systems (AREA)
• Physics & Mathematics (AREA)
• General Engineering & Computer Science (AREA)
• General Physics & Mathematics (AREA)
• Computer Hardware Design (AREA)
• General Health & Medical Sciences (AREA)
• Bioethics (AREA)
• Health & Medical Sciences (AREA)
• Databases & Information Systems (AREA)
• Stored Programmes (AREA)
• Storage Device Security (AREA)

Priority Applications (4)

Applications Claiming Priority (2)

Publications (1)

Family

ID=45097880

Family Applications (1)

Country Status (6)

Families Citing this family (3)

Citations (2)

Family Cites Families (10)

• 2010
  • 2010-06-09 JP JP2010132413A patent/JP5702953B2/ja not_active Expired - Fee Related
• 2011
  • 2011-04-13 KR KR20127033580A patent/KR101489049B1/ko not_active Expired - Fee Related
  • 2011-04-13 EP EP11792224.5A patent/EP2580702B1/en not_active Not-in-force
  • 2011-04-13 WO PCT/JP2011/059671 patent/WO2011155266A1/en not_active Ceased
  • 2011-04-13 CN CN201180027510.2A patent/CN102934124B/zh not_active Expired - Fee Related
  • 2011-04-13 US US13/702,508 patent/US8844027B2/en not_active Expired - Fee Related

Patent Citations (2)

Non-Patent Citations (2)

Also Published As

Similar Documents

Legal Events