JP2012014368A - Key management device, service providing device, access management system, access management method, control program, and computer-readable recording medium - Google Patents

Abstract

[PROBLEMS] To realize flexible role management while ensuring safety.
A role management apparatus 300 includes a service providing apparatus 500 that provides a service in which access restrictions are set for each role, and the service providing apparatus 500 stores data obtained by encrypting a predetermined plaintext with a public key specified at the time of access. Is transmitted to the service providing apparatus 500, and the public key is a descendant ID of the ID when the role name is an ID in the hierarchical ID-based encryption. A secret key corresponding to the public key is a secret key corresponding to the descendant ID calculated by the hierarchical ID-based encryption, and a role storage unit 352 for storing the public key and the corresponding secret key; A role transmitting unit 366 that transmits a public key to the service providing apparatus 500, and data encrypted by the transmitted public key are stored in the role storage unit 352. And a decoder 338 for generating data decoded by the secret key is.
[Selection] Figure 1

Description

  The present invention relates to an access management system that manages access authority to an information service, a key management device that manages an authentication key used when accessing an information service, and the like.

  2. Description of the Related Art Conventionally, as a method for managing access authority to an information service, a role-based access control (RBAC) technique that gives a user permission of an operation according to a role is widely known.

  In access authority management using role-based access control technology, it is necessary to strictly manage the issuance of roles, the association between users and roles, the association between roles and operations, etc. In order to ensure safety, it is usually performed with the authority of a system administrator.

  As a prior art related to the role-based access control technique, there is a technique disclosed in Patent Document 1. Japanese Patent Application Laid-Open No. 2004-228561 discloses a technique for dividing the collective management by a conventional system administrator by dividing the system management jurisdiction into a plurality of parts and delegating authority to each management jurisdiction. Specifically, a policy instance is determined by a sub-administrator to whom a part of authority is delegated.

  As a technique related to access authority management, there is a cross-domain single sign-on technique. For example, “OpenID” and “Shiboleth” are widely known. OpenID is an authentication method that makes it possible to use a common ID and password for a plurality of Web sites. If the ID and password owned by the user are centrally managed and the ID and password are obtained at a certain site (issue site), it is possible to log in using the same ID and password at other sites (use sites) It is said. Thereby, the load of the user's login operation is reduced.

  Shiboleth is a single sign-on authentication method in which user attribute information is exchanged between organizations that have previously formed federations. Access control is performed according to the attribute determination result, and it is possible to provide services across organizations to users who have logged into the federation organization.

