JP2011165073A - System, method and program for exchanging attribute information - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To effectively evaluate the reliability of an ID provider that is a providing source of attribute information. <P>SOLUTION: The system includes a Web application 401 that is a Web server which provides a Web service by web application execution; and an IdP400 which stores attribute information of a user of a browser device to be used in the web application execution. The Web application 401 includes a means for obtaining a message to be transmitted from the Web application 401 to the IdP400 when obtaining attribute information from the IdP 400 in the web application execution; a means for specifying and storing an obtaining destination of attribute information in the Web server based on the content of the message; and a means for calculating an evaluation value based on the use frequency as the obtaining destination of attribute information that is the use frequency of stored attribute exchange history information. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a system for managing attribute information used at the time of service execution in a web server.

When a client such as a browser uses a web service (web service) provided by a web server, attribute information such as personal information provided from the client side is required.
In order for a web service system to operate, the system (server) on the web service provider side usually holds personal information necessary for the operation, and provides the web service by performing an operation based on this information. Do. In this case, the user needs to register for each Web service system that uses personal information.

  However, when registering personal information for each Web service system to be used, the user must register his / her personal information in many different places, and for the user, leakage of registered personal information Risks such as unauthorized use will be amplified. In addition, the operator of the Web service system that is the registration destination of personal information must also securely store and manage the registered personal information. For this reason, attribute information such as registered personal information is stored on the Web server. A specification (standard specification for attribute exchange) for safe exchange on the side has been developed and used.

Here, the attribute exchange refers to a specific Id provider (IdP: Identity) in which attribute information is held in advance by a Web server that provides a Web service, for example, attribute information such as personal information necessary for the operation of the Web service system. Obtained from the provider).
Typical specifications include ID-WSF (Liberty Identity Web Service Framework) that defines an open standard specification-based method for developing a web service with an authentication function, and one URL (Uniform Resource Locator) as an ID. OpenID AX (Attribute Exchange), which is a mechanism for realizing the authentication of different websites on the Internet using the Internet.

Note that a method for determining which IdP is used to acquire necessary attribute information for providing a Web service is different for each specification.
For example, in ID-WSF, an IdP or WSP (Web Service Provider) determined to be reliable on the operating Web service system side is set as an attribute exchange destination. In OpenID, the IdP designated by the user is set as the attribute exchange destination. In the case of OpenID, a device corresponding to IdP may be called an OP (OpenID provider).

  This attribute exchange system allows users to limit the registration destination of personal information to some extent, and the Web service system operator (provider) does not have to store and manage personal information more than necessary. There is.

  However, in general, there are a plurality of Web service systems that acquire attribute information from one IdP (that is, attribute exchange with one IdP), and the user also uses a plurality of IdPs as registration destinations. When the number of Web service systems used by users increases, the number of IdP selected as the master data registration destination of personal information increases for each Web service system, and the number of Web service systems for which attribute exchange is performed increases. Become.

For this reason, it may be difficult to trace back what attribute exchange the user has performed for which Web service system.
Furthermore, for example, when the user wants to update his / her personal information for using the Web service system, it is difficult to determine which IdP should store the information stored therein. is there.

As a related technique for this, techniques for performing attribute exchange by associating user attribute information (user information) provided to a web server are disclosed (Patent Documents 1 and 2).
Further, as this related technique, a technique for calculating an evaluation value of an intrusion detection system based on detection information collected from a plurality of different intrusion detection systems is disclosed (Patent Document 3).

JP 2007-323340 A Special table 2007-521580 gazette JP 2004-30286 A

In a web service system (web server), the accuracy of personal information obtained from IdP is regarded as important. For this reason, in the Web service system, it is desired that the Web service system itself exchange attributes with the IdP trusted as the acquisition source of personal information (attribute information).
On the other hand, prior to using the Web service system, the Web service user (client side) selects an IdP that stores (registers) the personal information of the user.

  On the other hand, in the related arts in Patent Documents 1 and 2, the user is not presented with a criterion indicating which IdP should store personal information, that is, a criterion for selecting and specifying an IdP. There is an inconvenience that the user cannot appropriately select a registration destination of personal information.

  In this case, a mechanism for evaluating IdP is required to indicate the accuracy of registered personal information (attribute information) and its standards. For example, when the mechanism is operated by a service provider or IdP side. For example, if the evaluation information and the evaluation standard are illegally operated on the service provider side, there may be a disadvantage that the evaluation information and the evaluation standard are not appropriate judgment criteria for the user.

