Local encryption for single sign-on
US-10911431-B2 · Feb 2, 2021 · US
US12177202B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12177202-B2 |
| Application number | US-202218071228-A |
| Country | US |
| Kind code | B2 |
| Filing date | Nov 29, 2022 |
| Priority date | Sep 7, 2021 |
| Publication date | Dec 24, 2024 |
| Grant date | Dec 24, 2024 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A method of providing login information may include sending, from a service web page executed on a browser, a login request to an authentication web page executed on the browser, executing, by the authentication web page, a single sign on (SSO) agent in an electronic device, sending, by the authentication web page, a request for authentication information of a user to the SSO agent, generating and transmitting, by the SSO agent, a random number to the authentication web page, generating and transmitting an encrypted eigenvalue on an authentication web server based on the random number to the SSO agent, calling, by the SSO agent, an authentication application programming interface (API) server, and transmitting the eigenvalue, validating the eigenvalue on the authentication API server, and receiving, by the SSO agent, a result of the validating from the authentication API server, and transmitting the authentication information to the authentication web server.
Opening claim text (preview).
What is claimed is: 1. A method of providing login information, the method comprising: sending, from a service web page executed on a browser, a login request to an authentication web page executed on the browser; executing, by the authentication web page, a single sign on (SSO) agent in an electronic device; sending, by the authentication web page, a request for authentication information of a user to the SSO agent; generating, by the SSO agent, a random number and transmitting the random number to the authentication web page; generating an encrypted eigenvalue on an authentication web server based on the random number and transmitting the encrypted eigenvalue to the SSO agent; calling, by the SSO agent, an authentication application programming interface (API) server, and transmitting the encrypted eigenvalue; validating the encrypted eigenvalue on the authentication API server; and receiving, by the SSO agent, a result of the validating from the authentication API server, and transmitting the authentication information to the authentication web server. 2. The method of claim 1 , wherein the executing of the SSO agent comprises: receiving, by the SSO agent, a random port from the authentication web page; and executing a local host web server to communicate with the authentication web server and the authentication API server in the SSO agent based on the random port. 3. The method of claim 1 , wherein the transmitting of the random number to the authentication web page comprises: verifying whether the browser is a set browser; verifying the authentication web page from which the request for the authentication information is sent; and transmitting the random number to the authentication web page. 4. The method of claim 1 , wherein the transmitting of the encrypted eigenvalue to the SSO agent comprises: generating, by the authentication web server, the encrypted eigenvalue by encrypting the random number and a timestamp using a private key. 5. The method of claim 4 , wherein the validating of the encrypted eigenvalue on the authentication API server comprises: decrypting, by the authentication API server, the encrypted eigenvalue using a public key corresponding to the private key, wherein the public key is stored in the authentication API server. 6. The method of claim 5 , wherein the validating of the encrypted eigenvalue on the authentication API server further comprises: verifying whether the decrypted eigenvalue includes the random number; and verifying whether the timestamp is within a set time. 7. The method of claim 1 , wherein the transmitting of the authentication information to the authentication web server comprises: transmitting the authentication information to the authentication web server, and terminating the SSO agent. 8. A method of providing login information, the method comprising: sending, from a service web page executed on a browser, a login request to an authentication web page executed on the browser; executing, by the authentication web page, a single sign on (SSO) agent in an electronic device; sending, by the authentication web page, a request for authentication information of a user to the SSO agent; generating, by the SSO agent, a random number, and transmitting the random number to the authentication web page; generating an encrypted eigenvalue by encrypting the random number and a timestamp on an authentication web server using a private key, and transmitting the encrypted eigenvalue to the SSO agent; calling, by the SSO agent, an authentication application programming interface (API) server using a user authentication token stored in the electronic device to transmit the encrypted eigenvalue; validating the user authentication token on the authentication API server, and decrypting the encrypted eigenvalue using a public key corresponding to the private key to validate the encrypted eigenvalue; and receiving, by the SSO agent, a result of the validating from the authentication API server, and transmitting the authentication information to the authentication web server. 9. The method of claim 8 , further comprising: exchanging one or more messages in the electronic device, wherein the executing of the SSO agent, the sending of the request for the authentication information, and the transmitting of the random number to the authentication web page are each based at least in part on the one or more messages exchanged in the electronic device. 10. The method of claim 8 , wherein the transmitting of the random number to the authentication web page comprises: verifying whether the browser is a set browser; verifying the authentication web page from which the authentication information is sent; and transmitting the random number to the authentication web page. 11. An electronic device comprising: at least one processor; and a memory configured to store instructions executed by the at least one processor, a browser, and a single sign on (SSO) agent wherein the browser is configured to access a service web server and an authentication web server to execute a service web page and an authentication web page, the SSO agent is configured to log in to the electronic device and/or the service web server, and the at least one processor is configured to, in response to the instructions being executed by the at least one processor: send, from the service web page executed on the browser, a login request to the authentication web page executed on the browser, cause the authentication web page to execute the SSO agent, and to send a request for authentication information of a user to the SSO agent, cause the SSO agent to generate a random number and transmit the random number to the authentication web page, call an authentication application programming interface (API) server to transmit an encrypted eigenvalue received from an authentication web server, and to receive a validation result of the encrypted eigenvalue from the authentication API server, and transmit the authentication information to the authentication web server. 12. The electronic device of claim 11 , wherein the at least one processor is further configured to: cause the SSO agent to, in response to the instructions being executed by the at least one processor, receive a random port from the authentication web page, and execute a local host web server to communicate with the authentication web server and the authentication API server in the SSO agent based on the random port. 13. The electronic device of claim 11 , wherein the at least one processor is further configured to: cause the SSO agent to, in response to the instructions being executed by the at least one processor, verify whether the browser is a set browser, verify the authentication web page from which the request for the authentication information is sent, and transmit the random number to the authentication web page. 14. The electronic device of claim 11 , wherein the authentication web server obtains the encrypted eigenvalue by encrypting the random number and a timestamp using a private key. 15. The electronic device of claim 14 , wherein the authentication API server is configured to decrypt the encrypted eigenvalue using a public key corresponding to the private key, wherein the public key is stored in the authentication API server to validate the encrypted eigenvalue. 16. The electronic device of claim 11 , wherein the at least one processor is further configured to: transmit the authentication information to the authentication web server, and terminate the SSO agent.
involving random numbers or seeds · CPC title
using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates · CPC title
involving digital signatures · CPC title
using challenge-response · CPC title
wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption (cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.