Special table 2009-544076 (publication date: December 10, 2009)

  As described above, in the role-based access control technology, in order to perform system management strictly, maintenance of roles and operations is usually performed by a system administrator in a unified manner, and the user himself / herself performs maintenance such as roles. I can't do it. In other words, since safety is important, it is not flexible.

  On the other hand, in the method disclosed in Patent Document 1, since the management authority is divided using role-based access control, some flexibility is ensured. However, as is generally known, if the authority is divided, there is a problem that the security of the system becomes weak. The method disclosed in Patent Document 1 is based on the premise that the system is robust.

  In the method disclosed in Patent Document 1, a role is created by creating an appropriate context instance from a database created by an administrator, and the role attribute is determined by an application module. Since it is not possible to freely operate its own roll, sufficient flexibility is not ensured.

  Note that with OpenID, it is necessary to disclose a password at the use site, and information regarding authority cannot be exchanged safely. Also, in Shiboleth, user authority is managed in accordance with the rules of each organization, so there are restrictions on the types of authority that can be used, authority issuance, authority delegation, and the like, and flexibility is lacking.

  As described above, the conventional access authority management technique has a problem that it does not achieve both safety and flexibility of role management.

  The present invention has been made in view of the above-described problems, and an object thereof is to provide an access management system and the like that realizes flexible role management while ensuring safety.

  In order to solve the above-described problem, a key management apparatus according to the present invention provides a service providing apparatus that provides a service in which access restriction is set for each user group including one or a plurality of users. The encrypted data obtained by encrypting a predetermined plaintext with a designated public key, which is a public key designated by the user at the time of obtaining, from the service providing apparatus, and decrypted with a secret key corresponding to the designated public key As a lower layer ID of the parent ID when the identifier for identifying the user group is a parent ID in hierarchical ID-based encryption. A secret key corresponding to the specified public key is a descendant ID obtained when the parent ID is a public key in public key cryptography. A secret key corresponding to the descendant ID, calculated from the secret key by hierarchical ID-based encryption, and storing the specified public key and the secret key corresponding to the specified public key in association with each other A storage unit, a key transmission unit that transmits the designated public key to the service providing device, and the encrypted data encrypted by the designated public key transmitted by the key transmission unit is stored in the key information storage unit And decrypted data generation means for generating the decrypted data by decrypting with the secret key.

  According to the above configuration, when an identifier for identifying a user group (corresponding to a role name of a role in the embodiment) is a parent ID in the hierarchical ID-based encryption, as an ID below the parent ID A set of the obtained offspring ID and the secret key corresponding to the offspring ID (corresponding to the partial role in the embodiment) is stored in the key information storage unit. And the descendant ID designated by the user when accessing the service is transmitted to the service providing apparatus. Then, the encrypted data (that is, challenge data) obtained by encrypting a predetermined plaintext by the service providing apparatus using the transmitted descendant ID is decrypted with the secret key corresponding to the descendant ID, and decrypted data (that is, response data). Is generated and transmitted to the service providing apparatus. The service providing apparatus performs authentication processing by so-called challenge / response authentication.

  Therefore, even a user who does not belong to a group of users permitted to access the service can respond to challenge / response authentication performed by the service providing apparatus by using the descendant ID and the corresponding secret key. Can do. If the service providing apparatus is configured to permit access to the service when authentication is successful, the service can be accessed.

  Therefore, a user who is not permitted to access the service requests the system administrator by obtaining and using the descendant ID and the corresponding secret key obtained from the identifier of the user group permitted to access the service. Even without this, it is possible to easily access the service. That is, there is an effect that access authority can be easily delegated to a user who is not permitted to access the service.

  It is assumed that users belonging to a group of users permitted to access the service can generate descendant IDs and corresponding secret keys using hierarchical ID-based encryption at their own discretion. The access authority can be delegated flexibly.

  Furthermore, since the service providing apparatus verifies the validity of the descendant ID and the corresponding private key by challenge / response authentication, it is possible to ensure safety.

  Further, in the key management device according to the present invention, in the above configuration, the key information storage unit stores a plurality of sets of the descendant ID and a secret key when the descendant ID is used as a public key in public key cryptography. It is good also as a structure further provided with the key designation | designated means which makes a user designate either of the said descendant ID memorize | stored in the said key information storage part as the said designation | designated public key.

  According to the above configuration, the user can access a service by selecting a desired descendant ID from among a plurality of descendant IDs and using the selected descendant ID and the corresponding private key.

  Furthermore, the key management device according to the present invention is configured so that, in the above configuration, when the key designating unit causes the user to designate one of the descendant IDs stored in the key information storage unit, the validity of the user is determined. It is good also as a structure further provided with the authentication means to authenticate.

  According to the above configuration, since the legitimacy of the user who accesses the descendant ID stored in the key management device is authenticated, the use of the descendant ID by an unauthorized user can be prevented.

  Furthermore, the key management device according to the present invention stores, in the above configuration, a set of the descendant ID and a secret key when the descendant ID is used as a public key in public key cryptography in the key information storage unit. It is good also as a structure further provided with a key storage means.

  According to the above configuration, since the user can store the newly obtained offspring ID and the corresponding secret key from other users or the like in the key information storage unit, the newly obtained offspring ID and the corresponding secret key can be stored. By using, it becomes possible to access the service.

  Furthermore, the key management device according to the present invention, in the above configuration, comprises a hierarchical ID-based encryption from a set of an identifier for identifying the user group and a secret key when the identifier is used as a public key in public key cryptography. It is good also as a structure further provided with the key generation means which produces | generates the group of the said descendant ID and the private key corresponding to this descendant ID using.

  According to the above configuration, the user can generate a set of the descendant ID and the secret key corresponding to the descendant ID. Therefore, by passing the generated descendant ID and the corresponding secret key to another user, Other users can access the service by using the passed offspring ID and the corresponding secret key. That is, there is an effect that delegation of access authority between users can be performed flexibly.

  In order to solve the above-described problem, the service providing apparatus according to the present invention provides a service in which access restriction is set for each user group including one or a plurality of users, and when the user accesses the service. , Encrypting a predetermined plaintext with a designated public key that is a public key designated by the user to generate encrypted data, and managing the decrypted data obtained by decrypting the generated encrypted data with a secret key corresponding to the designated public key When the obtained decrypted data and the plaintext match with each other, the service providing device provides the service to the user when the obtained decrypted data matches the plaintext, wherein the designated public key is an identifier for identifying the user group. This is a descendant ID obtained as a lower layer ID of the parent ID when used as a parent ID in the base encryption, and corresponds to the specified public key. A secret key is a secret key corresponding to the descendant ID calculated by a hierarchical ID-based encryption from a secret key when the parent ID is used as a public key in public key cryptography, and the decrypted data and the plaintext And a service providing means for providing the service that is permitted to access the user group identified by the parent ID of the designated public key to a user who designates the designated public key. It is characterized by.

  According to the above configuration, when the identifier for identifying the user group (in the embodiment, the role name of the role (role) associated with the user group) is the parent ID in the hierarchical ID-based encryption, the parent ID Authentication processing is performed by so-called challenge / response authentication using a set of a descendant ID obtained as a lower layer ID and a secret key corresponding to the descendant ID (partial role in the embodiment). Then, when the authentication is successful, a service in which access is permitted to the user group identified by the parent ID is provided.

  Therefore, when a user who does not belong to a group of users permitted to access the service succeeds in authentication using the descendant ID and the corresponding secret key, the user can be provided with the service. Become.

  Here, assuming that a user belonging to a user group permitted to access the service can generate a descendant ID and a corresponding secret key using hierarchical ID-based encryption by his / her own judgment, By receiving the descendant ID and the corresponding secret key from the user, even a user who is not permitted to access the service can access the service. That is, there is an effect that delegation of access authority between users can be easily and flexibly performed.

  Furthermore, since the validity of the descendant ID and the corresponding secret key is verified by challenge / response authentication, safety can be ensured.

  Further, in the service providing apparatus according to the present invention, in the above configuration, the descendant ID includes limitation information indicating content that limits the provision of the service, and the service providing unit includes the designated public key. The provision of the service may be limited according to the limitation information included in the descendant ID.

  According to said structure, since provision of a service is limited according to limitation information, safety | security can be ensured more highly.

  Furthermore, the service providing apparatus according to the present invention is the above configuration, wherein the limited information is information including a provision date and time of the service, and the service providing means includes the service in the limited information. It is good also as a structure provided at a provision date.

  According to said structure, since provision of a service is limited only to the provision date and time contained in limitation information, safety | security can be ensured higher.

  In order to solve the above problems, an access management system according to the present invention provides a service in which access restrictions are set for each user group composed of one or a plurality of users, and when a user accesses the service. A service providing apparatus that encrypts a predetermined plaintext with a designated public key that is a public key designated by the user to generate encrypted data, and the encrypted data generated by the service providing apparatus corresponds to the designated public key A key management device that generates decrypted data decrypted by a secret key, and the service providing device provides the service to the user when the plaintext matches the decrypted data generated by the key management device. Provided is an access management system, wherein the designated public key uses a hierarchical ID-based encryption as an identifier for identifying the user group. And a secret key corresponding to the specified public key is a secret when the parent ID is a public key in public key cryptography. A secret key corresponding to the descendant ID calculated from the key by hierarchical ID-based encryption, wherein the key management device associates the designated public key with the secret key corresponding to the designated public key And storing the designated public key stored therein to the service providing apparatus, wherein the service providing apparatus matches the plaintext and the decrypted data generated by the key management apparatus. And providing the user who has designated the designated public key with the service permitted to access the user group identified by the parent ID of the designated public key.

  In order to solve the above problem, the access management method according to the present invention provides a service in which access restriction is set for each user group including one or a plurality of users, and the user accesses the service. A service providing apparatus that encrypts a predetermined plaintext with a designated public key that is a public key designated by a user to generate encrypted data, and the encrypted data generated by the service providing apparatus is converted into the designated public key. A key management device that generates decrypted data decrypted with a secret key corresponding to the key, and the service providing device prompts the user when the plaintext matches the decrypted data generated by the key management device. An access management method in an access management system that provides a service, wherein the designated public key is an identifier for identifying the user group When the parent ID in the hierarchical ID-based encryption is a descendant ID obtained as an ID below the parent ID, the private key corresponding to the designated public key is the public key in the public key encryption. A secret key corresponding to the descendant ID calculated from the secret key based on the hierarchical ID-based encryption, wherein the key management device has the specified public key and the secret corresponding to the specified public key. A key is stored in association with each other, and the stored specified public key is transmitted to the service providing apparatus. The service providing apparatus decrypts the plaintext and the key management apparatus. When the data matches, the service that allows access to the user group identified by the parent ID of the designated public key is provided to the user who designated the designated public key It is characterized in Rukoto.

  According to the above configuration, when the key management device uses the identifier for identifying the user group (in the embodiment, the role name of the role associated with the user group) as the parent ID in the hierarchical ID-based encryption. , A set (a partial role in the embodiment) of a descendant ID obtained as an ID below the parent ID and a secret key corresponding to the descendant ID is stored. And the descendant ID designated by the user when accessing the service is transmitted to the service providing apparatus. Then, the service providing apparatus generates encrypted data obtained by encrypting a predetermined plaintext with the transmitted descendant ID. Then, the key management device decrypts with the secret key corresponding to the descendant ID, generates decrypted data, and transmits it to the service providing device. Then, when the plaintext and the decrypted data generated by the key management device match, the service providing device accesses the user group identified by the parent ID of the designated public key to the user who designated the designated public key Provide services that are allowed.

  Therefore, a user who is not permitted to access the service requests the system administrator by obtaining and using the descendant ID and the corresponding secret key obtained from the identifier of the user group permitted to access the service. Even without this, it is possible to easily access the service.

  Here, assuming that a user belonging to a user group permitted to access the service can generate a descendant ID and a corresponding secret key using hierarchical ID-based encryption by his / her own judgment, By receiving the descendant ID and the corresponding secret key from the user, the service can be accessed. That is, there is an effect that delegation of access authority between users can be easily and flexibly performed.

  Furthermore, since the service providing apparatus verifies the validity of the descendant ID and the corresponding secret key by challenge / response authentication, safety can be ensured.

  The key management device and the service providing device may be realized by a computer. In this case, the key management device and the service providing device are realized by a computer by causing the computer to operate as each means. The control program for the key management device and the service providing device to be executed, and the computer-readable recording medium on which the control program is recorded also fall within the scope of the present invention.

  As described above, the key management apparatus according to the present invention provides a service providing apparatus that provides a service in which access restriction is set for each user group including one or a plurality of users when the user accesses the service. The encrypted data obtained by encrypting a predetermined plaintext with a designated public key that is a public key designated by the user is obtained from the service providing apparatus, and the decrypted data decrypted with a secret key corresponding to the designated public key is obtained with the service. A key management device to be transmitted to a providing device, wherein the designated public key is a descendant obtained as an ID below the parent ID when the identifier for identifying the user group is a parent ID in hierarchical ID-based encryption A secret key corresponding to the specified public key is an ID and a secret key when the parent ID is a public key in public key cryptography. A key information storage unit that is a secret key corresponding to the descendant ID, calculated by layer ID-based encryption, and stores the specified public key and the secret key corresponding to the specified public key in association with each other; A key transmitting means for transmitting the designated public key to the service providing apparatus; and a secret stored in the key information storage unit for the encrypted data encrypted by the designated public key transmitted by the key transmitting means. Decrypted data generating means for generating the decrypted data by decrypting with a key.

  Therefore, even a user who does not belong to a group of users permitted to access the service can respond to challenge / response authentication performed by the service providing apparatus by using the descendant ID and the corresponding secret key. Can do. If the service providing apparatus is configured to permit access to the service when authentication is successful, the service can be accessed.

  Therefore, a user who is not permitted to access the service requests the system administrator by obtaining and using the descendant ID and the corresponding secret key obtained from the identifier of the user group permitted to access the service. Even without this, it is possible to easily access the service. That is, there is an effect that access authority can be easily delegated to a user who is not permitted to access the service.

  It is assumed that users belonging to a group of users permitted to access the service can generate descendant IDs and corresponding secret keys using hierarchical ID-based encryption at their own discretion. The access authority can be delegated flexibly.

  Furthermore, since the service providing apparatus verifies the validity of the descendant ID and the corresponding private key by challenge / response authentication, it is possible to ensure safety.

  In addition, the service providing apparatus according to the present invention provides a service in which access restriction is set for each user group including one or a plurality of users, and is designated by the user when the user accesses the service. A predetermined plaintext is encrypted with a designated public key that is a public key to generate encrypted data, and decrypted data obtained by decrypting the generated encrypted data with a private key corresponding to the designated public key is obtained from a key management device, and When the obtained decrypted data matches the plaintext, the service providing apparatus provides the service to a user, and the designated public key uses an identifier for identifying the user group as a parent ID in a hierarchical ID-based encryption. And a secret key corresponding to the specified public key is a descendant ID obtained as an ID below the parent ID. Is a secret key corresponding to the descendant ID, which is calculated by a hierarchical ID-based encryption from a secret key when a public key is used as a public key in the public key cryptography, and when the decrypted data and the plaintext match, Service providing means is provided for providing the above-mentioned service that allows access to the user group identified by the parent ID of the designated public key to a user who designates the designated public key.

  Therefore, when a user who does not belong to a group of users permitted to access the service succeeds in authentication using the descendant ID and the corresponding secret key, the user can be provided with the service. Become.

  Here, assuming that a user belonging to a user group permitted to access the service can generate a descendant ID and a corresponding secret key using hierarchical ID-based encryption by his / her own judgment, By receiving the descendant ID and the corresponding secret key from the user, even a user who is not permitted to access the service can access the service. That is, there is an effect that delegation of access authority between users can be easily and flexibly performed.

  Furthermore, since the validity of the descendant ID and the corresponding secret key is verified by challenge / response authentication, safety can be ensured.

  In addition, the access management system according to the present invention provides a service in which access restrictions are set for each user group including one or a plurality of users, and is designated by the user when the user accesses the service. A service providing apparatus that encrypts a predetermined plaintext with a designated public key that is a public key to generate encrypted data, and the encrypted data generated by the service providing apparatus is decrypted with a secret key corresponding to the designated public key An access management system including a key management device for generating decrypted data, wherein the service providing device provides the user with the service when the plaintext matches the decrypted data generated by the key management device. And the designated public key is an identifier for identifying the user group as a parent ID in the hierarchical ID-based encryption. And a secret key corresponding to the specified public key is obtained from the secret key when the parent ID is a public key in public key cryptography. A secret key corresponding to the descendant ID calculated by base encryption, wherein the key management device stores the designated public key and the secret key corresponding to the designated public key in association with each other, and The stored specified public key is transmitted to the service providing apparatus, and the service providing apparatus transmits the specified public key when the plaintext matches the decrypted data generated by the key management apparatus. Is provided to the user specified by the parent ID of the specified public key.

  In addition, the access management method according to the present invention provides a service in which access restriction is set for each user group including one or a plurality of users, and is designated by the user when the user accesses the service. A service providing apparatus that encrypts a predetermined plaintext with a designated public key that is a public key to generate encrypted data, and the encrypted data generated by the service providing apparatus is decrypted with a secret key corresponding to the designated public key A key management device that generates decryption data, wherein the service providing device is an access management system that provides the user with the service when the plaintext matches the decryption data generated by the key management device. In the access management method, the specified public key uses a hierarchical ID-based encryption as an identifier for identifying the user group. And a secret key corresponding to the specified public key is a secret when the parent ID is a public key in public key cryptography. A secret key corresponding to the descendant ID calculated from the key by hierarchical ID-based encryption, wherein the key management device associates the designated public key with the secret key corresponding to the designated public key And storing the designated public key stored therein to the service providing apparatus, wherein the service providing apparatus matches the plaintext and the decrypted data generated by the key management apparatus. At this time, the service that allows access to the user group identified by the parent ID of the designated public key is provided to the user who designated the designated public key.

  Therefore, a user who is not permitted to access the service requests the system administrator by obtaining and using the descendant ID and the corresponding secret key obtained from the identifier of the user group permitted to access the service. Even without this, it is possible to easily access the service.

  Here, assuming that a user belonging to a user group permitted to access the service can generate a descendant ID and a corresponding secret key using hierarchical ID-based encryption by his / her own judgment, By receiving the descendant ID and the corresponding secret key from the user, the service can be accessed. That is, there is an effect that delegation of access authority between users can be easily and flexibly performed.

  Furthermore, since the service providing apparatus verifies the validity of the descendant ID and the corresponding secret key by challenge / response authentication, safety can be ensured.