[Object of invention]
The present invention provides an attribute information exchange system, an attribute information exchange method, and a method for effectively evaluating the reliability of an identity provider (attribute information providing apparatus) that is a provider of attribute information for a web server, by improving the disadvantages of the related technology. The purpose is to provide an attribute information exchange program.

  In order to achieve the above object, an attribute information exchange system according to the present invention includes a web server that provides a web service by executing a web application preset in response to a service request from a browser device, and the web An attribute information exchange system comprising an attribute information providing device that holds attribute information of the browser device user used when executing an application, wherein the web server is configured to execute the web application from the attribute information providing device. When acquiring the attribute information, a message acquisition device that acquires a message to be sent to the attribute information providing device, and the acquisition destination of the attribute information in the web server based on the content of the message Attribute exchange history storage device for storing as attribute exchange history information And an attribute exchange reliability evaluation device that calculates an evaluation value indicating the reliability as the acquisition destination of the attribute information corresponding to each of the attribute information providing devices based on the use frequency of the stored attribute exchange history information. The structure is taken.

  The attribute information exchanging method according to the present invention is used when a web server that provides a web service by executing a web application preset in response to a service request from a browser device, and when the web application is executed. An attribute information exchange system comprising: an attribute information providing device that holds attribute information of the browser device user; and a genus exchange history recording device that specifies an acquisition destination of the attribute information acquired by the web server, An attribute information exchanging method for evaluating an attribute information providing apparatus as an acquisition destination of the attribute information, wherein the web server acquires the attribute information from the attribute information providing apparatus for execution of the web application. A message sent from the device to the attribute information providing device Acquired by the recording device, the attribute exchange history recording device specifies an acquisition destination of the attribute information in the web server based on the content of the message, stores the acquisition destination as attribute exchange history information, and stores the stored attribute An evaluation value indicating reliability as an acquisition destination of the attribute information is calculated in correspondence with each of the attribute information providing devices based on the usage frequency of the exchange history information.

  An attribute information exchange program according to the present invention is used when a web server that provides a web service by executing a web application that is set in advance in response to a service request from a browser device, and when the web application is executed. An attribute information exchange system comprising: an attribute information providing device that holds attribute information of the browser device user; and a genus exchange history recording device that specifies an acquisition destination of the attribute information acquired by the web server, An attribute information exchange program for evaluating an attribute information providing apparatus as an acquisition destination of the attribute information, wherein the web server acquires the attribute information from the attribute information providing apparatus for execution of the web application Messages sent from the web server to the attribute information providing device A message acquisition function for acquiring the attribute information, an attribute exchange history storage function for performing processing for specifying the acquisition destination of the attribute information in the web server based on the content of the message and storing the acquisition destination as attribute exchange history information, and the storage Causing the computer to execute an attribute exchange reliability evaluation function for calculating an evaluation value indicating the reliability as an acquisition destination of the attribute information corresponding to each of the attribute information providing devices based on the frequency of use of the attribute exchange history information that has been made It is characterized by.

  Since the present invention is configured and functions as described above, according to this, when the web server acquires attribute information for executing a web application from the attribute information providing apparatus, the web server sends the attribute information providing apparatus to the attribute information providing apparatus. Means for acquiring a message, means for specifying an acquisition destination of attribute information in the web server based on the content of the message, means for storing the acquisition destination as attribute exchange history information, and based on the stored attribute exchange history information Means for calculating an evaluation value indicating the frequency of use as an attribute information acquisition destination, thereby effectively evaluating the reliability of an identity provider (attribute information providing apparatus) that is a provider of attribute information to a web server. It is possible to provide an attribute information exchange system, an attribute information exchange method, and an attribute information exchange program.

It is a sequence chart which shows the operation | movement content of the attribute exchange in ID-WSF which is the general specification which concerns on the attribute information exchange system by this invention. It is a sequence chart which shows the operation | movement content of the attribute exchange in OpenID AX which is the general specification which concerns on the attribute information exchange system by this invention. It is a schematic block diagram which shows one Embodiment in the attribute information exchange system by this invention. It is explanatory drawing which shows an example of the connection relation structure of the attribute exchange log | history recording apparatus in the attribute information exchange system disclosed in FIG. It is a schematic block diagram which shows an example of an internal structure of the attribute exchange log | history recording apparatus in the attribute information exchange system disclosed in FIG. FIG. 4 is a sequence chart showing operation processing steps in which attribute exchange is performed in the attribute information exchange system disclosed in FIG. 3. It is explanatory drawing which shows an example of the data content of the consent confirmation service request in the attribute information exchange system disclosed in FIG. It is explanatory drawing which shows an example of the data content of the consent confirmation service response in the attribute information exchange system disclosed in FIG. FIG. 4 is a sequence chart showing operation processing steps in which attribute exchange is performed in the attribute information exchange system disclosed in FIG. 3. FIG. 10A shows an example of the data content of the attribute exchange request in the attribute information exchange system disclosed in FIG. 3, and FIG. 10B is an explanatory diagram showing an example of the data content of the attribute exchange response. It is explanatory drawing which shows an example of the data content of the attribute exchange log | history information in the attribute information exchange system disclosed in FIG. It is a schematic block diagram which shows an example of an internal structure of the voting apparatus in the attribute information exchange system disclosed in FIG. It is explanatory drawing which shows an example of the data content of the evaluation data in the attribute information exchange system disclosed in FIG. It is explanatory drawing which shows an example of the data content of the evaluation data in the attribute information exchange system disclosed in FIG. It is explanatory drawing which shows an example of the data content of the evaluation data in the attribute information exchange system disclosed in FIG.

