Systems and methods for securely and transparently proxying saas applications through a cloud-hosted or on-premise network gateway for enhanced security and visibility
US-2018295134-A1 · Oct 11, 2018 · US
US2019116153A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2019116153-A1 |
| Application number | US-201715786124-A |
| Country | US |
| Kind code | A1 |
| Filing date | Oct 17, 2017 |
| Priority date | Oct 17, 2017 |
| Publication date | Apr 18, 2019 |
| Grant date | — |
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.
An example embodiment may include a computational instance and a computing device within a remote network management platform. The computing device may be configured to: receive, from a client device of the managed network, a request to redirect, to a second URL, future requests addressed to a first URL; provide, to the client device, instructions to generate a certificate that binds an identity of the entity that operates the managed network to the first URL; receive, from the client device, the certificate; store the certificate and a corresponding cryptographic key; and generate a mapping between the first URL and the second URL. The computational instance may be configured to, in response to receiving a content request referencing the destination, generate a content response containing content from the destination, where any hyperlinks to the second URL in the content are replaced with hyperlinks to the first URL.
Opening claim text (preview).
What is claimed is: 1 . A system comprising: a computational instance of a remote network management platform, wherein the computational instance is assigned to a managed network; a computing device operating a configuration interface within the remote network management platform, wherein the computing device is configured to: receive, by way of the configuration interface and from a client device associated with the managed network, a request to redirect, to a second uniform resource locator (URL), future requests addressed to a first URL, wherein the first URL is textually related to an entity that operates the managed network, and wherein the second URL addresses a destination within the computational instance, provide, by way of the configuration interface and to the client device, instructions to generate a certificate that binds an identity of the entity that operates the managed network to the first URL, receive, by way of the configuration interface and from the client device, the certificate, store the certificate and a corresponding cryptographic key on the remote network management platform, and generate a mapping between the first URL and the second URL; and wherein the computational instance is configured to: receive, from a second client device, a content request referencing the destination, transmit, to the second client device, the certificate, generate a content response containing content from the destination, wherein any hyperlinks to the second URL in the content are replaced with hyperlinks to the first URL in accordance with the mapping, and transmit, to the second client device, the content response. 2 . The system of claim 1 , wherein the content request includes an indication that the content request was initially addressed to the first URL, and wherein any hyperlinks to the second URL in the content are replaced with hyperlinks to the first URL based on the content request including the indication. 3 . The system of claim 2 , wherein the content request is a hypertext transfer protocol (HTTP) request, and wherein the indication that the content request was initially addressed to the first URL comprises the first URL being represented in an HTTP host header of the HTTP request. 4 . The system of claim 1 , wherein the destination is a virtual address assigned to a load balancer, and wherein the load balancer is configured to distribute content requests addressed to the virtual address amongst a plurality of server devices, each with access to the content. 5 . The system of claim 1 , wherein the computational instance is further configured to: receive a second content request referencing the destination; determine that the second content request contains an indication that the second content request was initially addressed to the second URL and was received from a search engine web crawler; and generate a second content response containing metadata configured to (i) cause the search engine web crawler to omit associating the content with the second URL at a search engine index, and (ii) redirect the search engine web crawler to access the content by way of the first URL. 6 . The system of claim 1 , wherein the computing device is further configured to: provide instructions to modify a Domain Name System (DNS) record associated with the first URL to cause the DNS to, in response to future DNS requests to look up the first URL, return the second URL. 7 . The system of claim 1 , wherein the computing device is further configured to: provide instructions to modify a Domain Name System (DNS) record associated with the first URL to cause the DNS to, in response to future DNS requests to look up the first URL, return an internet protocol (IP) address corresponding to the destination. 8 . The system of claim 1 , wherein generating the mapping between the first URL and the second URL comprises associating the first URL with a file system path that is included in the second URL, and wherein the file system path is at the destination. 9 . The system of claim 1 , wherein the first URL addresses a subdomain within the managed network, wherein the destination is a web portal hosted by the computational instance, and wherein the subdomain is textually related to the content. 10 . The system of claim 1 , wherein generating the response comprises: parsing the content for hyperlinks; determining that the content contains a hyperlink corresponding to the second URL; and replacing the hyperlink corresponding to the second URL with a hyperlink corresponding to the first URL. 11 . The system of claim 1 , wherein the computing device is further configured to: receive, by way of the configuration interface and from the client device, a second request to redirect, to a fourth URL, future requests addressed to a third URL, wherein the third URL is textually related to the entity that operates the managed network, wherein the fourth URL addresses a second destination within the computational instance, and generate a second mapping between the third URL and the fourth URL; and wherein the computational instance is further configured to: receive a second content request referencing the second destination, and generate a second content response containing second content from the second destination, wherein any hyperlinks to the fourth URL in the second content are replaced with hyperlinks to the third URL in accordance with the second mapping. 12 . The system of claim 1 , wherein the computing device is further configured to: provide instructions to configure an identity provider (IdP) to authenticate, using single sign-on (SSO) authentication, client devices associated with the managed network to access, by way of content requests initially addressed to the first URL, the destination, and wherein the computational instance is further configured to: in response to receiving the content request, determine that the second client device has not been authenticated to access the content, determine that the content request was initially addressed to the first URL, based on determining that the second client device has not been authenticated and that the content request was initially addressed to the first URL, provide instructions to the second client device to (i) redirect the second client device to the IdP for SSO authentication and, (ii) after authentication by the IdP, cause the second client device to transmit a second content request including the first URL, receive, from the second client device, the second content request and an authentication token issued by the IdP and indicating successful authentication of the second client device, and in response to receiving the second content request and the authentication token, generate the content response. 13 . The system of claim 1 , wherein reception, by the second client device, of the response causes the second client device to display, within an address bar of an application by way of which the content request referencing the destination was generated, the first URL. 14 . The system of claim 1 , wherein the certificate that binds the identity of the entity of the managed network to the first URL is a secure socket layer (SSL) or transport layer security (TLS) certificate issued by a certificate authority (CA). 15 . A method comprising: receiving, by way of a configuration interface of a computing device and from a client device associated with a managed network, a request to redirect, to a second uniform resource locator (URL), future requests addressed to a first URL, wherein the computing d
Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage · CPC title
using information identifiers, e.g. uniform resource locators [URL] · CPC title
for controlling access to devices or network resources · CPC title
using certificate validation, registration, distribution or revocation, e.g. certificate revocation list [CRL] · CPC title
based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.