It is a block diagram which shows the structure of the role management apparatus contained in the access management system shown in FIG. It is a schematic diagram which shows the structure of the access management system which concerns on one Embodiment of this invention. It is a block diagram which shows the structure of the service provision apparatus contained in the access management system shown in FIG. FIG. 3 is a sequence diagram showing a flow of processing in which a delegated user delivers a partial role to a delegated user in the access management system shown in FIG. 2. It is a schematic diagram of the login screen which the login authentication part in the role management apparatus shown in FIG. 1 provides. FIG. 2 is a schematic diagram of a role management screen provided by a role management unit in the role management apparatus shown in FIG. 1. It is a schematic diagram of the role addition screen which the role update part in the role management apparatus shown in FIG. 1 provides. FIG. 7 is a schematic diagram of a confirmation screen that is displayed to request confirmation from the user when a role deletion instruction is received on the role management screen illustrated in FIG. 6. It is a schematic diagram of the roll issue screen which the partial roll production | generation part in the roll management apparatus shown in FIG. 1 provides. FIG. 3 is a sequence diagram showing a flow of processing for a user to access a service in the access management system shown in FIG. 2. It is a schematic diagram of the service login screen which the login process part in the service provision apparatus shown in FIG. 3 provides. It is a schematic diagram of the authentication confirmation screen which the login authentication part in the role management apparatus shown in FIG. 1 provides. It is a schematic diagram of the role selection screen which the role management part in the role management apparatus shown in FIG. 1 provides. FIG. 14A is a schematic diagram of a confirmation screen provided by the role authentication unit when the authentication by the role authentication unit of the service providing apparatus illustrated in FIG. 3 is successful. FIG. 14B is a schematic diagram of a confirmation screen provided by the role authentication unit when authentication by the role authentication unit of the service providing apparatus illustrated in FIG. 3 fails. FIG. 14C is a schematic diagram of a confirmation screen provided by the role authentication unit when the authentication by the role authentication unit of the service providing apparatus shown in FIG. 3 fails.

  One embodiment of the present invention is described below with reference to FIGS.

(1. Overview of the present invention)
Generally speaking, the access management system 100 according to the present embodiment allows users who are not permitted to access a service for which access restrictions are set for each user group consisting of one or a plurality of users. It is a system that enables access to a service that is not permitted to access by receiving a delegation from a user who is permitted to do so. Hereinafter, a user who performs delegation is referred to as a “delegation user”. In addition, a user who receives a delegation from a delegating user is referred to as a “delegated user”. When the two are not distinguished, they are simply written as users.

  The types of services for which access restrictions are set are not particularly limited, and are any information services such as browsing / acquisition / update of electronic data, database reference / update, use of Web applications, etc. Also good.

  In the access management system 100, a user and a role (Role, role, job) are associated with each other in advance by a system administrator, and a role and an allowed operation (service for which access is permitted) are set. Assume that they are associated. A role is associated with one or more users. That is, the role name for identifying the role is an identifier for identifying the user group.

  The access management system 100 will be further described using roles. In the access management system 100, (1) the delegated user passes a “partial role” (described later) generated from the delegated user role to the delegated user. (2) If the delegated user succeeds in the authentication using the delivered partial role, the authorized user is allowed to access the role of the partial role generation source (hereinafter referred to as the generation source role). Access to the service is allowed.