[Embodiment]
Next, embodiments for carrying out the present invention will be described with reference to the drawings.

  As shown in FIG. 3, the attribute information exchange system according to the embodiment of the present invention is connected to a public network (network) 500 such as the Internet and responds to a request sent via the network 500 with a Web. A Web server (hereinafter referred to as “Web application”) 301 that provides a Web service by executing an application, and an IdP 300 that stores and holds pre-registered user attribute information that is required when the Web application is executed. ing.

In the present embodiment, Web applications 302 and 401 that provide Web services set in advance in response to requests sent via the network 500 are connected to the network 500 in the same manner as the IdP 300. The IdP 350, 360, and 400 each store and hold pre-registered attribute information.
The IdPs 300, 350, 360, and 400 are ID (identity) providers as computer apparatuses that store and hold different attribute information registered in advance, respectively, in response to requests from Web applications (Web service systems). An attribute information providing function for providing previously registered attribute information.

  In addition, the attribute information exchange system according to the present embodiment specifies the attribute information for the attribute information acquired from the IdP (300, 350, 360, or 400) by each of the Web applications (301, 302, 401). The attribute exchange history recording device 200 that acquires and analyzes information (attribute information identification information) via the network 500, and each IdP (300, 350, 360, or 400) based on the analysis result by the attribute exchange history recording device 200 A voting device 600 that performs an evaluation on the use frequency of attribute information and the reliability of IdP, and a Web client that uses a Web service provided by connecting to the network 500 via the attribute exchange history recording device 200 and provided by a Web application Device (hereinafter referred to as “Web browser”) 1 And it has a configuration in which the 0.

  In this embodiment, similarly to the attribute exchange history recording apparatus 200, an attribute exchange history recording apparatus 201 that acquires and analyzes attribute information specifying information of attribute information exchanged between the IdP and the Web application via the network 500 is obtained. Are connected to the network 500 and the attribute exchange history recording device 201, and like the voting device 600, the frequency of use of attribute information and the reliability of the IdP in each IdP (300, 350, 360, or 400) A voting device 601 that performs such evaluation, is connected to the network 500 via the attribute exchange history recording device 201, and uses a Web service provided by a Web application similar to the Web browser 100. A configuration having a browser 101 is provided.

  The Web client devices (hereinafter referred to as “Web browsers”) 100 and 101 are computers on which general Web browsers for using Web applications operate, and are connected via the attribute exchange history recording devices 200 and 201, respectively. Are connected to the network 500.

  The attribute exchange history recording apparatus 200 (attribute exchange history recording apparatus 201) includes a general reverse proxy server function that operates based on attribute exchange standard specifications such as ID-WSF and OpenID AX (FIG. 5).

Further, when the attribute exchange (message exchange) is performed via the attribute exchange history recording apparatus 200, the attribute exchange source (acquisition destination), the attribute provision destination, the exchange attribute name, the exchange, and the like as the attribute exchange history from the message. It has an attribute exchange extraction function that extracts and stores the date and time.
Here, as a storage method, for example, it is assumed that the data is stored in a CSV (comma delimited) file format that is stored in a relational database (RDB) table.

  Further, the attribute exchange history recording apparatus 200 has an attribute exchange history information providing function for providing the content of the stored attribute exchange history to the browser (user) in an information format that can be confirmed by the user. .

  Further, the attribute exchange history recording apparatus 200 has a function (SSL negotiation function) for performing SSL (Secure Socket Layer) negotiation via the network 500 instead of the Web browsers 100 and 101, and a network 500 as shown in FIG. When the data sent via the Web browser 100 is transferred to the Web browser 100, the hyperlink destination included in the data and the URL whose redirect destination is the HTTPS communication path are converted to the link destination of the HTTP communication path. It has the function to do.

  As a result, the attribute exchange history recording apparatus 200 performs SSL negotiation instead of the Web browser 100, so that when the network 500 is viewed from the Web browser 100, any URL appears to be connectable via the HTTP communication path. The attribute exchange history recording apparatus 200 can acquire the content of HTTPS communication performed by the Web browser 100.

  Assume that the Web applications (301, 302, 401) are Web servers connected to the network 500, respectively.

The IdP 300 (IdP 350, IdP 360, IdP 400) has an attribute information storage function for storing user attribute information (personal information) registered in advance.
The web service system 301, the web service system 302, and the web service system 401 provide a web service to the user based on a request from the user (having a web server function).

  The IdP 300 and the Web service systems 301 and 302 are implemented with ID-WSF, and attribute exchange based on the ID-WSF specification is performed between the IdP 300 and the Web service system 301. The attribute information exchanged (attribute exchange) between the IdP and the Web service system is assumed to be address information (address) and a telephone number (tel).

  Further, it is assumed that the IdP 400 and the Web service system 401 are each equipped with OpenID AX and perform attribute exchange based on the OpenID AX. The attribute information exchanged between the IdP 400 and the Web service system 401 is address information (address).

  As a result, in the present embodiment, based on standard attribute exchange specifications such as ID-WSF and OpenID AX, messages are exchanged between the Web application and IdP using the redirect function of the Web browser.

  The voting device 600 has a unique voting device ID, is connected to the network 500, and has an evaluation value calculation function for calculating an evaluation value of IdP based on attribute exchange history information acquired from the attribute exchange device 200. Shall.

