US20010000358A1 - Gateway system and recording medium - Google Patents
Gateway system and recording medium Download PDFInfo
- Publication number
- US20010000358A1 US20010000358A1 US09/729,194 US72919400A US2001000358A1 US 20010000358 A1 US20010000358 A1 US 20010000358A1 US 72919400 A US72919400 A US 72919400A US 2001000358 A1 US2001000358 A1 US 2001000358A1
- Authority
- US
- United States
- Prior art keywords
- user
- information
- request
- returned data
- designation
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
- G06F21/41—User authentication where a single sign-on provides access to a plurality of computers
Definitions
- the present invention relates to a gateway system which relays a request from a user for a service provided by another system and to a recording medium therefor.
- WWW world wide web
- the present invention aims at providing a desired information service with a single user ID and password entered on the side of each user. According to the present invention, this is realized by transmitting a request from each user received by a gateway to another desired information provider server or gateway with the user ID and password being converted and by returning a response to the request to the user through a reverse conversion process when the response is received.
- a gateway 1 receives a request from a user 7 , transmits the received request to another gateway 8 or an information service provider 9 , and transmits returned data to the requesting user 7 .
- the gateway 1 includes a data transmission/reception unit 2 , an authentication unit 3 , a designation conversion unit 4 , an authentication table 5 , and a designation conversion table 6 .
- the data transmission/reception unit 2 receives and transmits data.
- the authentication unit 3 authenticates the request from the user 7 by referring to the authentication table 5 .
- the designation conversion unit 4 converts or inversely converts a designation by referring to the designation conversion table 6 .
- the request from the user 7 is supplied first to the authentication unit 3 .
- the authentication unit 3 checks a user ID and password upon receiving the request from the user 7 . If the result of the check by the authentication unit 3 is “OK”, the designation of a service requested by the designation conversion unit 4 and a password are fetched from the designation conversion table 6 , and the data is converted.
- the data converted by the designation conversion unit 4 is supplied to the data transmission/reception unit 2 .
- the data transmission/reception unit 2 transmits the data supplied from the designation conversion unit 4 to the gateway 8 or the information service provider 9 .
- the data transmission/reception unit 2 supplies the returned data to the designation conversion unit 4 .
- the returned data received by the data transmission/reception unit 2 is inversely converted by the designation conversion unit 4 .
- the data inversely converted by the designation conversion unit 4 is supplied to the data transmission/reception unit 2 .
- the data transmission/reception unit 2 receives the inversely converted data from the designation conversion unit 4 and transmits the inversely converted data to the requesting party of the user 7 .
- the user ID and password of the requesting user 7 are converted if entered in the authentication table 5 , and if not, the user 7 is asked for reentry of the user ID and password or an error is detected.
- the designation conversion unit 4 fetches a representative ID and representative password corresponding to the designation from the designation conversion table 6 and sets the user ID in the representative ID. Further, the designation conversion unit 4 , when transmitting service information after receiving the representative ID and representative password, performs a billing by relating information on the representative ID including the user ID of the user 7 to the service information and collecting the information on the representative ID. Moreover, the designation conversion unit 4 , when the reverse conversion is performed, also converts the designation included in control information, which is set in the returned data and includes the access data of the user 7 to a WWW server.
- the user can receive a desired information service with the single user ID and password entered on the user's side by transmitting the request from the user received by the gateway 1 to another desired information provider server or gateway with the user ID and password being converted and by returning the response to the request to the user through the reverse conversion process when the response is received.
- FIG. 1 is a block diagram of a system of the present invention
- FIG. 2 is a flowchart illustrating an operation of the present invention
- FIG. 3 is a flowchart illustrating the operation of the present invention.
- FIG. 4 shows examples of tables according to the present invention
- FIG. 5 is a diagram illustrating an operation of the present invention
- FIG. 6 is a flowchart illustrating a detailed operation of the present invention.
- FIG. 7 is a flowchart illustrating a detailed operation of the present invention.
- FIG. 8 is a flowchart illustrating a detailed operation of the present invention.
- FIG. 9 is a flowchart of a conversion process of setting information of “Cookie” according to the present invention.
- FIG. 10 is a diagram illustrating an operation according to another embodiment of the present invention.
- FIG. 1 is a block diagram showing a system of the present invention.
- the gateway 1 which is connected to the Internet or local area networks (LANs), receives a request from the user 7 , transmits the received request to the gateway 8 or the information service provider 9 , and transmits returned data to the requesting user 7 .
- the gateway 1 includes the data transmission/reception unit 2 , the authentication unit 3 , the designation conversion unit 4 , the authentication table 5 , and the designation conversion table 6 .
- each of the gateways 1 performs a conversion or reverse conversion process according to a later-described process shown in FIGS. 2 and 3 so that the user 7 can receive a desired service automatically with the single user ID and password by accessing a WWW server connected to any of the gateways 1 having the hierarchical structure.
- the data transmission/reception unit 2 receives and transmits data.
- the authentication unit 3 checks the user ID and password included in the data (request) received from the user 7 by referring to the authentication table 5 , and further checks a designation (authorized information).
- the designation conversion unit 4 converts or inversely converts the designation including the user ID, a designation ID, a designation address (URL: Uniform Resource Locator) and the password by referring to the designation conversion table 6 .
- the gateway 8 has the same structure as the gateway 1 .
- the information service provider 9 is a server which provides a variety of information and has a large-scale database.
- the information service provider 9 has the same inside structure as the gateway 1 and transmits a request for service to another information service provider 10 .
- the information service provider 10 is a server which provides a variety of information.
- FIGS. 2 and 3 are flowcharts illustrating the operation of the present invention.
- a Web page request is made in step S 1 .
- This step transmits the Web page request (/AAA) for a Web page selected from a list, which Web page the user 7 wishes to have.
- step S 2 The data is received in step S 2 .
- the data transmission/reception unit 2 of the gateway 1 receives the Web page request data transmitted in step S 1 .
- step S 3 An authentication check is made in step S 3 .
- the authentication unit 3 checks whether the user ID and password are included in the data received in step S 2 .
- step S 3 If the result of the authentication check in step S 3 is “NG”, that is, the user ID and password are not included in the data, a message requesting entry of the user ID and password is transmitted in step S 4 .
- step S 3 determines whether the result of the authentication check in step S 3 is “OK”, that is, if the user ID and password are included in the data.
- step S 5 it is determined whether the user ID is already entered. In this step, it is determined whether the user ID is already entered into a browser on the side of the user 7 .
- step 5 If the determination result of step 5 is “YES”, the user has already entered the user ID and password into the browser opened on a screen. Therefore, the browser sets the user ID and password in control data output at the time of the Web page request and transmits the user ID and password to the gateway 1 .
- step S 5 determines whether the user ID and password is transmitted. If the determination result of step S 5 is “NO”, the user has not entered the user ID and password into the browser opened on the screen. Therefore, the user enters the user ID and password in a predetermined region on the screen and transmits the user ID and password to the gateway 1 . At this point at least below-described information is transmitted:
- URL ex. a gateway name and a designation ID (/AAA)
- step S 8 the above-described information is received.
- the data transmission/reception unit 2 of the gateway 1 stores a connection ID.
- the transmission and reception of the data (packet) are performed using the connection ID.
- step S 9 the user ID and password are checked. In this step, it is checked, by referring to the later-described authentication table 5 of FIG. 4( a ), whether a user ID and password corresponding to the user ID and password included in the data received in step S 8 are entered in the authentication table 5 .
- step S 9 If the check result of step S 9 is “OK”, the process proceeds to step S 10 .
- step S 9 If the check result of step S 9 is “NG”, an error message is transmitted to ask the user 7 for reentry of the user ID and password, and “ERROR” is displayed when a number of reentries exceeds a predetermined number of times.
- step S 10 it is checked whether a service is accessible. In this step, it is checked, by referring to the authentication table 5 of FIG. 4( a ), whether the requested service, for example, “/AAA”, is entered and authorized in the authorized information, namely, the designation ID of an entry corresponding to the user ID and password of step S 9 .
- the requested service for example, “/AAA”
- step S 10 If the check result of the step S 10 is “OK”, the process proceeds to step S 11 .
- step S 10 If the check result of the step S 10 is “NO”, it is determined that the requested service is not entered and authorized in the authentication table 5 , so that an “NG” message is transmitted to the user 7 and it is displayed on the screen that the requested service is not authorized.
- step S 11 the designation ID is checked.
- the check result of step S 10 is “OK” and the requested service is entered in the authorized information list of the authentication table 5 of FIG. 4( a ), it is checked whether the desired designation ID (authorized information) is entered in the designation conversion table 6 of FIG. 4( b ).
- step S 11 If the check result of step S 11 is “OK”, the process proceeds to step S 12 .
- step S 11 If the check result of step S 11 is “NO”, the designation ID is not entered. Therefore, an “NG” message is transmitted to be displayed on the screen to notify the user 7 that the designation ID is not entered.
- step S 12 a conversion process is performed.
- the check result of step S 11 is “OK” and it is determined that the authorized designation ID is entered in the designation conversion table 6 of FIG. 4( b ). Therefore, after
- Step S 13 is a data transmission process.
- step S 13 data in which the designation URL, representative ID and representative password formed in step S 12 are set is transmitted.
- step S 14 the information service provider 9 having the designation URL receives the data transmitted in step S 13 and stores the connection ID for returning data.
- step S 15 the representative ID and representative password received in step S 14 are checked.
- step S 15 If the check result of step S 15 is “OK”, the process proceeds to step S 16 .
- step S 15 If the check result of step S 15 is “NO”, an “NG” message is transmitted to the data transmitter.
- Step S 16 is a data preparation process.
- step S 16 data for which a request for service has been made is prepared.
- step S 17 billing information is collected.
- necessary billing information such as the representative ID and the contents of the request for service received in step S 14 is prepared to be stored. Since the user ID of the service requesting user 7 and the organization ID of an organization to which the user 7 belongs are embedded into the representative ID, it is possible to perform a billing by the user or the organization.
- step S 18 is a data transmission process.
- the data namely, the data for which the request for service has been made, is transmitted to the gateway 1 based on the connection ID stored in step S 14 .
- step S 19 the gateway 1 receives the data transmitted in step S 18 .
- Step S 20 is a reverse conversion process.
- the reverse conversion process which is reverse to the above-described conversion process performed in step S 12 of FIG. 2, is performed.
- data conversion is performed based on a URL. For example, “www.ggg.co.jp” is inversely converted into “gatewayname/AAA”.
- Step S 21 is a data transmission process. In this step, the data is transmitted to the requesting user 7 based on the connection ID stored in step S 8 .
- step S 22 the user 7 receives the data transmitted in step S 21 .
- Step S 23 is a display process. Then, the process returns to step S 1 of FIG. 2(A) and the above-described steps are repeated.
- the gateway 1 checks the user ID/password/authorized information by referring to the authentication table 5 of FIG. 4( a ) and automatically converts the user ID/password/authorized information, when the check result is “OK”, into the designation of the service provider, the representative ID into which the user ID and the like are embedded, and the representative password by referring to the designation conversion table 6 of FIG. 4( b ).
- the designation of the service provider, the representative ID and the representative password are then transmitted to the designation of the information service provider 9 or 10 .
- the information service provider 9 or 10 prepares and returns the data for the service provided, and collects the billing information such as the representative ID and the name of the service provided.
- the gateway 1 inversely converts the designation when receiving the returned data and transmits the data to the requesting user 7 so that the user 7 can receive the service with the data shown on the screen. This allows the user 7 , who is conscious only of the gateway 1 , to automatically receive the service provided from the information service provider 9 or 10 with the single user ID and password.
- This also allows the information service provider 9 or 10 to perform, by collecting the representative ID and the name of the service, the billing for the provided service by the user ID or the organization ID of the organization to which the user belongs.
- FIG. 4 shows examples of the tables according to the present invention.
- FIG. 4( a ) shows an example of the authentication table. As shown therein,
- the user ID is an ID assigned only to the user 7 of FIG. 1.
- the password is a secret password for each user ID.
- the authorized information is information (designation ID) on an authorized service.
- the option ID is the organization ID assigned only to the organization to which the user 7 belongs.
- steps S 9 , S 10 , and S 11 can be made by entering the above-described information in the authentication table 5 .
- the entry of data in, alteration of data entered in, and deletion of entered data from the authentication table 5 can be made easily by the respective operations of addition, alteration, and deletion.
- FIG. 4( b ) shows an example of the designation conversion table. As shown therein,
- the designation ID corresponds to the authorized information (designation ID) of the authentication table 5 of FIG. 4( a ).
- the designation URL is the URL (address) of a designation, and the representative ID includes a user ID and the organization ID of an organization to which each user belongs.
- the representative password which includes a user ID, is a password assigned to a given group, organization or gateway.
- the conversion of the designation and password and the reverse conversion of the designation can be made automatically with reference to the designation conversion table 6 when the above-described conversion process of step S 12 of FIG. 2 and reverse conversion process of step S 20 of FIG. 3 are performed.
- FIG. 5 illustrates an operation (selection from the list) of the present invention. This describes the details of steps to be taken to make a selection from the list of services provided.
- the list is downloaded from the gateway 1 to the user 7 so as to be displayed on the screen before the above-described Web page request is made in step S 1 of FIG. 2.
- FIG. 5( a ) shows a flowchart.
- the user 7 transmits a list request in step S 21 .
- the list is transmitted. That is, a WWW server receives the list request transmitted in step S 21 and transmits the requested list to the user 7 (the browser of the user 7 ).
- step S 23 the list is displayed. That is, the list transmitted in step S 22 is displayed on the browser opened on the screen on the side of the user 7 .
- the list is displayed, for example, as shown in later-described FIG. 5( b ) or 5 ( c ).
- step S 24 selection is made from the list.
- the user operates a mouse to select one service from the list of FIG. 5( b ) or 5 ( c ) on the screen. Then, the process proceeds to above-described step S 1 of FIG. 2.
- FIG. 5( b ) shows an example 1 of the list, in which the designation ID is used. As shown therein, designation IDs such as “AAA” and “BBB” are used.
- FIG. 5( c ) shows an example 2 of the list, in which the designation ID is not used. As shown therein, designation URLs are provided instead of the designation IDs.
- FIG. 6 is a first flowchart illustrating a detailed operation of the present invention.
- This flowchart illustrates a detailed operation of above-described steps S 9 and S 10 of FIG. 2.
- step S 31 the user ID and password are fetched.
- the authentication unit 3 fetches, for example, “user1/pass1”, which is noted on the right of step S 31 in FIG. 6, as the user ID and password from the data received from the user 7 .
- step S 32 a comparison is made between the fetched user ID and password and user IDs and passwords in the authentication table 5 .
- the user ID and password are compared with, for example, a user ID and password “user1/pass1” entered in the authentication table 5 of FIG. 4( a ).
- step S 33 it is determined whether the fetched user ID and password correspond to the user ID and password entered in the authentication table 5 . If correspondence is found as a result of step S 33 , the process proceeds to step S 34 .
- step S 33 If no correspondence is found as a result of step S 33 , an “NG” message is transmitted to the user 7 and it is displayed on the screen that the user ID and password entered are wrong so as to ask for reentry of the user ID and password. If wrong user IDs and passwords are entered the predetermined number of times, the process is terminated as an error.
- step S 34 the designation ID is fetched.
- the designation ID “AAA”, for example, is fetched from the data.
- step S 35 the fetched designation ID is compared with authorized information, namely, a designation ID corresponding to “user1” in the authentication table.
- the designation ID “AAA” fetched in step S 34 is compared with authorized information, namely, a designation ID “AAA, BBB” entered in the authentication table of FIG. 4( a ), which designation ID corresponds to the user ID, for example, “user1” approved through steps S 31 through S 33 .
- “AAA” exists correspondingly in both of the designation IDs.
- step S 36 it is determined whether “AAA” is included in the authorized information of “user1”. In this case, since “AAA” is included therein, the determination result of step S 36 is “OK”. This means that all of the user ID, password and designation ID are authenticated. On the other hand, if the determination result of step S 36 is “NO”, an “NG” message is transmitted to be displayed on the screen to notify the user 7 of the above result.
- FIG. 7 is a second flowchart illustrating a detailed operation of the present invention.
- This flowchart illustrates a detailed operation of above-described steps S 11 and S 12 of FIG. 2.
- step S 41 a comparison is made between designation IDs in the designation conversion table and “/AAA”.
- the designation ID “AAA” fetched in step S 34 of FIG. 6 is compared with designation IDs entered in the designation conversion table 6 so as to see if there is a designation ID corresponding to the designation ID “AAA” in the designation conversion table 6 .
- step S 42 it is determined whether “/AAA” is included in the designation IDs in the designation conversion table 6 . If it is determined in step S 42 that “/AAA” is included therein, the process proceeds to step S 43 .
- step S 42 If it is determined in step S 42 that “/AAA” is not included therein, the determination result of step S 42 is “NG” and an error is detected.
- step S 43 a designation URL corresponding to “/AAA” is fetched from the designation conversion table. In this step, the designation URL “.www.ggg.co.jp” is fetched from the entries of FIG. 4( b ).
- step S 44 a representative ID format corresponding to “/AAA” is fetched from the designation conversion table.
- the representative ID format “GGG+UserID+OptionID” is fetched from the entries of FIG. 4( b ).
- step S 45 the representative ID is formed.
- the user ID “user1” is embedded into the representative ID format fetched in step S 44 to form the representative ID “GGG. user1”.
- step S 46 a representative password corresponding to “/AAA” is fetched from the designation conversion table.
- the representative password “passA” is fetched from the entries of FIG. 4( b ).
- Step S 47 is a transmission request process.
- the designation conversion table 6 it is possible to automatically form, by referring to the designation conversion table 6 , the designation URL to which the data is transmitted and the representative ID and representative password which replace the user ID and password, respectively.
- the data can be transmitted by replacing (changing) the original designation URL, user ID and password with the automatically formed designation URL, representative ID and representative password.
- FIG. 8 is a third flowchart illustrating a detailed operation of the present invention. This flowchart illustrates a detailed operation of the above-described step S 20 of FIG. 3.
- step S 51 the received data (HTML) is read in.
- step S 52 link information in the HTML is compared with designation URLs in the designation conversion table.
- step S 53 a designation ID corresponding to the link information is found.
- the link information corresponds to, for example, “www.ggg.co.jp” in the designation conversion table 6 of FIG. 4( b )
- the designation ID “AAA” in the head of the entry is found.
- step S 54 the received data (HTML) is converted into a gateway name and a designation ID, for example, “Gatewayname+AAA”.
- the designation ID corresponding to the URL fetched from the received data is found by referring to the designation conversion table 6 , and inversely converted into and replaced with the gateway name and the designation ID so that the data is transmitted to the requesting user 7 based on the connection ID stored in step S 8 .
- the user 7 recognizes that the data is returned from the gateway 1 , to which the request for the data is made.
- “Cookie” is a function of (software for) a server to cause a machine on the side of a client to retain information native to the client. “Cookie” is written in a line marked with ⁇ in the control information of data as shown in later-described FIG. 10( c ). Since “Cookie” includes designation information (address information), the designation conversion unit 4 similarly performs the reverse conversion in the above-described gateway 1 of the present invention.
- FIG. 9 shows a flowchart of a conversion process of the setting information of “Cookie” according to the present invention.
- step S 61 the control information of received data is read in.
- step S 63 the setting information of “Cookie” is compared with the designations in the designation conversion table 6 .
- step S 64 a designation ID corresponding to the domain of the setting information is found.
- domain information shown in (b) is first fetched from the setting information of “Cookie” shown in (a), which information is read in through steps S 61 and S 62 , and then, the domain shown in (c) is fetched from the domain information.
- the designation ID, “FFF” in this case, corresponding to the domain shown in (c) is fetched by referring to the designation conversion table 6 .
- step S 65 the setting information of “Cookie” included in the control information of the received data is converted.
- the underlined domain information in the setting information of “Cookie” before conversion shown in (e) is converted into and replaced with an underlined designation ID in the converted setting information of “Cookie” shown in (f) based on the designation ID “FFF” found in step S 64 .
- This process corresponds to the above-described reverse conversion.
- FIG. 10 is a diagram illustrating another operation of the present invention.
- FIG. 10 shows an example according to the above-described flowchart of FIG. 9.
- FIG. 10( a ) shows an example of the name of the server including the gateway.
- the name is as follows:
- FIG. 10( b ) shows an example of the setting contents of the designation conversion table 6 .
- the setting contents are set as follows:
- FIG. 10( c ) shows an example of the received data.
- FIG. 10( c ) shows an example of the contents of data returned from a WWW server (included in the information service provider 9 ) to the gateway 1 .
- the line marked with ⁇ in the control information (a) in FIG. 10( c ) is the setting information of “Cookie”, which is identical to the setting information thereof shown in FIG. 9( a ).
- a line marked with ⁇ is the information described with reference to FIGS. 1 through 8.
- FIG. 10( d ) shows data after the reverse conversion process.
- the data is obtained after the conversion performed in accordance with above-described steps S 63 through S 65 .
- a line marked with ⁇ is the converted setting information of “Cookie”
- a line marked with ⁇ is the information after the above-described reverse conversion described with reference to FIGS. 1 through 8.
- the request from the user 7 received by the gateway 1 is transmitted to another desired information provider server or gateway with the user ID and password being converted. Further, when the response to the request is received, the response is returned to the user 7 through the reverse conversion process and at the same time, the designation included in the control information including access data of the user to the WWW server is inversely converted. Therefore, the user 7 can receive a desired information service with the single user ID and password entered on the user's side.
- the present invention allows the user 7 to automatically access a plurality of WWW servers having different billing systems through the gateway 1 with the single user ID and password;
- control information including access information of the user 7 to a WWW server for example, the setting information of “Cookie”
- a WWW server for example, the setting information of “Cookie”
- the user 7 can also automatically access a desired WWW server with the single user ID and password to receive a desired service if each of the gateways 1 similarly performs the conversion and reverse conversion.
- WWW server information service provider
Abstract
Description
- 1. The present invention relates to a gateway system which relays a request from a user for a service provided by another system and to a recording medium therefor.
- 2. According to a conventional intranet (network within organization), user IDs and passwords used therein are managed separately from user IDs and passwords for world wide web (WWW) servers (for example, pay WWW servers provided with databases each storing large-scale information) of other networks linked to the intranet, and each of the WWW servers is accessed and a billing is processed by using a proper user ID and password.
- 3. Therefore, it is necessary to manage the user IDs and passwords for the intranet separately from those for other WWW servers, thus being inconvenient for users.
- 4. In order to eliminate this disadvantage, the present invention aims at providing a desired information service with a single user ID and password entered on the side of each user. According to the present invention, this is realized by transmitting a request from each user received by a gateway to another desired information provider server or gateway with the user ID and password being converted and by returning a response to the request to the user through a reverse conversion process when the response is received.
- 5. A description will be given, with reference to FIG. 1, of a system for eliminating the disadvantage.
- 6. According to FIG. 1, a
gateway 1 receives a request from a user 7, transmits the received request to anothergateway 8 or aninformation service provider 9, and transmits returned data to the requesting user 7. Thegateway 1 includes a data transmission/reception unit 2, anauthentication unit 3, adesignation conversion unit 4, an authentication table 5, and a designation conversion table 6. - 7. The data transmission/
reception unit 2 receives and transmits data. Theauthentication unit 3 authenticates the request from the user 7 by referring to the authentication table 5. - 8. The
designation conversion unit 4 converts or inversely converts a designation by referring to the designation conversion table 6. - 9. Next, a description will be given of an operation of the above-described system.
- 10. The request from the user 7 is supplied first to the
authentication unit 3. Theauthentication unit 3 checks a user ID and password upon receiving the request from the user 7. If the result of the check by theauthentication unit 3 is “OK”, the designation of a service requested by thedesignation conversion unit 4 and a password are fetched from the designation conversion table 6, and the data is converted. - 11. The data converted by the
designation conversion unit 4 is supplied to the data transmission/reception unit 2. The data transmission/reception unit 2 transmits the data supplied from thedesignation conversion unit 4 to thegateway 8 or theinformation service provider 9. When data responding to the transmitted data is returned from thegateway 8 or theinformation service provider 9 to the data transmission/reception unit 2, the data transmission/reception unit 2 supplies the returned data to thedesignation conversion unit 4. - 12. The returned data received by the data transmission/
reception unit 2 is inversely converted by thedesignation conversion unit 4. The data inversely converted by thedesignation conversion unit 4 is supplied to the data transmission/reception unit 2. The data transmission/reception unit 2 receives the inversely converted data from thedesignation conversion unit 4 and transmits the inversely converted data to the requesting party of the user 7. - 13. At this point, the user ID and password of the requesting user 7 are converted if entered in the authentication table 5, and if not, the user 7 is asked for reentry of the user ID and password or an error is detected.
- 14. In the conversion of the designation, the
designation conversion unit 4 fetches a representative ID and representative password corresponding to the designation from the designation conversion table 6 and sets the user ID in the representative ID. Further, thedesignation conversion unit 4, when transmitting service information after receiving the representative ID and representative password, performs a billing by relating information on the representative ID including the user ID of the user 7 to the service information and collecting the information on the representative ID. Moreover, thedesignation conversion unit 4, when the reverse conversion is performed, also converts the designation included in control information, which is set in the returned data and includes the access data of the user 7 to a WWW server. - 15. Therefore, the user can receive a desired information service with the single user ID and password entered on the user's side by transmitting the request from the user received by the
gateway 1 to another desired information provider server or gateway with the user ID and password being converted and by returning the response to the request to the user through the reverse conversion process when the response is received. - 16.FIG. 1 is a block diagram of a system of the present invention;
- 17.FIG. 2 is a flowchart illustrating an operation of the present invention;
- 18.FIG. 3 is a flowchart illustrating the operation of the present invention;
- 19.FIG. 4 shows examples of tables according to the present invention;
- 20.FIG. 5 is a diagram illustrating an operation of the present invention;
- 21.FIG. 6 is a flowchart illustrating a detailed operation of the present invention;
- 22.FIG. 7 is a flowchart illustrating a detailed operation of the present invention;
- 23.FIG. 8 is a flowchart illustrating a detailed operation of the present invention;
- 24.FIG. 9 is a flowchart of a conversion process of setting information of “Cookie” according to the present invention; and
- 25.FIG. 10 is a diagram illustrating an operation according to another embodiment of the present invention.
- 26. Next, a detailed description will be given, with reference to FIGS. 1 through 10, of embodiments of the present invention.
- 27.FIG. 1 is a block diagram showing a system of the present invention.
- 28. According to FIG. 1, the
gateway 1, which is connected to the Internet or local area networks (LANs), receives a request from the user 7, transmits the received request to thegateway 8 or theinformation service provider 9, and transmits returned data to the requesting user 7. Thegateway 1 includes the data transmission/reception unit 2, theauthentication unit 3, thedesignation conversion unit 4, the authentication table 5, and the designation conversion table 6. - 29. According to FIG. 1, only the
gateway 1 is connected between the user 7 and aninformation service provider 10. However, a plurality of thegateways 1 may be hierarchically connected therebetween. In such a case, each of thegateways 1 performs a conversion or reverse conversion process according to a later-described process shown in FIGS. 2 and 3 so that the user 7 can receive a desired service automatically with the single user ID and password by accessing a WWW server connected to any of thegateways 1 having the hierarchical structure. - 30. The data transmission/
reception unit 2 receives and transmits data. Theauthentication unit 3 checks the user ID and password included in the data (request) received from the user 7 by referring to the authentication table 5, and further checks a designation (authorized information). - 31. The
designation conversion unit 4 converts or inversely converts the designation including the user ID, a designation ID, a designation address (URL: Uniform Resource Locator) and the password by referring to the designation conversion table 6. - 32. In the authentication table 5, authorized information (designation IDs), organization IDs and so on are entered in advance in correspondence to user IDs and passwords (see FIG. 4(a)). Designation URLs, representative IDs, representative passwords and so on are in advance entered in the designation conversion table 7 in correspondence to the designation IDs.
- 33. The
gateway 8 has the same structure as thegateway 1. Theinformation service provider 9 is a server which provides a variety of information and has a large-scale database. Theinformation service provider 9 has the same inside structure as thegateway 1 and transmits a request for service to anotherinformation service provider 10. - 34. The
information service provider 10 is a server which provides a variety of information. - 35. Next, a description will be given, according to the order of the flowcharts of FIGS. 2 and 3, of an operation of the whole system of FIG. 1.
- 36.FIGS. 2 and 3 are flowcharts illustrating the operation of the present invention. According to FIG. 2, a Web page request is made in step S1. This step transmits the Web page request (/AAA) for a Web page selected from a list, which Web page the user 7 wishes to have.
- 37. The data is received in step S2. In this step, the data transmission/
reception unit 2 of thegateway 1 receives the Web page request data transmitted in step S1. - 38. An authentication check is made in step S3. In this step, the
authentication unit 3 checks whether the user ID and password are included in the data received in step S2. - 39. If the result of the authentication check in step S3 is “NG”, that is, the user ID and password are not included in the data, a message requesting entry of the user ID and password is transmitted in step S4.
- 40. On the other hand, if the result of the authentication check in step S3 is “OK”, that is, if the user ID and password are included in the data, the process proceeds to step S8.
- 41. In step S5, it is determined whether the user ID is already entered. In this step, it is determined whether the user ID is already entered into a browser on the side of the user 7.
- 42. If the determination result of
step 5 is “YES”, the user has already entered the user ID and password into the browser opened on a screen. Therefore, the browser sets the user ID and password in control data output at the time of the Web page request and transmits the user ID and password to thegateway 1. - 43. On the other hand, if the determination result of step S5 is “NO”, the user has not entered the user ID and password into the browser opened on the screen. Therefore, the user enters the user ID and password in a predetermined region on the screen and transmits the user ID and password to the
gateway 1. At this point at least below-described information is transmitted: - 44. User ID/Password: ex. user1/pass1
- 45. URL: ex. a gateway name and a designation ID (/AAA)
- 46. In step S8, the above-described information is received. At this point, the data transmission/
reception unit 2 of thegateway 1 stores a connection ID. Hereafter, the transmission and reception of the data (packet) (for example, data transmission in step S13) are performed using the connection ID. - 47. In step S9, the user ID and password are checked. In this step, it is checked, by referring to the later-described authentication table 5 of FIG. 4(a), whether a user ID and password corresponding to the user ID and password included in the data received in step S8 are entered in the authentication table 5.
- 48. If the check result of step S9 is “OK”, the process proceeds to step S10.
- 49. If the check result of step S9 is “NG”, an error message is transmitted to ask the user 7 for reentry of the user ID and password, and “ERROR” is displayed when a number of reentries exceeds a predetermined number of times.
- 50. In step S10, it is checked whether a service is accessible. In this step, it is checked, by referring to the authentication table 5 of FIG. 4(a), whether the requested service, for example, “/AAA”, is entered and authorized in the authorized information, namely, the designation ID of an entry corresponding to the user ID and password of step S9.
- 51. If the check result of the step S10 is “OK”, the process proceeds to step S11.
- 52. If the check result of the step S10 is “NO”, it is determined that the requested service is not entered and authorized in the authentication table 5, so that an “NG” message is transmitted to the user 7 and it is displayed on the screen that the requested service is not authorized.
- 53. In step S11, the designation ID is checked. In this step, since the check result of step S10 is “OK” and the requested service is entered in the authorized information list of the authentication table 5 of FIG. 4(a), it is checked whether the desired designation ID (authorized information) is entered in the designation conversion table 6 of FIG. 4(b).
- 54. If the check result of step S11 is “OK”, the process proceeds to step S12.
- 55. If the check result of step S11 is “NO”, the designation ID is not entered. Therefore, an “NG” message is transmitted to be displayed on the screen to notify the user 7 that the designation ID is not entered.
- 56. In step S12, a conversion process is performed. In this step, the check result of step S11 is “OK” and it is determined that the authorized designation ID is entered in the designation conversion table 6 of FIG. 4(b). Therefore, after
- 57. Designation URL: ex. www.ggg.co.jp
- 58. Representative ID/Representative password: ex. GGG+UserID+Option/PassA
- 59. are fetched from the designation conversion table 6, the user ID of “user1” is embedded into the above-described information to form:
- 60. Designation URL: ex. www.ggg.co.jp
- 61. Representative ID/Representative password: ex. GGG. User1/PassA
- 62. Step S13 is a data transmission process. In step S13, data in which the designation URL, representative ID and representative password formed in step S12 are set is transmitted.
- 63. In step S14, the
information service provider 9 having the designation URL receives the data transmitted in step S13 and stores the connection ID for returning data. - 64. In step S15, the representative ID and representative password received in step S14 are checked.
- 65. If the check result of step S15 is “OK”, the process proceeds to step S16.
- 66. If the check result of step S15 is “NO”, an “NG” message is transmitted to the data transmitter.
- 67. Step S16 is a data preparation process. In step S16, data for which a request for service has been made is prepared.
- 68. In step S17, billing information is collected. In this step, necessary billing information such as the representative ID and the contents of the request for service received in step S14 is prepared to be stored. Since the user ID of the service requesting user 7 and the organization ID of an organization to which the user 7 belongs are embedded into the representative ID, it is possible to perform a billing by the user or the organization.
- 69. According to FIG. 3, step S18 is a data transmission process. In step S18, the data, namely, the data for which the request for service has been made, is transmitted to the
gateway 1 based on the connection ID stored in step S14. - 70. In step S19, the
gateway 1 receives the data transmitted in step S18. - 71. Step S20 is a reverse conversion process. In step S20, the reverse conversion process, which is reverse to the above-described conversion process performed in step S12 of FIG. 2, is performed. In step S20, data conversion is performed based on a URL. For example, “www.ggg.co.jp” is inversely converted into “gatewayname/AAA”.
- 72. Step S21 is a data transmission process. In this step, the data is transmitted to the requesting user 7 based on the connection ID stored in step S8.
- 73. In step S22, the user 7 receives the data transmitted in step S21.
- 74. Step S23 is a display process. Then, the process returns to step S1 of FIG. 2(A) and the above-described steps are repeated.
- 75. As described above, the user 7 has only to make the request to the
gateway 1 for the data, and thegateway 1 checks the user ID/password/authorized information by referring to the authentication table 5 of FIG. 4(a) and automatically converts the user ID/password/authorized information, when the check result is “OK”, into the designation of the service provider, the representative ID into which the user ID and the like are embedded, and the representative password by referring to the designation conversion table 6 of FIG. 4(b). The designation of the service provider, the representative ID and the representative password are then transmitted to the designation of theinformation service provider - 76. The
information service provider gateway 1 inversely converts the designation when receiving the returned data and transmits the data to the requesting user 7 so that the user 7 can receive the service with the data shown on the screen. This allows the user 7, who is conscious only of thegateway 1, to automatically receive the service provided from theinformation service provider information service provider - 77.FIG. 4 shows examples of the tables according to the present invention.
- 78.FIG. 4(a) shows an example of the authentication table. As shown therein,
- 79. User ID:
- 80. Password:
- 81. Authorized information (designation ID):
- 82. Option ID (organization ID or the like):
- 83. Others:
- 84. are entered and related to one another in the authentication table 5.
- 85. Here, the user ID is an ID assigned only to the user 7 of FIG. 1. The password is a secret password for each user ID. The authorized information (designation ID) is information (designation ID) on an authorized service. The option ID is the organization ID assigned only to the organization to which the user 7 belongs.
- 86. The above-described checks in steps S9, S10, and S11 can be made by entering the above-described information in the authentication table 5. The entry of data in, alteration of data entered in, and deletion of entered data from the authentication table 5 can be made easily by the respective operations of addition, alteration, and deletion.
- 87.FIG. 4(b) shows an example of the designation conversion table. As shown therein,
- 88. Designation ID:
- 89. Designation URL:
- 90. Representative ID: ex. GGG+UserID+ OptionID
- 91. Representative password:
- 92. Others:
- 93. are entered and related to one another in the designation conversion table 6.
- 94. Here, the designation ID corresponds to the authorized information (designation ID) of the authentication table 5 of FIG. 4(a). The designation URL is the URL (address) of a designation, and the representative ID includes a user ID and the organization ID of an organization to which each user belongs. The representative password, which includes a user ID, is a password assigned to a given group, organization or gateway.
- 95. By entering the above-described information in the designation conversion table 6 as described above, the conversion of the designation and password and the reverse conversion of the designation can be made automatically with reference to the designation conversion table 6 when the above-described conversion process of step S12 of FIG. 2 and reverse conversion process of step S20 of FIG. 3 are performed.
- 96. The entry of data in, alteration of data entered in, and deletion of entered data from the designation conversion table 6 can be made easily by the respective operations of addition, alteration, and deletion.
- 97.FIG. 5 illustrates an operation (selection from the list) of the present invention. This describes the details of steps to be taken to make a selection from the list of services provided. The list is downloaded from the
gateway 1 to the user 7 so as to be displayed on the screen before the above-described Web page request is made in step S1 of FIG. 2. - 98.FIG. 5(a) shows a flowchart. According to FIG. 5(a), the user 7 transmits a list request in step S21. In step S22, the list is transmitted. That is, a WWW server receives the list request transmitted in step S21 and transmits the requested list to the user 7 (the browser of the user 7).
- 99. In step S23, the list is displayed. That is, the list transmitted in step S22 is displayed on the browser opened on the screen on the side of the user 7. The list is displayed, for example, as shown in later-described FIG. 5(b) or 5(c).
- 100. In step S24, selection is made from the list. In this step, the user operates a mouse to select one service from the list of FIG. 5(b) or 5(c) on the screen. Then, the process proceeds to above-described step S1 of FIG. 2.
- 101. Thus, the user 7 is allowed to make the list request to the WWW server and select the one service from the list of FIG. 5(b) or 5(c) on the screen. FIG. 5(b) shows an example 1 of the list, in which the designation ID is used. As shown therein, designation IDs such as “AAA” and “BBB” are used.
- 102.FIG. 5(c) shows an example 2 of the list, in which the designation ID is not used. As shown therein, designation URLs are provided instead of the designation IDs.
- 103.FIG. 6 is a first flowchart illustrating a detailed operation of the present invention.
- 104. This flowchart illustrates a detailed operation of above-described steps S9 and S10 of FIG. 2.
- 105. According to FIG. 6, in step S31, the user ID and password are fetched. In this step, the
authentication unit 3 fetches, for example, “user1/pass1”, which is noted on the right of step S31 in FIG. 6, as the user ID and password from the data received from the user 7. - 106. In step S32, a comparison is made between the fetched user ID and password and user IDs and passwords in the authentication table 5. In this step, the user ID and password are compared with, for example, a user ID and password “user1/pass1” entered in the authentication table 5 of FIG. 4(a).
- 107. In step S33, it is determined whether the fetched user ID and password correspond to the user ID and password entered in the authentication table 5. If correspondence is found as a result of step S33, the process proceeds to step S34.
- 108. If no correspondence is found as a result of step S33, an “NG” message is transmitted to the user 7 and it is displayed on the screen that the user ID and password entered are wrong so as to ask for reentry of the user ID and password. If wrong user IDs and passwords are entered the predetermined number of times, the process is terminated as an error.
- 109. In step S34, the designation ID is fetched. In this step, since the check result of the user ID and password is “OK”, the designation ID “AAA”, for example, is fetched from the data.
- 110. In step S35, the fetched designation ID is compared with authorized information, namely, a designation ID corresponding to “user1” in the authentication table. In this step, the designation ID “AAA” fetched in step S34 is compared with authorized information, namely, a designation ID “AAA, BBB” entered in the authentication table of FIG. 4(a), which designation ID corresponds to the user ID, for example, “user1” approved through steps S31 through S33. In this case, “AAA” exists correspondingly in both of the designation IDs.
- 111. In step S36, it is determined whether “AAA” is included in the authorized information of “user1”. In this case, since “AAA” is included therein, the determination result of step S36 is “OK”. This means that all of the user ID, password and designation ID are authenticated. On the other hand, if the determination result of step S36 is “NO”, an “NG” message is transmitted to be displayed on the screen to notify the user 7 of the above result.
- 112. Thus, it is possible to make the checks on the user ID, password and designation ID included in the data received from the user 7 by referring to the above-described authentication table 5 of FIG. 4(a).
- 113.FIG. 7 is a second flowchart illustrating a detailed operation of the present invention.
- 114. This flowchart illustrates a detailed operation of above-described steps S11 and S12 of FIG. 2.
- 115. According to FIG. 7, in step S41, a comparison is made between designation IDs in the designation conversion table and “/AAA”. In this step, for example, the designation ID “AAA” fetched in step S34 of FIG. 6 is compared with designation IDs entered in the designation conversion table 6 so as to see if there is a designation ID corresponding to the designation ID “AAA” in the designation conversion table 6.
- 116. In step S42, it is determined whether “/AAA” is included in the designation IDs in the designation conversion table 6. If it is determined in step S42 that “/AAA” is included therein, the process proceeds to step S43.
- 117. If it is determined in step S42 that “/AAA” is not included therein, the determination result of step S42 is “NG” and an error is detected. In step S43, a designation URL corresponding to “/AAA” is fetched from the designation conversion table. In this step, the designation URL “.www.ggg.co.jp” is fetched from the entries of FIG. 4(b).
- 118. In step S44, a representative ID format corresponding to “/AAA” is fetched from the designation conversion table. In this step, the representative ID format “GGG+UserID+OptionID” is fetched from the entries of FIG. 4(b).
- 119. In step S45, the representative ID is formed. In this step, the user ID “user1” is embedded into the representative ID format fetched in step S44 to form the representative ID “GGG. user1”.
- 120. In step S46, a representative password corresponding to “/AAA” is fetched from the designation conversion table. In this step, the representative password “passA” is fetched from the entries of FIG. 4(b).
- 121. Step S47 is a transmission request process.
- 122. Thus, it is possible to automatically form, by referring to the designation conversion table 6, the designation URL to which the data is transmitted and the representative ID and representative password which replace the user ID and password, respectively. The data can be transmitted by replacing (changing) the original designation URL, user ID and password with the automatically formed designation URL, representative ID and representative password.
- 123.FIG. 8 is a third flowchart illustrating a detailed operation of the present invention. This flowchart illustrates a detailed operation of the above-described step S20 of FIG. 3.
- 124. According to FIG. 8, in step S51, the received data (HTML) is read in.
- 125. In step S52, link information in the HTML is compared with designation URLs in the designation conversion table. The link information (URL) “www.ggg.co.jp” fetched from the received HTML data, for example, is compared with the above-mentioned designation URLs in the designation conversion table 6 of FIG. 4(b).
- 126. In step S53, a designation ID corresponding to the link information is found. In this step, if it is determined, as a result of the comparison made in step S52, that the link information corresponds to, for example, “www.ggg.co.jp” in the designation conversion table 6 of FIG. 4(b), the designation ID “AAA” in the head of the entry is found.
- 127. In step S54, the received data (HTML) is converted into a gateway name and a designation ID, for example, “Gatewayname+AAA”.
- 128. Thus, the designation ID corresponding to the URL fetched from the received data (HTML) is found by referring to the designation conversion table 6, and inversely converted into and replaced with the gateway name and the designation ID so that the data is transmitted to the requesting user 7 based on the connection ID stored in step S8.
- 129. By this, the user 7 recognizes that the data is returned from the
gateway 1, to which the request for the data is made. - 130. Next, a detailed description will be given, with reference to FIGS. 9 and 10, of an embodiment in which the present invention is applied to so-called “Cookie”. Here, “Cookie” is a function of (software for) a server to cause a machine on the side of a client to retain information native to the client. “Cookie” is written in a line marked with ★ in the control information of data as shown in later-described FIG. 10(c). Since “Cookie” includes designation information (address information), the
designation conversion unit 4 similarly performs the reverse conversion in the above-describedgateway 1 of the present invention. - 131. The detailed description will be given in the following.
- 132.FIG. 9 shows a flowchart of a conversion process of the setting information of “Cookie” according to the present invention.
- 133. According to FIG. 9, in step S61, the control information of received data is read in. In step S62, it is determined whether the setting information of “Cookie” is included in the control information. In this step, it is determined whether the setting information of “Cookie” such as Set-Cookie; sample=12345;domain=.zzzzzzz.co.jp;path=/;, as shown in (a) noted on the right of the flowchart in FIG. 9, is written. If the determination result of step S62 is “YES”, the process proceeds to step S63. If the determination result of step S62 is “NO”, the process is terminated.
- 134. In step S63, the setting information of “Cookie” is compared with the designations in the designation conversion table 6.
- 135. In step S64, a designation ID corresponding to the domain of the setting information is found. In steps S63 and S64, for example, as noted on the right of steps S63 and S64 in FIG. 9, domain information shown in (b) is first fetched from the setting information of “Cookie” shown in (a), which information is read in through steps S61 and S62, and then, the domain shown in (c) is fetched from the domain information.
- 136. Next, as shown in (d), the designation ID, “FFF” in this case, corresponding to the domain shown in (c) is fetched by referring to the designation conversion table 6.
- 137. In step S65, the setting information of “Cookie” included in the control information of the received data is converted. In this step, the underlined domain information in the setting information of “Cookie” before conversion shown in (e) is converted into and replaced with an underlined designation ID in the converted setting information of “Cookie” shown in (f) based on the designation ID “FFF” found in step S64. (This process corresponds to the above-described reverse conversion.)
- 138. Thus, the setting information of “Cookie” before conversion shown in (e), which information is included in the received data, is automatically converted into the converted setting information of “Cookie” shown in (f). This conversion can be performed together with the reverse conversion of the designation marked with ⋆ in FIG. 10, which reverse conversion is previously described with reference to FIG. 1 or 8.
- 139.FIG. 10 is a diagram illustrating another operation of the present invention. FIG. 10 shows an example according to the above-described flowchart of FIG. 9. FIG. 10(a) shows an example of the name of the server including the gateway. Here, the name is as follows:
- 140. Server name: www.gateway-Server.co.jp
- 141.FIG. 10(b) shows an example of the setting contents of the designation conversion table 6. Here, the setting contents are set as follows:
- 142. Designation ID: FFF (of FIG. 4(b))
- 143. Actual designation: www.ZZZZZZZ.co.jp
- 144.FIG. 10(c) shows an example of the received data. FIG. 10(c) shows an example of the contents of data returned from a WWW server (included in the information service provider 9) to the
gateway 1. The line marked with ★ in the control information (a) in FIG. 10(c) is the setting information of “Cookie”, which is identical to the setting information thereof shown in FIG. 9(a). A line marked with ⋆ is the information described with reference to FIGS. 1 through 8. - 145.FIG. 10(d) shows data after the reverse conversion process. The data is obtained after the conversion performed in accordance with above-described steps S63 through S65. In the data, a line marked with ★ is the converted setting information of “Cookie”, and a line marked with ⋆ is the information after the above-described reverse conversion described with reference to FIGS. 1 through 8.
- 146. As described above, according to the present invention, the request from the user 7 received by the
gateway 1 is transmitted to another desired information provider server or gateway with the user ID and password being converted. Further, when the response to the request is received, the response is returned to the user 7 through the reverse conversion process and at the same time, the designation included in the control information including access data of the user to the WWW server is inversely converted. Therefore, the user 7 can receive a desired information service with the single user ID and password entered on the user's side. - 147. Thus:
- 148. (1) although, conventionally, user IDs and passwords for different WWW servers or WWW servers having different billing systems have to be managed separately, the present invention allows the user 7 to automatically access a plurality of WWW servers having different billing systems through the
gateway 1 with the single user ID and password; - 149. (2) control information including access information of the user 7 to a WWW server (for example, the setting information of “Cookie”), which control information is included in received data, can be utilized effectively with the
gateway 1 according to the present invention automatically inversely converting a designation included in the received data; and - 150. (3) with a plurality of the
gateways 1 according to the present invention being provided between the user 7 and an information service provider (WWW server) in a hierarchical structure, the user 7 can also automatically access a desired WWW server with the single user ID and password to receive a desired service if each of thegateways 1 similarly performs the conversion and reverse conversion.
Claims (14)
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP10-165660 | 1998-06-12 | ||
JP16566098A JP3493141B2 (en) | 1998-06-12 | 1998-06-12 | Gateway system and recording medium |
JPPCT/JP99/02472 | 1999-05-13 |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
JPPCT/JP99/02472 Continuation | 1998-06-12 | 1999-05-13 |
Publications (2)
Publication Number | Publication Date |
---|---|
US20010000358A1 true US20010000358A1 (en) | 2001-04-19 |
US6938171B1 US6938171B1 (en) | 2005-08-30 |
Family
ID=15816601
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/729,194 Expired - Fee Related US6938171B1 (en) | 1998-06-12 | 2000-12-05 | Gateway system and recording medium |
Country Status (2)
Country | Link |
---|---|
US (1) | US6938171B1 (en) |
JP (1) | JP3493141B2 (en) |
Cited By (38)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2002021788A3 (en) * | 2000-09-04 | 2002-06-06 | Ibm | Method and system for testing a contents server |
US20030023756A1 (en) * | 2001-07-03 | 2003-01-30 | Fujitsu Limited | Contents conversion method and server |
EP1293912A2 (en) * | 2001-09-14 | 2003-03-19 | Sony Computer Entertainment Inc. | Method for issuing identification information |
EP1327950A2 (en) * | 2002-01-09 | 2003-07-16 | Toshiba Tec Kabushiki Kaisha | Membership information integrated management system and service |
US20030163569A1 (en) * | 2002-02-26 | 2003-08-28 | Citrix Systems, Inc | Secure traversal of network components |
EP1396992A2 (en) * | 2002-08-15 | 2004-03-10 | Ricoh Company, Ltd. | Image forming apparatus that can operate without wasteful use of resources thereof and unnecessary authentication |
US6731731B1 (en) * | 1999-07-30 | 2004-05-04 | Comsquare Co., Ltd. | Authentication method, authentication system and recording medium |
US6947404B1 (en) * | 2000-11-06 | 2005-09-20 | Nokia Corporation | Automatic WAP login |
WO2006034476A1 (en) * | 2004-09-24 | 2006-03-30 | Siemens Medical Solutions Usa, Inc. | A system for activating multiple applications for concurrent operation |
US20060075474A1 (en) * | 2004-10-05 | 2006-04-06 | Sachiko Takeuchi | Service providing system, information processing apparatus, service providing server and service providing method |
US20060095501A1 (en) * | 2003-08-06 | 2006-05-04 | Naoyuki Mochida | Relay server, relay server service management method, service providing system and program |
US20060168211A1 (en) * | 2002-08-29 | 2006-07-27 | Hiroyuki Koike | Information processing system, information processing device and method, program storage medium, and program |
US20060277406A1 (en) * | 2005-05-20 | 2006-12-07 | Yoko Hashimoto | System and method for encrypted communication |
FR2895856A1 (en) * | 2005-12-30 | 2007-07-06 | Trusted Logic Sa | Authentication data inputting, processing and transferring system for e.g. domestic environment, has peripheral with secure operating mode to collect data, access security component and safely transfer data via communication unit |
US20070289004A1 (en) * | 2002-08-28 | 2007-12-13 | International Business Machines Corporation | Authenticated and communicating verifiable authorization between disparate network domains |
GB2440425A (en) * | 2006-07-25 | 2008-01-30 | Intuit Inc | Single sign-on system which translates authentication tokens |
US20080101597A1 (en) * | 2006-11-01 | 2008-05-01 | Microsoft Corporation | Health integration platform protocol |
US20080103830A1 (en) * | 2006-11-01 | 2008-05-01 | Microsoft Corporation | Extensible and localizable health-related dictionary |
US20080103794A1 (en) * | 2006-11-01 | 2008-05-01 | Microsoft Corporation | Virtual scenario generator |
US20080104012A1 (en) * | 2006-11-01 | 2008-05-01 | Microsoft Corporation | Associating branding information with data |
US20080104617A1 (en) * | 2006-11-01 | 2008-05-01 | Microsoft Corporation | Extensible user interface |
US20080103818A1 (en) * | 2006-11-01 | 2008-05-01 | Microsoft Corporation | Health-related data audit |
US7373140B1 (en) * | 1999-10-20 | 2008-05-13 | Nec Corporation | Wireless communication system and method of changing language to be displayed in wireless client |
US20080244078A1 (en) * | 2007-03-26 | 2008-10-02 | Pieter Viljoen | Web services intermediary |
CN100447799C (en) * | 2004-10-05 | 2008-12-31 | 株式会社理光 | Service providing system, information processing apparatus, service providing server and service providing method |
US20090083240A1 (en) * | 2007-09-24 | 2009-03-26 | Microsoft Corporation | Authorization agnostic based mechanism |
US20090313069A1 (en) * | 2005-01-06 | 2009-12-17 | Early Warning Services, Llc | Identity Verification Systems and Methods |
US20110035594A1 (en) * | 2009-07-27 | 2011-02-10 | Barbara Ann Fox | Apparatus and method for providing elective message tagging |
US20110154457A1 (en) * | 2009-12-21 | 2011-06-23 | Fujitsu Limited | Authenticating method, conversion device, and relay device |
EP2590380A1 (en) * | 2011-11-05 | 2013-05-08 | Kyocera Document Solutions Inc. | Image forming apparatus, image forming system, and method for realizing pseudo single sign-on |
US8533746B2 (en) | 2006-11-01 | 2013-09-10 | Microsoft Corporation | Health integration platform API |
US20140122715A1 (en) * | 2012-10-25 | 2014-05-01 | Simon Michael Rowe | User Logging of Web Traffic on Non-Browser Based Devices |
EP2875430A1 (en) * | 2012-08-16 | 2015-05-27 | Huawei Technologies Co., Ltd. | Control pool based enterprise policy enabler for controlled cloud access |
EP2693357A4 (en) * | 2011-03-31 | 2015-07-08 | Fujitsu Ltd | Management device, management program, and management method |
US20150269368A1 (en) * | 2014-03-18 | 2015-09-24 | Fuji Xerox Co., Ltd. | Relay apparatus, system, relay method, and computer readable medium |
FR3022375A1 (en) * | 2014-06-17 | 2015-12-18 | Evidian | METHOD AND DEVICE FOR SECURING A PASSWORD PROTECTED SYSTEM |
US11196733B2 (en) * | 2018-02-08 | 2021-12-07 | Dell Products L.P. | System and method for group of groups single sign-on demarcation based on first user login |
US11431698B2 (en) * | 2018-10-31 | 2022-08-30 | NBA Properties, Inc. | Partner integration network |
Families Citing this family (51)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6757903B1 (en) * | 1999-04-05 | 2004-06-29 | Gateway, Inc. | Object driven software architecture method and apparatus |
FI108592B (en) * | 2000-03-14 | 2002-02-15 | Sonera Oyj | Billing on a mobile application protocol using a wireless application protocol |
JP2001265736A (en) * | 2000-03-23 | 2001-09-28 | Canon Inc | User authentication method |
JP2001283062A (en) * | 2000-04-03 | 2001-10-12 | Cybozu Inc | Electric transaction system using groupware |
JP2002007346A (en) * | 2000-06-21 | 2002-01-11 | Hewlett Packard Japan Ltd | Communication system |
JP2002032340A (en) | 2000-07-14 | 2002-01-31 | Nec Corp | System and method for single sign-on web site and recording medium |
JP2002032273A (en) * | 2000-07-18 | 2002-01-31 | Melco Inc | Connection service providing system, connection service providing method, connection service requesting device, connection service requesting method, medium in which connection service request processing program is recorded, connection service proxy requesting device, connection service proxy requesting method and medium in which connection service proxy request processing program is recorded |
US7080147B2 (en) | 2000-09-04 | 2006-07-18 | International Business Machines Corporation | Computer network system, computer system, method for communication between computer systems, method for measuring computer system performance, and storage medium |
US7181490B1 (en) * | 2001-02-14 | 2007-02-20 | Cisco Technology, Inc. | Method and apparatus for mapping network events to names of network devices |
JP3828517B2 (en) * | 2001-02-19 | 2006-10-04 | 株式会社東芝 | Electronic commerce management server and electronic commerce management method |
US20020116649A1 (en) * | 2001-02-21 | 2002-08-22 | Kenji Goshima | Authentication system and authentication method |
US20020147985A1 (en) * | 2001-04-05 | 2002-10-10 | Koji Miyajima | Video distribution system and video distribution method |
US7383347B2 (en) * | 2001-07-18 | 2008-06-03 | International Business Machines Corporation | Method and apparatus for providing extensible scalable transcoding of multimedia content |
KR100397438B1 (en) * | 2001-09-24 | 2003-09-13 | 삼성에스디에스 주식회사 | Unix-based gateway for exterior data transmission and method using the same |
JP2003108748A (en) | 2001-09-28 | 2003-04-11 | Sony Corp | Method for generalizing identification information, portal information providing device and ic card |
US7126954B2 (en) * | 2001-11-13 | 2006-10-24 | General Instrument Corporation | Virtual gateway |
KR20030056568A (en) * | 2001-12-28 | 2003-07-04 | 한국전자통신연구원 | Method of authentication for protecting agent and messages |
JP2003233729A (en) * | 2002-02-08 | 2003-08-22 | Seiko Epson Corp | Electronic commercial transaction system |
JP4179535B2 (en) * | 2002-09-03 | 2008-11-12 | インターナショナル・ビジネス・マシーンズ・コーポレーション | Network system, reverse proxy, computer apparatus, data processing method and program |
US7092942B2 (en) * | 2002-05-31 | 2006-08-15 | Bea Systems, Inc. | Managing secure resources in web resources that are accessed by multiple portals |
US7596692B2 (en) * | 2002-06-05 | 2009-09-29 | Microsoft Corporation | Cryptographic audit |
US7187681B1 (en) * | 2002-06-11 | 2007-03-06 | Cisco Technology, Inc. | Method and apparatus for traffic quality and billing authorization by request token insertion |
US7403925B2 (en) * | 2003-03-17 | 2008-07-22 | Intel Corporation | Entitlement security and control |
US7467414B2 (en) * | 2003-03-17 | 2008-12-16 | Intel Corporation | Entitlement security and control for information system entitlement |
US7451305B1 (en) * | 2003-04-10 | 2008-11-11 | Cisco Technology, Inc. | Method and apparatus for securely exchanging cryptographic identities through a mutually trusted intermediary |
WO2005001660A2 (en) * | 2003-06-25 | 2005-01-06 | Anonymizer, Inc. | Secure network privacy system using proxy server |
US20140143852A1 (en) | 2008-08-21 | 2014-05-22 | Ntrepid Corporation | Secure network privacy system |
JP2011120242A (en) * | 2003-08-06 | 2011-06-16 | Panasonic Corp | Relay server, service management method therefor, service providing system, and program |
WO2005065035A2 (en) * | 2004-01-08 | 2005-07-21 | Wisair Ltd. | Distributed and centralized media access control device and method |
US7346773B2 (en) | 2004-01-12 | 2008-03-18 | Cisco Technology, Inc. | Enabling stateless server-based pre-shared secrets |
JP4517709B2 (en) * | 2004-04-23 | 2010-08-04 | 富士ゼロックス株式会社 | Image processing apparatus, image processing program, image processing method, control apparatus, and system |
JP4613512B2 (en) * | 2004-04-23 | 2011-01-19 | 富士ゼロックス株式会社 | Image processing apparatus, image processing apparatus management program, image processing apparatus management method, and information processing apparatus |
JP2006072749A (en) * | 2004-09-02 | 2006-03-16 | Ricoh Co Ltd | Information unit, printing unit, service relay unit and service provision system |
US7350227B2 (en) * | 2005-04-26 | 2008-03-25 | Cisco Technology, Inc. | Cryptographic peer discovery, authentication, and authorization for on-path signaling |
US8775602B2 (en) * | 2006-06-01 | 2014-07-08 | Avaya Inc. | Alarm-driven access control in an enterprise network |
US7639629B2 (en) * | 2006-07-28 | 2009-12-29 | Microsoft Corporation | Security model for application and trading partner integration |
US8218435B2 (en) * | 2006-09-26 | 2012-07-10 | Avaya Inc. | Resource identifier based access control in an enterprise network |
JP5125424B2 (en) * | 2007-11-01 | 2013-01-23 | 富士通株式会社 | COMMUNICATION SYSTEM, RELAY METHOD, RELAY DEVICE, AND RELAY PROGRAM |
US8122482B2 (en) * | 2008-01-24 | 2012-02-21 | Cisco Technology, Inc. | Cryptographic peer discovery, authentication, and authorization for on-path signaling |
US20130061302A1 (en) * | 2011-02-28 | 2013-03-07 | Gregory Alan Colla | Method and Apparatus for the Protection of Computer System Account Credentials |
JP5618883B2 (en) * | 2011-03-28 | 2014-11-05 | 西日本電信電話株式会社 | Authentication system, authentication linkage device, authentication method |
EP2521329B1 (en) | 2011-05-04 | 2013-07-10 | Alcatel Lucent | A server, a system, a method, a computer program and a computer program product for accessing a server in a computer network |
JP5589034B2 (en) * | 2012-07-24 | 2014-09-10 | 日本電信電話株式会社 | Information distribution system, authentication linkage method, apparatus, and program thereof |
AU2012393609B2 (en) * | 2012-11-02 | 2017-04-13 | Silverlake Mobility Ecosystem Sdn Bhd | Method of processing requests for digital services |
JP2014175736A (en) * | 2013-03-06 | 2014-09-22 | Panasonic Corp | Relay device and relay method |
JP5920260B2 (en) * | 2013-03-19 | 2016-05-18 | 富士ゼロックス株式会社 | COMMUNICATION SYSTEM, RELAY DEVICE, AND PROGRAM |
US9009461B2 (en) * | 2013-08-14 | 2015-04-14 | Iboss, Inc. | Selectively performing man in the middle decryption |
KR101483901B1 (en) * | 2014-01-21 | 2015-01-16 | (주)이스트소프트 | Intranet security system and method |
US20170220819A1 (en) * | 2014-08-12 | 2017-08-03 | Hewlett Packard Enterprise Development Lp | Information exchange gateway |
JP6508067B2 (en) * | 2016-01-14 | 2019-05-08 | 株式会社デンソー | Vehicle data communication system |
US9680801B1 (en) | 2016-05-03 | 2017-06-13 | Iboss, Inc. | Selectively altering references within encrypted pages using man in the middle |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5678041A (en) * | 1995-06-06 | 1997-10-14 | At&T | System and method for restricting user access rights on the internet based on rating information stored in a relational database |
US5835718A (en) * | 1996-04-10 | 1998-11-10 | At&T Corp | URL rewriting pseudo proxy server |
US5918228A (en) * | 1997-01-28 | 1999-06-29 | International Business Machines Corporation | Method and apparatus for enabling a web server to impersonate a user of a distributed file system to obtain secure access to supported web documents |
US6058426A (en) * | 1997-07-14 | 2000-05-02 | International Business Machines Corporation | System and method for automatically managing computing resources in a distributed computing environment |
US6163536A (en) * | 1997-06-11 | 2000-12-19 | International Business Machines Corporation | Communication system including a client controlled gateway for concurrent voice/data messaging with a data server |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2746123B2 (en) | 1994-03-31 | 1998-04-28 | 日本電気株式会社 | Gateway system |
JPH0844643A (en) | 1994-07-27 | 1996-02-16 | Fujitsu Ltd | Gateway device |
CA2176775C (en) | 1995-06-06 | 1999-08-03 | Brenda Sue Baker | System and method for database access administration |
JP3526688B2 (en) | 1996-03-29 | 2004-05-17 | 富士通株式会社 | Metered system and method for connectionless communication |
-
1998
- 1998-06-12 JP JP16566098A patent/JP3493141B2/en not_active Expired - Fee Related
-
2000
- 2000-12-05 US US09/729,194 patent/US6938171B1/en not_active Expired - Fee Related
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5678041A (en) * | 1995-06-06 | 1997-10-14 | At&T | System and method for restricting user access rights on the internet based on rating information stored in a relational database |
US5835718A (en) * | 1996-04-10 | 1998-11-10 | At&T Corp | URL rewriting pseudo proxy server |
US5918228A (en) * | 1997-01-28 | 1999-06-29 | International Business Machines Corporation | Method and apparatus for enabling a web server to impersonate a user of a distributed file system to obtain secure access to supported web documents |
US6163536A (en) * | 1997-06-11 | 2000-12-19 | International Business Machines Corporation | Communication system including a client controlled gateway for concurrent voice/data messaging with a data server |
US6058426A (en) * | 1997-07-14 | 2000-05-02 | International Business Machines Corporation | System and method for automatically managing computing resources in a distributed computing environment |
Cited By (73)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6731731B1 (en) * | 1999-07-30 | 2004-05-04 | Comsquare Co., Ltd. | Authentication method, authentication system and recording medium |
US7373140B1 (en) * | 1999-10-20 | 2008-05-13 | Nec Corporation | Wireless communication system and method of changing language to be displayed in wireless client |
WO2002021788A3 (en) * | 2000-09-04 | 2002-06-06 | Ibm | Method and system for testing a contents server |
US6947404B1 (en) * | 2000-11-06 | 2005-09-20 | Nokia Corporation | Automatic WAP login |
US7305453B2 (en) | 2001-07-03 | 2007-12-04 | Fujitsu Limited | Contents conversion method and server |
US20030023756A1 (en) * | 2001-07-03 | 2003-01-30 | Fujitsu Limited | Contents conversion method and server |
US20030074560A1 (en) * | 2001-09-14 | 2003-04-17 | Muneki Shimada | Method for issuing identification information |
US7313702B2 (en) | 2001-09-14 | 2007-12-25 | Sony Computer Entertainment Inc. | Method for issuing identification information |
EP1293912A3 (en) * | 2001-09-14 | 2006-04-12 | Sony Computer Entertainment Inc. | Method for issuing identification information |
EP1293912A2 (en) * | 2001-09-14 | 2003-03-19 | Sony Computer Entertainment Inc. | Method for issuing identification information |
EP1327950A3 (en) * | 2002-01-09 | 2004-04-21 | Toshiba Tec Kabushiki Kaisha | Membership information integrated management system and service |
US20030154145A1 (en) * | 2002-01-09 | 2003-08-14 | Toshiba Tec Kabushiki Kaisha | Membership information integrated management system, and membership information integrated management service |
EP1327950A2 (en) * | 2002-01-09 | 2003-07-16 | Toshiba Tec Kabushiki Kaisha | Membership information integrated management system and service |
US7661129B2 (en) | 2002-02-26 | 2010-02-09 | Citrix Systems, Inc. | Secure traversal of network components |
EP1483680A2 (en) * | 2002-02-26 | 2004-12-08 | Citrix Systems, Inc. | Secure traversal of network components |
EP1483680A4 (en) * | 2002-02-26 | 2008-12-17 | Citrix Systems Inc | Secure traversal of network components |
WO2003073216A2 (en) | 2002-02-26 | 2003-09-04 | Citrix Systems, Inc. | Secure traversal of network components |
US20030163569A1 (en) * | 2002-02-26 | 2003-08-28 | Citrix Systems, Inc | Secure traversal of network components |
EP1396992A3 (en) * | 2002-08-15 | 2007-04-25 | Ricoh Company, Ltd. | Image forming apparatus that can operate without wasteful use of resources thereof and unnecessary authentication |
EP1396992A2 (en) * | 2002-08-15 | 2004-03-10 | Ricoh Company, Ltd. | Image forming apparatus that can operate without wasteful use of resources thereof and unnecessary authentication |
US20040080771A1 (en) * | 2002-08-15 | 2004-04-29 | Sachiko Mihira | Image forming apparatus that can operate without wasteful use of resources thereof and unnecessary authentication |
US8499339B2 (en) * | 2002-08-28 | 2013-07-30 | International Business Machines Corporation | Authenticating and communicating verifiable authorization between disparate network domains |
US20070289004A1 (en) * | 2002-08-28 | 2007-12-13 | International Business Machines Corporation | Authenticated and communicating verifiable authorization between disparate network domains |
US20060168211A1 (en) * | 2002-08-29 | 2006-07-27 | Hiroyuki Koike | Information processing system, information processing device and method, program storage medium, and program |
US20060095501A1 (en) * | 2003-08-06 | 2006-05-04 | Naoyuki Mochida | Relay server, relay server service management method, service providing system and program |
WO2006034476A1 (en) * | 2004-09-24 | 2006-03-30 | Siemens Medical Solutions Usa, Inc. | A system for activating multiple applications for concurrent operation |
US20060075224A1 (en) * | 2004-09-24 | 2006-04-06 | David Tao | System for activating multiple applications for concurrent operation |
US8171526B2 (en) * | 2004-10-05 | 2012-05-01 | Ricoh Company, Ltd. | Service providing system, information processing apparatus, service providing server and service providing method |
CN100447799C (en) * | 2004-10-05 | 2008-12-31 | 株式会社理光 | Service providing system, information processing apparatus, service providing server and service providing method |
EP1646179A1 (en) * | 2004-10-05 | 2006-04-12 | Ricoh Company, Ltd. | Service providing system, information processing apparatus, service providing server and method of authentication of service requests |
US20060075474A1 (en) * | 2004-10-05 | 2006-04-06 | Sachiko Takeuchi | Service providing system, information processing apparatus, service providing server and service providing method |
US8172132B2 (en) * | 2005-01-06 | 2012-05-08 | Early Warning Services, Llc | Identity verification systems and methods |
US20090313069A1 (en) * | 2005-01-06 | 2009-12-17 | Early Warning Services, Llc | Identity Verification Systems and Methods |
US7984290B2 (en) * | 2005-05-20 | 2011-07-19 | Hitachi, Ltd. | System and method for encrypted communication |
US20060277406A1 (en) * | 2005-05-20 | 2006-12-07 | Yoko Hashimoto | System and method for encrypted communication |
WO2007077348A1 (en) * | 2005-12-30 | 2007-07-12 | Trusted Logic | Secure system for inputting and processing authentication data |
FR2895856A1 (en) * | 2005-12-30 | 2007-07-06 | Trusted Logic Sa | Authentication data inputting, processing and transferring system for e.g. domestic environment, has peripheral with secure operating mode to collect data, access security component and safely transfer data via communication unit |
US8799639B2 (en) | 2006-07-25 | 2014-08-05 | Intuit Inc. | Method and apparatus for converting authentication-tokens to facilitate interactions between applications |
AU2007203101B8 (en) * | 2006-07-25 | 2013-02-07 | Intuit, Inc. | Method and apparatus for converting authentication-tokens to facilitate interactions between applications |
AU2007203101B2 (en) * | 2006-07-25 | 2012-10-11 | Intuit, Inc. | Method and apparatus for converting authentication-tokens to facilitate interactions between applications |
DE102007033615B4 (en) | 2006-07-25 | 2023-01-19 | Intuit, Inc. | Method and apparatus for converting authentication tokens to enable interactions between applications |
US20080046715A1 (en) * | 2006-07-25 | 2008-02-21 | Balazs Alex G | Method and apparatus for converting authentication-tokens to facilitate interactions between applications |
GB2440425A (en) * | 2006-07-25 | 2008-01-30 | Intuit Inc | Single sign-on system which translates authentication tokens |
GB2440425B (en) * | 2006-07-25 | 2012-01-11 | Intuit Inc | Method and apparatus for converting authentication-tokens |
US20080103818A1 (en) * | 2006-11-01 | 2008-05-01 | Microsoft Corporation | Health-related data audit |
US20080103794A1 (en) * | 2006-11-01 | 2008-05-01 | Microsoft Corporation | Virtual scenario generator |
US20080103830A1 (en) * | 2006-11-01 | 2008-05-01 | Microsoft Corporation | Extensible and localizable health-related dictionary |
US8533746B2 (en) | 2006-11-01 | 2013-09-10 | Microsoft Corporation | Health integration platform API |
US20080101597A1 (en) * | 2006-11-01 | 2008-05-01 | Microsoft Corporation | Health integration platform protocol |
US20080104617A1 (en) * | 2006-11-01 | 2008-05-01 | Microsoft Corporation | Extensible user interface |
US8316227B2 (en) | 2006-11-01 | 2012-11-20 | Microsoft Corporation | Health integration platform protocol |
US20080104012A1 (en) * | 2006-11-01 | 2008-05-01 | Microsoft Corporation | Associating branding information with data |
US8417537B2 (en) | 2006-11-01 | 2013-04-09 | Microsoft Corporation | Extensible and localizable health-related dictionary |
US20080244078A1 (en) * | 2007-03-26 | 2008-10-02 | Pieter Viljoen | Web services intermediary |
US20090083240A1 (en) * | 2007-09-24 | 2009-03-26 | Microsoft Corporation | Authorization agnostic based mechanism |
US20110035594A1 (en) * | 2009-07-27 | 2011-02-10 | Barbara Ann Fox | Apparatus and method for providing elective message tagging |
US20110154457A1 (en) * | 2009-12-21 | 2011-06-23 | Fujitsu Limited | Authenticating method, conversion device, and relay device |
US8655946B2 (en) | 2009-12-21 | 2014-02-18 | Fujitsu Limited | Authenticating method, conversion device, and relay device |
EP2693357A4 (en) * | 2011-03-31 | 2015-07-08 | Fujitsu Ltd | Management device, management program, and management method |
US8819799B2 (en) | 2011-11-05 | 2014-08-26 | Kyocera Document Solutions Inc. | Image forming apparatus, image forming system, and method for realizing pseudo single sign-on |
EP2590380A1 (en) * | 2011-11-05 | 2013-05-08 | Kyocera Document Solutions Inc. | Image forming apparatus, image forming system, and method for realizing pseudo single sign-on |
EP2875430B1 (en) * | 2012-08-16 | 2021-12-29 | Huawei Technologies Co., Ltd. | Control pool based enterprise policy enabler for controlled cloud access |
EP2875430A1 (en) * | 2012-08-16 | 2015-05-27 | Huawei Technologies Co., Ltd. | Control pool based enterprise policy enabler for controlled cloud access |
US20140122715A1 (en) * | 2012-10-25 | 2014-05-01 | Simon Michael Rowe | User Logging of Web Traffic on Non-Browser Based Devices |
US9313080B2 (en) * | 2012-10-25 | 2016-04-12 | Google Inc. | User logging of web traffic on non-browser based devices |
US9876871B2 (en) | 2012-10-25 | 2018-01-23 | Google Llc | User logging of web traffic on non-browser based devices |
US20150269368A1 (en) * | 2014-03-18 | 2015-09-24 | Fuji Xerox Co., Ltd. | Relay apparatus, system, relay method, and computer readable medium |
US9614830B2 (en) * | 2014-03-18 | 2017-04-04 | Fuji Xerox Co., Ltd. | Relay apparatus, system, relay method, and computer readable medium |
FR3022375A1 (en) * | 2014-06-17 | 2015-12-18 | Evidian | METHOD AND DEVICE FOR SECURING A PASSWORD PROTECTED SYSTEM |
US11196733B2 (en) * | 2018-02-08 | 2021-12-07 | Dell Products L.P. | System and method for group of groups single sign-on demarcation based on first user login |
US11431698B2 (en) * | 2018-10-31 | 2022-08-30 | NBA Properties, Inc. | Partner integration network |
US20230006990A1 (en) * | 2018-10-31 | 2023-01-05 | NBA Properties, Inc. | Partner integration network |
US11706204B2 (en) * | 2018-10-31 | 2023-07-18 | NBA Properties, Inc. | Partner integration network |
Also Published As
Publication number | Publication date |
---|---|
JP3493141B2 (en) | 2004-02-03 |
JP2000003334A (en) | 2000-01-07 |
US6938171B1 (en) | 2005-08-30 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6938171B1 (en) | Gateway system and recording medium | |
US5918009A (en) | Technique for sharing information on world wide web | |
EP0998091B1 (en) | System and method for web server user authentication | |
US6173407B1 (en) | Method of authenticating and charging a client using a web infoshop service system | |
RU2273107C2 (en) | Method, system and computer device for providing communication services between resources in communication networks and internet to perform transactions | |
US9900305B2 (en) | Internet server access control and monitoring systems | |
RU2308755C2 (en) | System and method for providing access to protected services with one-time inputting of password | |
US8606900B1 (en) | Method and system for counting web access requests | |
US6601092B2 (en) | Information processing apparatus, information processing method, and transmitting medium | |
EP1361723B1 (en) | Maintaining authentication states for resources accessed in a stateless environment | |
US5708780A (en) | Internet server access control and monitoring systems | |
EP0830774B1 (en) | Internet server access control and monitoring systems | |
US7552172B2 (en) | Multi-windowed online application environment | |
US6823452B1 (en) | Providing end-to-end user authentication for host access using digital certificates | |
US6237040B1 (en) | Hypertext transmission method and server apparatus for sending and receiving files other than HTML files | |
US5870562A (en) | Universal domain routing and publication control system | |
US20110138446A1 (en) | System and method for providing user authentication and identity management | |
MXJL02000042A (en) | System and methods of accessing network resources. | |
JP2005536787A (en) | Method and system for managing cookies according to privacy policy | |
US20050210135A1 (en) | System for ubiquitous network presence and access without cookies | |
JP2002334056A (en) | System and method for executing log-in in behalf of user | |
CN101345758A (en) | Report normalization processing method, apparatus and system | |
JP2005529392A (en) | Hierarchical distributed identity management | |
CN109710861B (en) | System and method for generating URL | |
US20020156708A1 (en) | Personalized internet server |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: FUJITSU LIMITED, JAPAN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ISOMICHI, KOUSEI;GOMYO, HISAYUKI;MAKINO, YASUSHI;AND OTHERS;REEL/FRAME:011342/0071 Effective date: 20001114 |
|
CC | Certificate of correction | ||
FPAY | Fee payment |
Year of fee payment: 4 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
REMI | Maintenance fee reminder mailed | ||
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.) |
|
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20170830 |