(1-1. Delegation method)
Here, the access management system 100 uses a generally known “hierarchical ID-based encryption (HIBE)” as a partial role to be transferred from the delegated user to the delegated user. It has a mechanism that can be arbitrarily generated from the role managed by the delegated user. Therefore, delegation from a delegated user to a delegated user can be performed easily and flexibly without asking a system administrator or the like. Note that the hierarchical ID-based encryption technique is a generally known technique, and thus detailed description thereof is omitted in this specification.

  Here, in the present invention, a role name for identifying a role is used as an ID in hierarchical ID-based encryption. Then, when a role name is an ID in hierarchical ID-based encryption, a role having a descendant ID obtained as a lower layer ID of the ID as a role name is a partial role.

  The partial roll consists of the following two data. That is, (1) a role name for identifying a partial role (hereinafter referred to as a partial role name), and (2) a secret key corresponding to the partial role name. The secret key can be calculated (calculated) by hierarchical ID-based encryption from the secret key when the role name of the generation source role is the public key in public key cryptography.

  However, the secret key when the role name associated with the user in advance by the system administrator (that is, the role that is not a partial role) is used as the public key in public key cryptography is issued in advance by a public key issuing organization. Shall be.

  In the present specification, when the partial role and the generation source role are expressed without distinction, they are simply expressed as “roll”.

(1-2. Authentication method)
In addition to the mechanism described above, the access management system 100 determines whether or not the user has been properly delegated by the delegated user (that is, the partial role used for authentication has been legitimately passed from the delegated user). Or not) using a well-known “challenge-response authentication technology”. Therefore, high system safety (security) can be ensured.

  Specifically, (1) encrypting randomly generated random data (plaintext) using the partial role name of the partial role delivered from the delegated user as a public key, and generating encrypted data (2) The generated encrypted data is decrypted with the secret key corresponding to the partial role name to generate the decrypted data. (3) If the generated decrypted data matches the random data, the delegated user is properly delegated. The access to the service that is permitted to access the generation role of the partial role passed from the delegated user is permitted. The encrypted data is also referred to as challenge data. The decrypted data is also referred to as response data.

  Since the challenge / response authentication technique is a widely known technique, a detailed description thereof will be omitted in this specification.

  As an authentication method, in addition to challenge / response authentication, an authentication method using a widely known “electronic certificate” may be considered. However, in the authentication using the electronic certificate, it is necessary to request an external certificate authority to issue the electronic certificate, which is not flexible. Further, when the user functions as a certificate authority, the infrastructure maintenance cost increases. Therefore, challenge-response authentication has an advantage over authentication using an electronic certificate in terms of flexibility and cost.

(1-3. Effects of the Invention)
As can be seen from the above description, according to the present invention, it is possible to easily and flexibly delegate access authority between users, and in addition to high convenience, it is possible to ensure high system safety. It becomes. Furthermore, the cost does not increase greatly in realizing these.

(1-4. Addition of limited information)
The ID in the hierarchical ID-based encryption has a hierarchical structure. For example, if the parent ID is a character string represented by “kaji”, the child ID of the lower layer can be represented, for example, “kaji.yuichi”, and the grandchild ID of the lower layer can be represented by, for example, “kaji. yuichi.2010 ”. In this case, “yuichi” and “2010” are character strings that can be arbitrarily set by the user when generating a child ID and a grandchild ID, respectively. That is, the partial role name can include a character string that can be arbitrarily set by the user.

  For this reason, the partial role name can include limited information representing information for limiting access to the service. As a result, the service providing apparatus 500 can limit access to the service according to the limited information included in the partial role name, and can further increase the security of the system.

  Examples of the contents of restriction include restriction of access date and time (for example, permit only X month Y day), restriction of access contents (for example, permit only browsing), and the like.

  For example, when the limited information for limiting access to June 11 is included in the partial role of the role “kaji”, the partial role name can be set to “kaji.June11”, for example. The service providing apparatus 500 that has received this partial role name limits access so that access is possible only on June 11 even when authentication is successful.

  Similarly, information including service provision date and time may be limited information. And the service provision apparatus 500 can ensure higher safety | security by restrict | providing service provision according to the provision date contained in limitation information.

  However, it is assumed that the description format of the limited information is predetermined. The service providing apparatus 500 can extract the limited information included in the partial role name, and can limit the access according to the extracted limited information.

(2. Application example of the present invention)
Here, a case where the access management system 100 is applied to a system that manages medical information data will be described. Such a system requires tight access restrictions on medical information data, and only a user assigned a specific role such as a doctor needs to be able to access the medical information data.

  For example, when only the “doctor” role is allowed to access the electronic medical record, the “nurse” role cannot access the electronic medical record. However, it may be desirable for nurses to have access to electronic medical records in the absence of a doctor or in an emergency.

  In such a case, if the access management system 100 receives a partial role generated from the “doctor” role (for example, a “doctor's agent” role) from the doctor, the nurse can access the electronic medical record. Become.

  In other words, if the “doctor's agent” role is handed over to the nurse in advance, it becomes possible for the nurse as the agent of the doctor to access the electronic medical record when the doctor is absent.

  At this time, since the doctor can easily generate a partial role from the “doctor” role only by his / her own judgment without requesting the system administrator or the like, delegation of access authority can be performed easily and flexibly. High convenience.

  Furthermore, because the partial roles used by nurses are verified by challenge-response authentication to verify whether they are legitimately delivered by doctors, the system can be secured with high security and prevent unauthorized use. can do.

  In addition, by including limited information such as access date and time in the “doctor's agent” role, it is possible to further limit the access to the electronic medical record of the nurse, so that the safety of the system can be further secured. .

  Note that the present invention is applicable to all information services that require access management. For example, it can be applied to access management of research data at research institutions, electronic libraries at universities, confidential data at corporations, performance data at educational institutions, and the like.

(3. System configuration)
Next, the configuration of the access management system 100 will be described with reference to FIG. FIG. 2 is a schematic diagram showing the configuration of the access management system 100. The access management system 100 includes a user terminal 200, a role management device (key management device) 300, and a service providing device 500. These devices are communicably connected to the communication network 700 directly or via other devices. Note that the communication network 700 is described as being single in FIG. 2, but various communication networks and access networks may be configured in multiple and multiple layers.

  The service providing device 500 is a server device that provides various services in response to access from an external device. The configuration of the service providing apparatus 500 will be described later.

  The user terminal 200 is an apparatus that accesses the service providing apparatus 500 and the role management apparatus 300, and accepts user input operations and displays various screens provided. The user terminal 200 is assumed to be a PC (Personal Computer), a PDA (Personal Digital Assistance), a mobile phone, a smartphone, or the like. It is assumed that the user terminal 200 is owned by each user.

  The role management device 300 is a device that centrally manages a role associated with a user and a partial role delivered from a delegated user. As will be described later, the role managed by the role management apparatus 300 can be added, updated, and deleted by the user himself / herself. The role management apparatus 300 may be a terminal such as a PC, or may be a card such as an IC card that can be attached to and detached from the user terminal 200. The configuration of the role management apparatus 300 will be described later.

  The role management device 300 may be shared by a plurality of users, but is preferably owned by each user in order to increase security. In this embodiment, it shall be owned for every user.

  When the role management device 300 is owned by each user, the role management device 300 may collectively manage roles issued by different organizations. For example, the role management apparatus 300 may manage “doctor” as a role at Hospital A, “part-time doctor” as a role at Hospital B, and “senior member” as a role at Society C.

  Hereinafter, the user terminal 200 and the role management device 300 owned by the delegated user will be referred to as the user terminal 200A and the role management device 300A, respectively, and the user terminal 200 and the role management device 300 owned by the delegated user will each be a user terminal. 200B and role management device 300B are distinguished from each other. When they are not distinguished from each other, they are simply referred to as the user terminal 200 and the role management device 300.

  In the present embodiment, the user terminal 200 and the role management device 300 are described as separate devices, but are not necessarily separate devices, and may be provided as an integrated device. In the case of being provided as an integrated device, the communication exchange between the user terminal 200 and the role management device 300 is performed within the integrated device.

(4. Outline of processing)
Next, an outline of processing performed in the access management system 100 will be described with reference to FIG. Since details of the process will be described later, only the outline will be described here.

  The processing performed in the access management system 100 includes (A) a process in which a delegated user delivers (delegates) a partial role to a delegated user, and (B) a delegated user authenticates using the partial role. It can be roughly divided into processing that enables access to services.

  In the process (A), first, the delegating user operates the user terminal 200A to access the role management apparatus 300A, and the role management apparatus 300A generates a partial role from the role of the delegation user (FIG. 2). (A1)). Then, the generated partial role is transferred to the delegated user ((A2) in FIG. 2). The means for passing the partial role to the delegated user is not particularly limited, and an e-mail attached with the partial role may be transmitted, or the recording medium storing the partial roll may be sent by mail or by hand. May be passed to Then, the delegated user stores the transferred partial role in the role management apparatus 300B.

  Next, in the process (B), the delegated user specifies a partial role stored in the role management apparatus 300B when accessing the service provided by the service providing apparatus 500 using the user terminal 200B. Then, the partial role name (specified public key) of the specified partial role is transmitted to the service providing apparatus 500 ((B1) in FIG. 2). Subsequently, challenge / response authentication is performed between the service providing apparatus 500 and the role management apparatus 300B ((B2) in FIG. 2). Specifically, the service providing apparatus 500 generates encrypted data (challenge data) obtained by encrypting random data (predetermined plaintext) using the partial role name transmitted from the role management apparatus 300B as a public key. Subsequently, the role management device 300B decrypts the encrypted data acquired from the service providing device 500 with the secret key corresponding to the transmitted partial role name to generate decrypted data (response data). Subsequently, the service providing apparatus 500 determines whether or not the decrypted data acquired from the role management apparatus 300B matches the random data.

  If it is determined that the random data matches the decrypted data, the user terminal 200B to the service permitted to access the role identified by the parent ID of the partial role name transmitted from the role management device 300B Is permitted ((B3) in FIG. 2).