The voting device 600 has a function of creating evaluation data based on the calculated evaluation value and storing the evaluation data (evaluation data management function).
Furthermore, the voting device 600 has a P2P anonymous data sharing function for exchanging evaluation data with a voting device 601 that is another voting device (for example, 601) by anonymous P2P data exchange.

  Like the voting device 600, the voting device 601 is a computer device that has a unique voting device ID and is connected to the network 500. Here, the voting device 601 is based on the attribute exchange history in the attribute exchange device 201. , A function for calculating an evaluation value of IdP (evaluation value calculation function) and a function for creating and storing evaluation data based on the calculated evaluation value (evaluation data management function).

  Further, the voting device 601 has a P2P anonymous data sharing function for exchanging evaluation data with the voting device 600 which is another voting device by anonymous P2P data exchange, and evaluation data stored in the other voting device. And a function of transmitting the evaluation data to the Web browser (evaluation data totaling transmission function).

Furthermore, the voting devices 600 and 601 have an evaluation data identifier setting function for setting an evaluation data identifier for the generated evaluation data.
Thus, the voting devices 600 and 601 can be set not to use the evaluation result from the same site (Web application) a plurality of times based on the evaluation data identifier while maintaining anonymity.

  Since many sites refer to evaluation results generated by other sites, the validity of the evaluation results can be set by not using the evaluation results from the same site (Web application) multiple times. Can be improved.

Furthermore, the voting devices 600 and 601 may be configured to set a validity period for evaluation results from the same site.
As a result, it is possible to delete past information after a certain period from the P2P data distribution network.

  In the present embodiment, an attribute exchange specification model using the redirect function of a web browser is assumed, and an attribute exchange history recording device is newly installed between a general web browser and a web service system. The Web service system that records, analyzes, and uses electronic messages exchanged between the IdP and the WSP can notify the user retroactively from which IdP or WSP the attribute information is received.

  In addition, by evaluating the attribute exchange history based on the IdP usage frequency, the reliability frequency from the Web service system, etc., and sharing the evaluation information via a P2P network among multiple users, a specific individual, business It is possible to realize an IdP evaluation mechanism in which an arbitrary operation of evaluation information by a person or the like is difficult to enter.

Also, in this embodiment, it is possible to easily grasp the exchange status of personal information stored for each Web service system by recording when and by which Web service system personal information of the user is exchanged with the Web service system. Is what
Furthermore, IdP evaluation is performed based on the exchange history of personal information based on IdP usage frequency, Web service system reliability frequency, etc., and IdP evaluation information is shared among multiple users via the P2P network. .
This realizes an IdP evaluation mechanism in which arbitrary operation of evaluation information by a specific individual, business operator, or the like is difficult to enter.

[Description of Operation of Embodiment]
Next, an outline of the overall operation of the first embodiment will be described.
When the web server 401 acquires attribute information from the IdP (attribute information providing apparatus) 300 for executing the web application, the attribute exchange history recording apparatus 200 acquires a message transmitted from the web server 401 to the IdP 300 ( Message acquisition process).
Here, the attribute exchange history recording apparatus 200 identifies the IdP 400 from which the attribute information is acquired in the web server 401 based on the content of the message, and stores the IdP 400 as attribute exchange history information (attribute exchange history storage step).
Next, the attribute exchange history recording apparatus 200 calculates an evaluation value corresponding to the IdP 400 based on the usage frequency of the stored attribute exchange history information, corresponding to the IdP 400 (attribute exchange reliability evaluation). Process).

  Here, regarding the message acquisition step, the attribute exchange history storage step, and the attribute exchange reliability evaluation step, the execution contents may be programmed and executed by a computer.

  Next, the operation of Interaction Service in ID-WSF, which is a general specification, will be described based on the sequence chart of FIG. 1 as a technique for exchanging attributes using the redirect function of a Web browser.

This ID-WSF is performed between a Web browser, an SP (Service Provider) that requests a personal attribute and provides a service, and a WSP that provides a personal attribute.
In addition, the arrow of the broken line in FIG. 1 shall show the message undefined by the specification of ID-WSF.

  First, the Web browser (service request source) requests a service (Web service) from the SP (step S001). In response to the service request from the Web browser, the SP requests the WSP for personal attributes of the accessor (service request source) necessary for providing the Web service (step S002).

Next, the WSP requests the accessor's consent (accessor consent) to pass the personal attribute to the SP (step S003).
The SP makes a consent confirmation service request with redirection to the Web browser so as to access the WSP in order to agree to the provision of the personal attribute (step S004).

  When the WSP receives an agreement confirmation service request for the request from the SP (step S004) from the Web browser, the WSP requests the Web browser for consent to provide personal attributes to the SP (how to obtain consent, etc .: Step S005).

  When the Web browser obtains consent to provide personal attributes to the SP (how to obtain consent, etc .: step S005), the WSP sends an consent confirmation service response to the SP using the web browser redirect. It is issued to (Step S006).

