Systems and Methods for Providing Automated Access to Resources of Computer Systems
US-2024430261-A1 · Dec 26, 2024 · US
US9306928B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9306928-B2 |
| Application number | US-201414271299-A |
| Country | US |
| Kind code | B2 |
| Filing date | May 6, 2014 |
| Priority date | Dec 8, 2010 |
| Publication date | Apr 5, 2016 |
| Grant date | Apr 5, 2016 |
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.
There is presented a system and method for associating a domain transcendent identification (ID) of a user and a domain specific ID of the user, the system comprising an ID association server accessible by a plurality of secure domains over a network. The system also includes an ID associator application that when executed by ID association server is configured to receive a domain specific ID that associates the user to the secure domain, enter the domain specific ID in a domain transcendent ID record created for the user, generate a unique data associated with the domain transcendent ID record and identify a network location for submission of the unique data, send the unique data and the network location to the user, and associate the domain transcendent ID and the domain specific ID.
Opening claim text (preview).
What is claimed is: 1. A method comprising: sending, by a secure domain to a server, a provider information and a domain specific ID of a user associated with the secure domain, wherein the provider information identifies a commercial entity corresponding to the secure domain; and receiving, by the secure domain from the server and in response to the sending of the domain specific ID, a network location and a unique data generated by the server and associated with a domain transcendent ID, the network location identifying an authorization gateway for authenticating the unique data by a trusted third-party identity provider, and the unique data being for use by the authorization gateway to identify the domain transcendent ID of the user for associating the domain transcendent ID of the user with the domain specific ID of the user, wherein the domain transcendent ID of the user is associated with at least one or more other domain specific IDs of the user; wherein the sending and the receiving are part of a user login process onto the secure domain. 2. The method of claim 1 , wherein the domain transcendent ID is associated with other domain transcendent IDs of the user provided by other trusted third-party identify providers. 3. The method of claim 1 , wherein the domain transcendent ID of the user is used for authentication across one or more other secure domains. 4. The method of claim 1 , wherein the network location is accessible by the user for a limited time period after the unique data is sent to the user via the secure domain. 5. A secure domain comprising: a hardware processor configured to: send to a server, a provider information and a domain specific ID of a user associated with the secure domain, wherein the provider information identifies a commercial entity corresponding to the secure domain; and receive, from the server and in response to sending the domain specific ID to the server, a network location and a unique data generated by the server and associated with a domain transcendent ID, the network location identifying an authorization gateway for authenticating the unique data by a trusted third-party identity provider, and the unique data being for use by the authorization gateway to identify the domain transcendent ID of the user for associating the domain transcendent ID of the user with the domain specific ID of the user, wherein the domain transcendent ID of the user is associated with at least one or more other domain specific IDs of the user; wherein the sending and the receiving are part of a user login process onto the secure domain. 6. The secure domain of claim 5 , wherein the domain transcendent ID is associated with other domain transcendent IDs of the user provider by other trusted third-party identify providers. 7. The secure domain of claim 5 , wherein the domain transcendent ID of the user is used for authentication across one or more other secure domains. 8. The secure domain of claim 5 , wherein the network location is accessible by the user for a limited time period after the unique data is sent to the user via the secure domain. 9. A method comprising: receiving, by a server from a secure domain, a provider information and a domain specific ID of a user associated with the secure domain, wherein the provider information identifies a commercial entity corresponding to the secure domain; generating, by the server, a unique data associated with a domain transcendent ID; and sending, by the server to the secure domain and in response to the receiving of the domain specific ID, a network location and the unique data, the network location identifying an authorization gateway for authenticating the unique data by a trusted third-party identity provider, and the unique data being for use by the authorization gateway to identify the domain transcendent ID of the user for associating the domain transcendent ID of the user with the domain specific ID of the user, wherein the domain transcendent ID of the user is associated with at least one or more other domain specific IDs of the user; wherein the sending and the receiving are part of a user login process onto the secure domain. 10. The method of claim 9 , wherein the domain transcendent ID is associated with other domain transcendent IDs of the user provided by other trusted third-party identify providers. 11. The method of claim 9 , wherein the domain transcendent ID of the user is used for authentication across one or more other secure domains. 12. The method of claim 9 , wherein the network location is accessible by the user for a limited time period after the unique data is sent to the user via the secure domain.
wherein the security policies are location-dependent, e.g. entities privileges depend on current location or allowing specific operations only from locally connected terminals · CPC title
for controlling access to devices or network resources · CPC title
for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32) · CPC title
where a single sign-on provides access to a plurality of computers · CPC title
Filtering by address, protocol, port number or service, e.g. IP-address or URL · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.