(5. Configuration of each device)
Next, the configuration of each device included in the access management system 100 will be described with reference to FIGS. 1 and 3.

(5-1. Configuration of Role Management Device)
First, FIG. 1 is a block diagram illustrating a configuration of the role management apparatus 300. As shown in the figure, the role management apparatus 300 includes at least a communication unit 310, a control unit 330, and a storage unit 350.

  The communication unit 310 allows the role management device 300 to communicate with external devices (the user terminal 200 and the service providing device 500) via the communication network 700.

  Next, the control part 330 controls operation | movement of each part with which the roll management apparatus 300 is provided. The control unit 330 controls various units of the roll management apparatus 300 by reading various programs stored in the storage unit 350 and performing predetermined arithmetic processing, and includes a CPU (Central Processing Unit), a memory, and the like. Can be configured. A detailed configuration of the control unit 330 will be described later.

  The storage unit 350 stores various programs and data. Specifically, the control unit 330 executes (1) a control program for each unit, (2) an OS (Operating System) program, (3) an application program, and (4) various data read when these programs are executed. Etc. are memorized. The storage unit 350 is configured by a nonvolatile storage device such as a flash memory, for example. The storage unit 350 has a work area configured by a volatile storage device such as a RAM (Random Access Memory). The work area is for temporarily storing data in the process of executing the above-described various programs by the control unit 330.

  The storage unit 350 further includes a user information storage unit 351 and a role storage unit (key information storage unit) 352.

  The user information storage unit 351 stores user information (a combination of a user name and a password) for user authentication of a user who accesses the role management apparatus 300 from the user terminal 200.

  Next, the roll storage unit 352 stores one or a plurality of rolls. Specifically, one or more pairs of a role name for identifying a role and a secret key when the role name is used as a public key for public key encryption are stored. The role includes a role associated with the user by the system administrator and a partial role generated by the delegated user. Note that the secret key corresponding to the role name of the role previously associated with the user by the system administrator is issued by a public key issuing organization. Also, the secret key corresponding to the partial role name is generated by the delegate user.

  Note that the storage unit 350 is not necessarily provided in the roll management apparatus 300, and may be configured to be connected to the roll management apparatus 300 via a cable or a communication network 700 as an external apparatus.

  Next, the control unit 330 will be described in detail. The control unit 330 includes a login authentication unit (authentication unit) 331, a role management unit (key designation unit) 333, and a decryption unit (decryption data generation unit) 338.

  The login authentication unit 331 performs user authentication (verifies the validity of the user). When the user terminal 200 directly accesses, a “login screen” is provided to the user terminal 200. Further, when the user terminal 200 that has accessed the service providing apparatus 500 accesses by the redirect specified by the service providing apparatus 500, an “authentication confirmation screen” is provided to the user terminal 200. Screen examples of the login screen and the authentication confirmation screen will be described later.

  Then, the login authentication unit 331 performs user authentication by checking whether or not the user information (user name and password) input on these screens is stored in the user information storage unit 351.

  Next, generally speaking, the role management unit 333 performs addition, update, and deletion of roles stored in the role storage unit 352, generation of partial roles, and transmission of role names to the service providing apparatus 500. Is.

  The role management unit 333 provides a “role management screen” to the user terminal 200 when the user authentication by the login authentication unit 331 is successful (1) when the user terminal 200 directly accesses the role management unit 333. On the other hand, (2) when the user terminal 200 is accessed by redirection, a “role selection screen” is provided to the user terminal 200.

  The “role management screen” displays a list of role names stored in the role storage unit 352, adds roles to be stored in the role storage unit 352, and deletes roles stored in the role storage unit 352. It is a screen for receiving an instruction and a delegation instruction to a delegated user. A screen example of the role management screen will be described later.

  On the other hand, the “role selection screen” is a screen for displaying a list of role names stored in the role storage unit 352 and accepting selection of roles. A screen example of the role selection screen will be described later.

  The role management unit 333 further includes a role update unit (key storage unit) 334, a partial roll generation unit (key generation unit) 335, and a role transmission unit (key transmission unit) 336.

  When the role update unit 334 receives a role addition instruction on the role management screen, the role update unit 334 provides the user terminal 200 with a “role addition screen” for adding a role. A screen example of the role addition screen will be described later. Then, on the role addition screen, a set of the role name and the secret key corresponding to the role name is stored in the role storage unit 352.

  Further, when the role update unit 334 receives a role deletion instruction on the role management screen, the role update unit 334 stores a set of the role name (public key) instructed to be deleted and a secret key corresponding to the role name in a role storage. It is deleted from the part 352.

  Next, the partial role generation unit 335 generates a partial role from the generation source role using hierarchical ID-based encryption. Specifically, when a delegation instruction is received on the role management screen, a role issue screen for generating a partial role to be transferred to the delegated user is provided to the user terminal 200. A screen example of the roll issue screen will be described later. Then, on the role issuance screen, an input of a partial roll generation condition (specifically, a partial role name) is accepted and a partial role is generated according to the input generation condition. Specifically, a partial role name and a secret key when the partial role name is used as a public key are generated. The generated secret key is notified to the delegated user by displaying it in the role issuing screen.

  Next, the role transmitting unit 336 transmits the role name to the service providing apparatus 500. Specifically, in order to use the role name of the role selected on the role selection screen as a public key in challenge / response authentication executed by the role authentication unit 533 (described later) of the service providing apparatus 500, It transmits to the service providing apparatus 500.

  Next, the decryption unit 338 receives the encrypted data (challenge data) generated in the challenge / response authentication executed by the role authentication unit 533 of the service providing apparatus 500. Then, a secret key corresponding to the role name of the role selected on the role selection screen is read from the role storage unit 352, and the received encrypted data is decrypted with the read secret key to generate response data. Then, the generated response data is returned to the service providing apparatus 500.