The SP that has received the consent confirmation service response makes an attribute request to the WSP together with the result of the consent confirmation service (step S007).
The WSP that has received the consent confirmation service response and the attribute request returns the personal attribute to the SP (step S008).
Thereby, SP acquires a personal attribute. Next, the SP that acquired the personal attribute executes the requested service and provides the service to the Web browser (service response: step S009).

Next, the operation of OpenID AX, which is a general technique for exchanging attributes using the redirect function of the Web browser, will be described based on the sequence chart of FIG.
As shown in FIG. 2, the OpenID AX actor includes a Web browser, an RP (Relying Party) that requests a personal attribute and provides a service, and an OP that provides a personal attribute.

First, the web browser sends a service request to the RP to make a service request (step S101). At this time, the Web browser transmits a service provision request and an OpenID together with the RP.
Next, the RP makes an association establishment request with the OP in order to provide a service in response to the service request sent (step S102).

Next, the OP sends an association establishment response to the RP (step S103). The RP that has established the association with the OP transmits an attribute exchange request accompanied by redirection in the Web browser together with the association handle to the Web browser (step S104).
Next, the OP that has received the attribute exchange request of S104 from the Web browser performs an attribute exchange response including the personal attribute (step S105).
At this time, the attribute included in the response is only the personal attribute for which the user has permitted the attribute exchange in advance.

As a result, the RP receives the attribute exchange response via the redirect of the Web browser (step S105), analyzes this response (attribute exchange response) message, and extracts and acquires the personal attribute.
Further, the RP provides the service to the Web browser by executing the service based on the acquired personal attribute (step S106).

  Next, in the configuration of the present embodiment (FIG. 3), the operation of recording attribute exchange history information indicating when the personal information of the user was exchanged between which IdP and the Web service system is shown in FIG. This will be described with reference to FIG.

Here, the Web service system 301 exchanges attributes with the IdP 300 using ID-WSF.
The operation steps corresponding to the standard specification (ID-WSF) sequence shown in FIG. 1 are assigned the same step numbers (S001 to S008). In addition, step numbers A001 to A005 are given to operation processing steps performed in the attribute exchange history recording apparatus 200 in the present embodiment.

  In the present embodiment, the HTTP request from the Web browser (here, 100) is always transmitted to the Web application via the reverse proxy server function (FIG. 5) of the attribute exchange history recording apparatus 200. And

First, a web browser (service request source) requests the provision of a service (web service) by transmitting a service request to the web application (web server) 301 (service provision request: step S001).
In response to the service request from the Web browser, the Web application requests the IdP 300 for personal information (attribute information) of the Web browser user (accessor) necessary for executing the Web service (attribute request: step S002). ).

Next, the IdP 300 requests the web application 301 for user consent for passing the personal attribute corresponding to the sent attribute request to the web application 301 (requesting user consent: step S003).
The Web application 301 transmits an agreement confirmation service request for requesting access to the IdP 300 in order to agree to the provision of personal attributes to the Web browser 100 (step S004).
The consent confirmation service request includes a redirect request, and the consent confirmation service request is transmitted to the Web browser 100 via the attribute exchange history recording device 200.

Next, the Web browser 100 transmits the consent confirmation service request sent from the Web service system 301 to the IdP 300 using redirection.
At this time, the attribute exchange history recording apparatus 200 acquires the consent confirmation service request and analyzes the data content of the consent confirmation service request (attribute exchange analysis function: step A001).

An example of the content of the consent confirmation service request is shown in FIG. It is assumed that the consent confirmation service request includes information as to which attribute is agreed to be exchanged, as shown in FIG.
Here, the attribute exchange history recording apparatus 200 extracts the Web service system 301 as the attribute providing destination, the IdP 300 as the attribute providing source, the attribute name for exchanging the attribute as the exchange attribute name, and the address in this example (attribute exchange extraction function These are stored in the attribute exchange history DB (step A002), and this consent confirmation service request is transmitted to the IdP 300.

As a result, the IdP 300 that has received the consent confirmation service request from the Web browser 100 obtains consent to provide personal attributes to the SP (step S005).
Next, the IdP 300 that has obtained the user agreement for attribute exchange transmits an agreement confirmation service response to the web service system 301 in a form accompanied by redirection in the web browser 100 (step S006).

At this time, the attribute exchange history recording apparatus 200 acquires the consent confirmation service response sent via redirection in the Web browser 100 and analyzes the data content of the consent confirmation service response (attribute exchange analysis function: step A003). .
An example of the consent confirmation service response is shown in FIG. As shown in FIG. 8, the consent confirmation service response includes information (character string) indicating whether or not the user has agreed to exchange attribute information (that is, to provide to the Web application 301). It is.

  Here, when a message (consent confirmation service response) that allows attribute exchange is transmitted via the attribute exchange history recording device 200, the attribute exchange history recording device 200 determines the attribute from the data content of the consent confirmation service response. A record indicating that the providing destination is the Web service system 301, the attribute providing source is the IdP 300, and the exchange attribute name is “address” recorded in the above step A001 is extracted, and the attribute exchange date / time is updated based on this (attribute) Exchange extraction function).

  On the other hand, when a message that does not permit attribute exchange (consent confirmation service response) is sent, a process of deleting the corresponding record is performed (step A004).

  Here, similarly to the attribute exchange between the IdP 300 and the Web application, the history of attribute exchange between the IdP 300 and the Web service system 302 is also stored in the attribute exchange history recording apparatus 200. Here, for example, it is assumed that the attribute providing destination is the Web service system 301, the attribute providing source is the IdP 300, and the exchange attribute name is tel.