(5-2. Configuration of Service Providing Device)
Next, FIG. 3 is a block diagram illustrating a configuration of the service providing apparatus 500. As shown in the figure, the service providing apparatus 500 includes at least a communication unit 510, a control unit 530, and a storage unit 550.

  The communication unit 510 is for the service providing apparatus 500 to communicate with external apparatuses (the user terminal 200 and the role management apparatus 300). The communication unit 510 is configured to be connectable to the communication network 700. Although not shown, the communication unit 510 performs communication such as a LAN (Local Area Network) or a router between the communication unit 510 and the communication network 700. Necessary structures are provided as appropriate.

  Next, the control part 530 controls operation | movement of each part with which the service provision apparatus 500 is provided. The control unit 530 controls each unit of the service providing apparatus 500 by reading various programs stored in the storage unit 550 and performing predetermined arithmetic processing, and may be configured by a CPU, a memory, and the like. it can. A detailed configuration of the control unit 530 will be described later.

  The storage unit 550 stores various programs and data. Specifically, the control unit 530 executes (1) a control program for each unit, (2) an OS program, (3) an application program, and (4) various data read when these programs are executed. Is. The storage unit 550 is configured by a non-volatile storage device such as a flash memory, for example. The storage unit 550 has a work area configured by a volatile storage device such as a RAM. The work area is used for temporarily holding data in the process in which the control unit 530 executes the various programs described above.

  Storage unit 550 includes authority information storage unit 551 and service data storage unit 552.

  The authority information storage unit 551 stores user information and roles in association with each other, and stores roles and permitted operations (access restrictions on services) in association with each other.

  The service data storage unit 552 stores a data group constituting various services.

  The storage unit 550 is not necessarily provided in the service providing apparatus 500, and may be configured to be connected to the service providing apparatus 500 via a cable or a communication network 700 as an external apparatus.

  Next, the control unit 530 will be described in detail. The control unit 530 includes a login processing unit 531, a role authentication unit 533, and a service providing unit (service providing unit) 537.

  When accessed from the user terminal 200, the login processing unit 531 provides the user terminal 200 with a service login screen for performing user authentication. In the service login screen, it is possible to specify the address (URL: Uniform Resource Locator) of the role management device 300B so that the delegated user can use the transferred partial role. A screen example of the service login screen will be described later.

  Then, when the address of the role management device 300 is specified on the service login screen, the login processing unit 531 transfers (redirects) the access from the user terminal 200 to the role management device 300 of the specified address. ).

  Next, when the role authentication unit 533 receives the role name from the role transmission unit 336 of the role management apparatus 300, the role authentication unit 533 executes challenge / response authentication. That is, it generates encrypted data (challenge data) obtained by encrypting randomly generated random data using the received role name as a public key, and transmits the generated encrypted data to the role management apparatus 300. Subsequently, as the response, it is determined whether or not the response data returned from the decryption unit 338 of the role management apparatus 300 matches the random data. If they match, it is assumed that the authentication is successful. If they do not match, the processing is interrupted assuming that the authentication has failed.

  Next, when the role authentication unit 533 succeeds in authentication, the service providing unit 537 permits access from the user terminal 200 and performs processing for providing a service. First, the role management device 300 is notified of the login address for the service providing device 500, and the access from the user terminal 200 to the role management device 300 is transferred (redirected) to the notified address.

  When the user terminal 200 accesses the address notified above, the service providing unit 537 has authority to restrict access to the service associated with the role name acquired from the role management apparatus 300 by the role authentication unit 533. Obtained from the information storage unit 551. When the role name acquired from the role management apparatus 300 is a partial role name, the access restriction to the service associated with the role name of the generation source role is acquired from the authority information storage unit 551. Then, a data group constituting the service is acquired from the service data storage unit 552, and the service is provided to the user terminal 200 according to the acquired access restriction. At that time, when the limited information is included in the role name acquired from the role management apparatus 300, the provision of the service is limited according to the limited information.

  Although not shown, the service providing apparatus 500 may include an input unit 570 and a display unit 590.

  The input unit 570 receives an input from the administrator of the service providing apparatus 500 and transmits an input signal corresponding to the input to the control unit 530. The input unit 570 may be anything that allows the administrator to make a desired input, and is assumed to be a mouse or a keyboard.

  The display unit 590 is a display device that displays a screen for setting, maintenance, and the like based on an instruction from the control unit 530. For example, an LC display panel, an EL display panel, a CRT display device, or the like can be used as the display portion 590.

(5-3. Configuration of user terminal)
Although not shown, the user terminal 200 communicates with external devices (the role management device 300 and the service providing device 500) via the communication network 700, and various screens provided by the role management device 300 and the service providing device 500. A display unit such as a liquid crystal panel to be displayed, an input unit such as a mouse and a keyboard for receiving user input, and a control unit configured by a CPU, a memory, and the like that control these units.

(6. Specific processing flow)
(6-1. Flow of processing in which delegated user delivers partial role to delegated user)
Next, the details of the flow of processing in which the delegated user delivers the partial role to the delegated user will be described with reference to FIG. FIG. 4 is a sequence diagram showing a flow of processing in which a delegated user delivers a partial role to a delegated user.

  First, processing performed on the delegated user side will be described. The delegated user operates the user terminal 200A to access the role management device 300A in order to generate a partial role to be transferred to the delegated user (sequence (hereinafter simply referred to as “S”) 11). On the other hand, the login authentication unit 331 of the role management apparatus 300A provides a login screen to the user terminal 200A (S12). Then, the delegated user operates the user terminal 200A and inputs user information (user name and password) on the login screen (S13).

  When the user authentication is successful, the role management unit 333 of the role management device 300A provides a role management screen to the user terminal 200A (S14). Then, the delegating user operates the user terminal 200A to instruct to perform delegation on the role management screen (S15). In response to this, the partial role generation unit 335 of the role management device 300A provides a role issue screen to the user terminal 200A (S16).

  Then, when the delegated user operates the user terminal 200A and inputs a partial role generation condition (specifically, a partial role name) (S17), the partial role generation unit 335 of the role management apparatus 300A is input. A partial role is generated according to the generation conditions, and the secret key of the generated partial role is notified to the delegate user (displayed in the role issue screen) (S18).

  Through the above flow, the delegated user obtains a partial role to be transferred to the delegated user. Then, the delegated user passes the partial role to the delegated user (S19).

  Next, processing performed on the delegated user side will be described. When the delegated user accesses the role management device 300B by operating the user terminal 200B in order to register the transferred partial role in the role management device 300B, the role management unit 333 of the role management device 300B displays the role management screen. Is provided to the user terminal 200B (S21 to S24). Note that the processes of S21 to S24 are the same as the processes of S11 to S14, respectively.

  Then, the delegated user operates the user terminal 200B to instruct addition of a role on the role management screen (S25). In response to this, the role update unit 334 of the role management device 300B provides a role addition screen to the user terminal 200B (S26).

  Then, the delegated user stores the partial role delivered in step S19 in the role storage unit 352 by inputting it on the role addition screen (S27, S28).