When the user of the Web browser 100 wants to refer to his / her attribute exchange history information, the attribute exchange history recording apparatus 200 makes an attribute exchange history display request by making an attribute exchange history display request to the attribute exchange history recording apparatus 200. The attribute exchange history information corresponding to the display request is output and displayed (attribute exchange history display function: step A005).
As a result, the user of the Web browser 100 can refer to the attribute exchange history information stored in the attribute exchange history recording device 200, and the exchange state of the personal information stored for each Web service system (Web application) can be checked. I can grasp it.

  Next, the Web application 301 makes an attribute request to the IdP 300 again (step S007), and the IdP 300 returns attribute information permitted for this attribute request (attribute return: step S008).

  Next, when attribute exchange using OpenID AX is performed between the Web application 401 and the IdP 400 in the configuration of the present embodiment (FIG. 3), the personal information of the user is between which IdP and the Web service system. An operation for recording attribute exchange history information indicating when the exchange has been performed will be described with reference to FIGS. 5 and 9.

  In addition, the same step number (S101-S105) shall be attached | subjected to the operation step corresponding to the sequence of the standard specification (OpenID AX) shown in FIG. In addition, step numbers A001 to A005 are given to operation processing steps performed in the attribute exchange history recording apparatus 200 in the present embodiment.

  In this embodiment, an HTTP request from a web browser (here, 100) is always transmitted to the web application 401 via the reverse proxy server function (FIG. 5) of the attribute exchange history recording device 200. Shall.

First, the web browser 100 transmits a service request message to the web application 401. At this time, the Web browser 100 requests provision of a service (Web service) by transmitting the service request together with the OpenID (step S101).
This service request and OpenID are transmitted to the Web application 401 via the attribute exchange history recording apparatus 200.

Next, the Web application 401 makes an association establishment request to the IdP 400 in order to provide a service in response to the sent service request (step S102).
In response to the association establishment request from the Web application 401, the IdP 400 transmits an association establishment response (Step S103).
As a result, an association is established between the Web application 401 and the IdP 400. Here, the Web application 401 transmits an attribute exchange request accompanied by an association handle and a Web browser redirection to the Web browser 100 (step S104).

Thus, the attribute exchange request transmitted from the Web service system 401 is redirected by the Web browser 100 and transmitted to the IdP 400.
At this time, the attribute exchange history recording apparatus 200 acquires the redirected attribute effect request, analyzes the data content of the attribute exchange request, and transmits the attribute exchange request to the IdP 400.

Here, FIG. 10A shows an example of the data content of the consent confirmation service request. It is assumed that the attribute exchange request includes information indicating which attribute is agreed to be exchanged (in the rectangle of FIG. 10A).
At this time, the attribute exchange history recording apparatus 200 records the Web service system 401 as the attribute providing destination, the IdP 400 as the attribute providing source, and the attribute name (here, “address”) for performing asdfa attribute exchange as the exchange attribute name (step A101). ).
Note that the attribute exchange history recording apparatus 200 performs the same processing as in steps A001 and A002 in step A101.

  Next, the IdP 400 transmits an attribute exchange response corresponding to the sent attribute exchange request to the Web application (service system) 401 with a redirect of the browser 100 (step S105).

At this time, the attribute exchange history recording apparatus 200 analyzes the content of the attribute exchange response sent via the browser 100 by redirection.
Here, an example of the attribute exchange response is shown (inside the rectangle in FIG. 10B). In this attribute exchange response, as shown in FIG. 10B, it is assumed that a character string indicating the type of attribute information to be exchanged is included.

  Here, when the attribute exchange history is determined from the data content of the attribute exchange response, the attribute exchange history recording apparatus 200 determines that the attribute providing destination is the Web service system 401, the attribute providing source is the IdP 400, and the exchange attribute name is Step A101. The exchange date of the record “address” recorded in the above is updated.