(6-2. Screen example)
Next, an example of a screen provided in the above-described process will be described with reference to FIGS.

  FIG. 5 is a schematic diagram of a login screen provided by the login authentication unit 331. As shown in the figure, the user name and password can be input on the login screen.

  Next, FIG. 6 is a schematic diagram of a role management screen provided by the role management unit 333. As shown in the figure, the role management screen displays a list of role names. In this example, role names “aaaa.faculty”, “bbbb.member”, “cccc.member.premium”, and “dddd-system.guest” are displayed.

  In addition, a button B1 shown in the figure is a button for receiving a role addition instruction. A button B2 shown in the figure is a button for accepting an instruction to delete a role displayed in a pair with the button.

  A button B3 shown in the figure is a button for receiving a delegation instruction, and is a button for receiving an instruction (delegation instruction) for generating a partial role based on the role displayed in a pair with the button.

  Next, FIG. 7 is a schematic diagram of a role addition screen provided by the role update unit 334. The input field F1 is a field for inputting a role name (public key) to be added. In this example, a role name “eeee-u.lecture.June10” is input. This roll is a partial roll of “eeee-u.lecture”. The input field F2 is a field for inputting a corresponding secret key.

  Next, FIG. 8 is a schematic diagram of a confirmation screen displayed for requesting confirmation from the user when a role deletion instruction is received on the role management screen.

  Next, FIG. 9 is a schematic diagram of a roll issue screen provided by the partial roll generation unit 335. In the display field D1, the role name of the role that is the generation source of the partial role is displayed. In this example, the role name “aaaa.faculty” is displayed.

  The input field F3 is a field for inputting an arbitrary character string. A character string obtained by concatenating the role name displayed in the display field D1 and the character string input in the input field F3 becomes the role name of the newly generated partial role. In the example shown in the figure, the role name of the partial role is “aaaa.faculty.assistant.June11”.

  When the button B4 shown in the figure is pressed, the role name formed by connecting the role name displayed in the display field D1 and the character string input in the input field F3 by the partial role generation unit 335 is used as the public key. The generated secret key is generated, and the generated secret key is displayed in the display field D2.

(6-3. Flow of processing for user to access service)
Next, with reference to FIG. 10, the details of the flow of processing for a user to access a service will be described. FIG. 10 is a sequence diagram illustrating a flow of processing in which a user accesses a service. The process flow when the delegated user accesses the service and the process flow when the delegated user accesses the service are common, and will be described together.

  First, when the user operates the user terminal 200 to access the service providing apparatus 500 (S31), the login processing unit 531 of the service providing apparatus 500 provides a service login screen to the user terminal 200 (S32).

  In order to read and use a role from the role management apparatus 300, the user designates the address of the role management apparatus 300 on the service login screen (S33). The login processing unit 531 of the service providing device 500 transfers (redirects) access from the user terminal 200 to the designated address (S34, S35).

  Next, the login authentication unit 331 of the role management apparatus 300 provides an authentication confirmation screen to the user terminal 200 (S36). Then, the user operates the user terminal 200 and inputs user information on the authentication confirmation screen (S37).

  When the user authentication is successful, the role transmission unit 336 of the role management device 300 provides a role selection screen to the user terminal 200 (S38).

  Then, when the user operates the user terminal 200 to select a role to be used for challenge / response authentication on the role selection screen (S39), the role transmission unit 336 of the role management device 300 causes the role of the selected role to be selected. The name is transmitted to the service providing apparatus 500 (S40).

  Subsequently, when the role authentication unit 533 of the service providing apparatus 500 receives the partial role name, it generates encrypted data (challenge data) obtained by encrypting randomly generated random data using the received partial role name as a public key. At the same time, the generated encrypted data is transmitted to the role management apparatus 300 (S41).

  Then, when the decryption unit 338 of the role management device 300 acquires the encrypted data (challenge data) from the service providing device 500, the role storage unit stores the secret key corresponding to the partial role name of the partial role selected on the role selection screen. The encrypted data acquired from the service providing apparatus 500 is decrypted with the read secret key, and response data is generated. Then, the generated response data is returned to the service providing apparatus 500 (S42).

  Then, the role authentication unit 533 of the service providing apparatus 500 determines whether or not the response data acquired from the role management apparatus 300 matches the generated random data. The address for login to the service providing apparatus 500 is notified to 300 (S43).

  Then, the role management device 300 logs in the service providing device 500 by transferring (redirecting) the access of the user terminal 200 to the notified address (S44 to S46). After logging in, the user terminal 200 can access the service.

  Through the above flow, the user can authenticate using the role and access the service.

  In order to maintain a communication session between the role management device 300 and the service providing device 500, it is preferable to include session information in the communication data as necessary. In the example of FIG. 10, the session ID is included in the communication shown in S34 and S40 to S42 so that it is understood that the communication is in the same session. However, if the access management system 100 has a separate session management function, it is not necessary to include session information in the communication data.

  Moreover, it is preferable that communication between apparatuses is protected by a widely known encryption technique (for example, SSL (Secure Sockets Layer)).

(6-4. Screen example)
Next, an example of a screen provided in the above-described process will be described with reference to FIGS.

  FIG. 11 is a schematic diagram of a service login screen provided by the login processing unit 531. The input field F4 is a field for inputting the address of the role management apparatus 300. FIG. 11 shows a state where an address “http://rs.aaaa.jp/” is input.

  Next, FIG. 12 is a schematic diagram of an authentication confirmation screen provided by the login authentication unit 331 of the role management apparatus 300. As shown in the figure, the user name and password can be entered on the authentication confirmation screen.

  Next, FIG. 13 is a schematic diagram of a role selection screen provided by the role management unit 333 of the role management apparatus 300. As shown in the figure, the role selection screen displays a list of role names in a selectable manner. In this example, a role having a role name “bbbb.member” is selected.

  Next, FIG. 14A is a schematic diagram of a confirmation screen provided by the role authentication unit 533 when the authentication by the role authentication unit 533 of the service providing apparatus 500 is successful. FIG. 14B and FIG. 14C are schematic diagrams of confirmation screens provided by the role authentication unit 533 when the authentication by the role authentication unit 533 of the service providing apparatus 500 fails.

(7. Reference form)
As a reference form according to the present invention, a form for realizing provision of an organic service between different organizations will be described.

  As described above with reference to FIG. 10, when a user accesses a service provided by the service providing apparatus 500, the user transmits a role stored in the role management apparatus 300 to the service providing apparatus 500.

  Therefore, by registering in advance the role for which access is permitted in the service providing apparatus 500, it is possible to determine whether or not access is possible according to the role transmitted from the role management apparatus 300. That is, even if the access is from a user who has not registered user information in the service providing apparatus 500, the access can be permitted as long as the user has a role for which access is permitted.

  As a specific example, mutual use of electronic library services between universities will be described. Specifically, an example in which a student at University B accesses an electronic library service provided at University A will be described.

  First, it is assumed that University A permits University B students to access the electronic library service provided by University A service providing apparatus 500. It should be noted that the user information of the university B student is not registered in the university A service providing apparatus 500. Instead, it is assumed that the “University B Student” role is registered in advance in the service providing apparatus 500 of the University A as a role for permitting access. In addition, it is assumed that the B University student has registered the “B University Student” role in the role management apparatus 300 owned by the B University.

  In this case, the University B student accesses the University A service providing apparatus 500 in sequence S31 in the process flow described with reference to FIG. 10, and then selects the “University B student” role in sequence S39. . As a result, it is possible to log in to the service providing apparatus 500 of University A in sequence S45.

  In this way, by performing the processing described with reference to FIG. 10, it is possible to provide an organic service between organizations.

  Another specific example is a tie-up service between different organizations. For example, in the case of a member user of an online store at an X store, a service for discounting the purchase price of an online store at a Y store is provided at the Y store. In this case, the user can receive a discount service at the Y store by registering the “X store member” role in the role management device 300 owned by the user.