If the attribute value to be exchanged cannot be determined from the message of the attribute exchange response, the corresponding record is deleted (step A102).
Note that the attribute exchange history recording apparatus 200 also performs the same processing as in steps A003 and A004 in step A102.

  Here, an example of the attribute exchange history information stored in the attribute exchange history recording apparatus 200 is shown in FIG. Thereby, the user can always know which Web service system performed attribute exchange with which IdP by referring to the information (FIG. 11) stored in the attribute exchange history recording apparatus 200. It becomes.

  Next, the operation in which the attribute exchange history recording apparatus 200 calculates the evaluation value of each IdP based on the acquired attribute exchange history as described above will be described with reference to FIG.

  First, the voting device 600 acquires an attribute exchange history (information) from the attribute exchange history recording device 200 (step B001), and calculates an evaluation value of IdP based on the data content of the attribute exchange history (evaluation value calculation). Function: Step B002).

  Here, the IdP to be evaluated is an IdP recorded (registered) in the attribute exchange history. As an evaluation method, for each registered IdP, for example, the number of counterparts (Web servers) that have performed attribute exchange ( The number of attribute exchange partners) and the number of evaluation elements indicating the number of attribute types that have been exchanged are calculated by adding points to each evaluation value of each IdP.

Here, as a criterion for adding points, for example, 5 points are given for each Web service system in which attribute exchange is performed, and 1 point is given for each attribute exchanged attribute.
For example, the IdP 300 registered in the attribute exchange history exchanges one attribute with the Web service system 301 and exchanges one attribute with the Web service system 301. Since the IdP 400 exchanges one attribute with the Web service system 401, the evaluation value of the IdP 300 is calculated as 12 points (5 + 1 + 5 + 1), and the evaluation value of the IdP 400 is calculated as 6 points (5 + 1).

  Here, as described above, an IdP that performs many attribute exchanges is set to have a high evaluation value because it is judged to be highly used and trusted by many users and Web service systems. Shall be.

Next, the voting apparatus 600 creates evaluation data for each IdP based on the evaluation value calculated in step B002 (evaluation data creation function: step B003).
Here, the evaluation data includes an evaluation data identifier, an IdP name, an evaluation value, and an effective period (FIG. 12). Assume that the evaluation data identifier is generated by hashing a character string connecting the IdP name character string and the voting device ID character string. In addition, the valid period is designated as an arbitrary period when the evaluation data is created, for example, one year from the evaluation data creation time.

Next, the voting apparatus 600 stores the created evaluation data (evaluation data management function: step B004).
Here, when the evaluation data identifiers of the already stored evaluation data match at the time of execution of the evaluation data saving process, the newly created evaluation data is the latest, so that the evaluation data is replaced.

Also, it is assumed that the voting device 601 has created evaluation data from the attribute exchange history recording device 201 as in the case of step B003.
Here, it is assumed that the attribute exchange history recording apparatus 201 has an attribute exchange history different from that of the attribute exchange history recording apparatus 200, and holds evaluation values of IdP350 and IdP360 in addition to IdP300.

Here, an example of the evaluation data held by the voting device 601 is shown in FIG.
The voting device 600 exchanges evaluation data by transmitting the evaluation data of each IdP stored in the evaluation data management function to the other voting devices 601 and acquiring the evaluation data of the voting device 601 ( P2P anonymous data sharing function: Step B005).
Thereby, the voting device 600 acquires the evaluation data held by the voting device 601 and the voting devices 600 and 601 can share the evaluation data with each other.

Next, the voting device 600 examines the evaluation data identifier of each newly stored evaluation data, and stores it if it is a new evaluation data identifier (evaluation data management function: step B006).
Here, if the evaluation data identifiers are the same, it is determined that the evaluation data is already stored, and the validity period is confirmed.

  As a result of the confirmation, the newer valid period is set as new evaluation data, the old valid period is discarded, and the new evaluation data is updated and stored (step B007). Here, evaluation data obtained as a result of the update setting is shown in FIG.

Next, the voting apparatus 600 outputs evaluation data to the user based on the user's request for the stored evaluation data (evaluation data totaling function: step B008).
Note that the aggregation method here may be, for example, a setting for calculating the sum of evaluation values for each IdP.

  As a result, the Web browser user refers to the result output and displayed by the evaluation data totaling function (step B008) to determine which IdP is frequently used, that is, trust from the Web server (Web application). The registration destination of the attribute information can be determined based on this.

  Here, each voting device can acquire a large number of evaluation data by executing the same processing as the above-described steps B001 to B007 with many other voting devices. Since the IdP and its evaluation value can be obtained, the evaluation data possessed by each voting device is updated to a content that is more realistic.

  As described above, in the present embodiment, it is possible for the user to easily understand the exchange state of the attribute information of the user between the IdP and the Web application based on the attribute exchange history information, and for each IdP. By performing an evaluation related to the frequency of use and the reliability from the Web service system (Web server), it is possible to realize an IdP evaluation mechanism in which arbitrary operation of evaluation information by a specific individual or business operator is difficult to enter. It becomes possible.

  In addition, the user of the Web browser can accurately grasp in which IdP the attribute information used in the Web service system is registered. For this reason, for example, the attribute registered in the IdP When it is necessary to update information, the user can quickly determine which IdP information (master attribute information) should be updated.

  Furthermore, by setting the evaluation data calculated from the actual attribute exchange status to be shared via the P2P network, the criteria indicating which IdP should store personal information to the user, that is, Judgment criteria for selecting and specifying the IdP can be presented, so that the user can make an appropriate selection of the registration destination of personal information, which allows the browser user to be in the actual usage situation. Based on the corresponding evaluation value of IdP, it is possible to (select) determine a highly reliable IdP as a registration destination of attribute information.

  The present invention evaluates an attribute management device that manages user attribute information registered in advance for execution of a web service based on the usage frequency of the web server, and determines a registration destination of attribute information based on this evaluation. It can be usefully applied to the system.