(8. Supplementary notes)
Each control unit described above may be realized by software using a CPU, or may be configured as hardware by a logic circuit formed on an integrated circuit (IC chip).

  When implemented by software, the service providing apparatus 500, the role management apparatus 300, and the user terminal 200 are configured such that a CPU that executes instructions of a control program that realizes each function, a ROM that stores the program, a RAM that expands the program, A storage device (recording medium) such as a memory for storing the program and various data is provided. An object of the present invention is to provide program codes (execution format program, intermediate code program, source program) of control programs for the service providing apparatus 500, the role management apparatus 300, and the user terminal 200, which are software for realizing the functions described above. The readable recording medium is supplied to the service providing apparatus 500, the role management apparatus 300, and the user terminal 200, and the service providing apparatus 500, the role management apparatus 300, and the computer in the user terminal 200 (or CPU or MPU (Micro This can also be achieved by the processing unit)) reading and executing the program code recorded on the recording medium.

  Examples of the recording medium include tapes such as magnetic tapes and cassette tapes, magnetic disks such as floppy (registered trademark) disks / hard disks, and disks including optical disks such as CD-ROM / MO / MD / DVD / CD-R. IC cards (including memory cards) / optical cards, semiconductor memories such as mask ROM / EPROM / EEPROM / flash ROM, logic circuits such as PLD (Programmable Logic Device), etc. it can.

  The service providing apparatus 500, the role management apparatus 300, and the user terminal 200 may be configured to be connectable to a communication network, and the program code may be supplied via the communication network. The communication network is not particularly limited. For example, the Internet, intranet, extranet, LAN, ISDN, VAN, CATV communication network, virtual private network, telephone line network, mobile communication network, satellite communication. A net or the like is available. Further, the transmission medium constituting the communication network is not particularly limited. For example, even in the case of wired such as IEEE 1394, USB, power line carrier, cable TV line, telephone line, ADSL line, etc., infrared rays such as IrDA and remote control, Bluetooth ( (Registered trademark), IEEE802.11 radio, HDR (High Data Rate), NFC (Near Field Communication), DLNA (Digital Living Network Alliance), mobile phone network, satellite line, terrestrial digital network, etc. .

  The present invention is not limited to the above-described embodiments, and various modifications can be made within the scope shown in the claims, and embodiments obtained by appropriately combining technical means disclosed in different embodiments. Is also included in the technical scope of the present invention.

  The present invention can be applied to an access management system that manages access authority to an information service, a key management device that manages an authentication key used when accessing the information service, and the like.

100 Access management system 200, 200A, 200B User terminal 300, 300A, 300B Role management device (key management device)
331 Login authentication unit (authentication means)
333 Role management unit (key designation means)
334 Role update unit (key storage means)
335 Partial roll generation unit (key generation means)
336 Roll transmission unit (key transmission means)
338 Decryption unit (decoded data generation means)
351 User information storage unit 352 Roll storage unit (key information storage unit)
500 Service Providing Device 533 Role Authentication Unit 537 Service Providing Unit (Service Providing Means)

Claims (14)

A service providing apparatus that provides a service in which access restrictions are set for each user group composed of one or a plurality of users is predetermined by a designated public key that is a public key designated by the user when the user accesses the service. The encrypted data obtained by encrypting the plaintext of the key is transmitted from the service providing apparatus, and the decrypted data decrypted with the secret key corresponding to the designated public key is transmitted to the service providing apparatus,
The designated public key is a descendant ID obtained as an ID below the parent ID when the identifier for identifying the user group is a parent ID in the hierarchical ID-based encryption.
The secret key corresponding to the designated public key is a secret key corresponding to the descendant ID, calculated by hierarchical ID-based encryption from a secret key when the parent ID is used as a public key in public key cryptography. ,
A key information storage unit that stores the designated public key and a secret key corresponding to the designated public key in association with each other;
Key transmitting means for transmitting the designated public key to the service providing device;
Decrypted data generating means for decrypting the encrypted data encrypted by the designated public key transmitted by the key transmitting means with a secret key stored in the key information storage unit and generating the decrypted data; A key management device comprising: The key information storage unit stores a plurality of sets of the descendant ID and a secret key when the descendant ID is used as a public key in public key cryptography.
The key management apparatus according to claim 1, further comprising a key designating unit that allows a user to designate any one of the descendant IDs stored in the key information storage unit as the designated public key.   3. The authentication means for authenticating the validity of the user when the key specifying means causes the user to specify any of the descendant IDs stored in the key information storage unit. The key management device described in 1.   The key storage means for storing in the key information storage unit a pair of the descendant ID and a secret key when the descendant ID is used as a public key in public key cryptography. The key management device according to any one of the above.   A secret key corresponding to the descendant ID and the descendant ID using a hierarchical ID-based encryption from a set of an identifier for identifying the user group and a secret key when the identifier is used as a public key in public key cryptography. The key management apparatus according to claim 1, further comprising key generation means for generating a pair of the key management unit and the key management unit. Provide a service in which access restrictions are set for each user group composed of one or a plurality of users, and when the user accesses the service, a predetermined plaintext is designated by a designated public key that is a public key designated by the user. Is generated from the key management device, and the obtained decrypted data and the plaintext coincide with each other. The decrypted data obtained by decrypting the generated encrypted data with the private key corresponding to the designated public key is obtained from the key management device. A service providing device for providing the service to the user,
The designated public key is a descendant ID obtained as an ID below the parent ID when the identifier for identifying the user group is a parent ID in the hierarchical ID-based encryption.
The secret key corresponding to the designated public key is a secret key corresponding to the descendant ID, calculated by hierarchical ID-based encryption from a secret key when the parent ID is used as a public key in public key cryptography. ,
When the decrypted data and the plaintext match, the service that allows access to the user group identified by the parent ID of the designated public key is provided to the user who designated the designated public key A service providing apparatus comprising service providing means. The above-mentioned descendant ID includes limited information indicating the content that limits the provision of the above service,
The service providing means is:
The service providing apparatus according to claim 6, wherein the provision of the service is limited according to the limitation information included in the descendant ID that is the designated public key. The limited information is information including the service provision date and time,
The service providing apparatus according to claim 7, wherein the service providing unit provides the service at the provision date and time included in the limited information. Provide a service in which access restrictions are set for each user group composed of one or a plurality of users, and when the user accesses the service, a predetermined plaintext is designated by a designated public key that is a public key designated by the user. A service providing device for generating encrypted data by encrypting
A key management device for generating decrypted data obtained by decrypting the encrypted data generated by the service providing device with a secret key corresponding to the designated public key,
The service providing device is an access management system that provides the service to a user when the plaintext matches the decrypted data generated by the key management device,
The designated public key is a descendant ID obtained as an ID below the parent ID when the identifier for identifying the user group is a parent ID in the hierarchical ID-based encryption.
The secret key corresponding to the designated public key is a secret key corresponding to the descendant ID, calculated by hierarchical ID-based encryption from a secret key when the parent ID is used as a public key in public key cryptography. ,
The key management device is
Storing the designated public key and a secret key corresponding to the designated public key in association with each other, and transmitting the stored designated public key to the service providing apparatus;
The service providing apparatus includes:
When the plaintext and the decrypted data generated by the key management device match, the user who designates the designated public key is allowed to access the user group identified by the parent ID of the designated public key An access management system characterized by providing the service described above. Provide a service in which access restrictions are set for each user group composed of one or a plurality of users, and when the user accesses the service, a predetermined plaintext is designated by a designated public key that is a public key designated by the user. A service providing device for generating encrypted data by encrypting
A key management device for generating decrypted data obtained by decrypting the encrypted data generated by the service providing device with a secret key corresponding to the designated public key,
The service providing apparatus is an access management method in an access management system that provides the user with the service when the plaintext matches the decrypted data generated by the key management apparatus,
The designated public key is a descendant ID obtained as an ID below the parent ID when the identifier for identifying the user group is a parent ID in the hierarchical ID-based encryption.
The secret key corresponding to the designated public key is a secret key corresponding to the descendant ID, calculated by hierarchical ID-based encryption from a secret key when the parent ID is used as a public key in public key cryptography. ,
The key management device is
Storing the designated public key and a secret key corresponding to the designated public key in association with each other, and transmitting the stored designated public key to the service providing apparatus;
The service providing apparatus includes:
When the plaintext and the decrypted data generated by the key management device match, the user who designates the designated public key is allowed to access the user group identified by the parent ID of the designated public key An access management method characterized by providing the service described above.   A control program for operating a computer included in the key management device according to any one of claims 1 to 5, wherein the control program causes the computer to function as each unit.   A control program for operating a computer included in the service providing apparatus according to any one of claims 6 to 8, wherein the control program causes the computer to function as each of the means.   The computer-readable recording medium which recorded the control program of Claim 11. A computer-readable recording medium on which the control program according to claim 12 is recorded.

Images