100, 101 Web browser 200, 201 Attribute exchange history recording device 300, 400, 350, 360 IdP
301, 302, 401 Web server (Web application)
500 Network 600, 601 Registration device

Claims (10)

A web server that provides a web service by executing a preset web application in response to a service request from a browser device, and holds attribute information of the browser device user used when the web application is executed An attribute information exchange system comprising an attribute information providing device,
A message acquisition device for acquiring a message to be sent to the attribute information providing device when the web server acquires the attribute information from the attribute information providing device for executing the web application;
An attribute exchange history storage device that identifies the acquisition destination of the attribute information in the web server based on the content of the message and stores the acquisition destination as attribute exchange history information;
An attribute exchange reliability evaluation device that calculates an evaluation value indicating the reliability as the acquisition destination of the attribute information corresponding to each of the attribute information providing devices based on the use frequency of the stored attribute exchange history information. An attribute information exchange system characterized by that. In the attribute information exchange system according to claim 1,
Prior to acquiring the attribute information from the attribute information providing device for executing the web application, the web server sends the attribute exchange request for requesting the attribute exchange as the message via the attribute exchange history device. An attribute information exchange system characterized by being transmitted to an information providing apparatus. In the attribute information exchange system according to claim 2,
The attribute information providing apparatus includes an attribute exchange response transmission function for transmitting an attribute exchange response to the attribute exchange request to the attribute information providing apparatus via the attribute exchange history apparatus,
The attribute exchange history device includes an attribute information acquisition destination specifying function for specifying an acquisition destination of the attribute information based on the content of the attribute exchange response sent from the attribute information providing device. system. In the attribute information exchange system according to claim 1,
The browser device has a service request transmission function for transmitting the service request to the web server via the attribute exchange history storage device;
The attribute exchange history storage device includes an attribute information request source specifying function for specifying a web server as a request source of the attribute information based on the content of the service request sent from the browser device. Exchange system. In the attribute information exchange system according to claim 2,
The attribute information exchange system, wherein the web server transmits the attribute exchange request to the attribute information providing device via redirection in the browser device. In the attribute information exchange system according to claim 3,
The attribute information providing apparatus, wherein the attribute information providing apparatus transmits the attribute exchange response to the attribute information providing apparatus via redirection in the browser apparatus. In the attribute information exchange system according to claim 1,
The attribute exchange reliability evaluation device shares the calculated evaluation value among other preset attribute exchange reliability evaluation devices, and calculates the evaluation value total by aggregating the shared evaluation values. An attribute information exchange system having an evaluation value sharing function. In the attribute information exchange system according to claim 7,
The attribute exchange reliability evaluation device sets a fixed effective period for each evaluation value when calculating the calculated evaluation value, and generates the generated value between other preset attribute exchange reliability evaluation devices. An attribute information exchange system comprising an in-period evaluation value sharing function for sharing an evaluation value within the valid period. A web server that provides a web service by executing a preset web application in response to a service request from a browser device, and holds attribute information of the browser device user used when the web application is executed An attribute information exchange system comprising an attribute information providing device and a genus exchange history recording device for specifying an acquisition destination of attribute information acquired by the web server, wherein the attribute information providing device is used as an acquisition destination of the attribute information. An attribute information exchange method to be evaluated,
When the web server obtains the attribute information from the attribute information providing device for executing the web application, the attribute exchange history recording device obtains a message sent from the web server to the attribute information providing device. And
The attribute exchange history recording device
Specify the acquisition destination of the attribute information in the web server based on the content of the message, store the acquisition destination as attribute exchange history information,
An attribute information exchanging method characterized in that an evaluation value indicating reliability as an acquisition destination of the attribute information is calculated corresponding to each of the attribute information providing devices based on a use frequency of the stored attribute exchange history information. A web server that provides a web service by executing a preset web application in response to a service request from a browser device, and holds attribute information of the browser device user used when the web application is executed An attribute information exchange system comprising an attribute information providing device and a genus exchange history recording device for specifying an acquisition destination of attribute information acquired by the web server, wherein the attribute information providing device is used as an acquisition destination of the attribute information. An attribute information exchange program for evaluation,
A message acquisition function for acquiring a message sent from the web server to the attribute information providing device when the web server acquires the attribute information from the attribute information providing device for execution of the web application;
An attribute exchange history storage function for performing processing of specifying the acquisition destination of the attribute information in the web server based on the content of the message and storing the acquisition destination as attribute exchange history information;
Computer-execution of an attribute exchange reliability evaluation function for calculating an evaluation value indicating reliability as an acquisition destination of the attribute information corresponding to each attribute information providing device based on the use frequency of the stored attribute exchange history information An attribute information exchange program characterized by

Images