Identity management system

US9749309B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9749309-B2
Application numberUS-200813124045-A
CountryUS
Kind codeB2
Filing dateSep 12, 2008
Priority dateSep 12, 2008
Publication dateAug 29, 2017
Grant dateAug 29, 2017

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A system comprising an IMS network ( 104 ), an adapter module ( 106 ), an identity provider ( 108 ) and an application ( 110 ) is described. The adapter module ( 106 ) is within an IMS trust domain. The application ( 110 ) is within the trust domain of the identity provider. A user of the system can access the application ( 110 ) via the IMS network ( 104 ), regardless of whether the application is within the IMS trust domain, by making use of the adapter module ( 106 ) to obtain the user's user credentials for the application from the identity provider.

First claim

Opening claim text (preview).

The invention claimed is: 1. A method of enabling a user to access an application via a first trust domain within a closed network, the method comprising the steps of: accessing an account of the user at an identity provider via an adapter module, wherein the adapter module is within the first trust domain and the identity provider is within a second trust domain, wherein the second trust domain is located outside the closed network; obtaining user credentials of the user for the application from the identity provider, wherein a server on which the application operates is within the second trust domain; and using the user credentials for the application to provide the user with access to the application, wherein when the user credentials at the identity provider are different from a user identity of the user in the first trust domain, the adapter module stores at the adapter module a mapping between the user identity and the user credentials, and wherein the user identity in the first trust domain is fixed and used by services running in the first trust domain within the closed network. 2. The method as claimed in claim 1 , wherein either: the adapter module is within both the first trust domain and the second trust domain; or the identity provider is within both the first trust domain and the second trust domain. 3. The method as claimed in claim 1 , wherein: the adapter module is within the first trust domain and outside the second trust domain; and the identity provider is with the second trust domain and outside the first trust domain. 4. The method as claimed in claim 1 , wherein the first trust domain is an IMS network. 5. The method as claimed in claim 1 , wherein the adapter module is configured to obtain data required to access the account of the user at the identity provider. 6. The method as claimed in claim 5 , wherein the step of obtaining the data required to access the account of the user at the identity provider via the adapter module further comprises obtaining a location of the identity provider. 7. The method as claimed in claim 5 , wherein the step of the obtaining the data required to access the account of the user at the identity provider via the adapter module further comprises obtaining user credentials required to access the account of the user at the identity provider. 8. The method as claimed in claim 1 , wherein the adapter module performs protocol and/or format translation between the first trust domain on the one hand, and the identity provider and/or the application on the other hand. 9. An adapter module configured to enable a user to access an application via a first trust domain within a closed network, wherein the adapter module is within the first trust domain and a server on which the application operates is within a second trust domain, wherein the second trust domain is located outside the closed network, and wherein the adapter module is configured to: access an account of the user at an identity provider at which the user has an account, wherein the identity provider is within the second trust domain; obtain said user credentials of the user for the application from the identity provider; and enable the user to access the application, wherein when the user credentials at the identity provider are different from a user identity of the user in the first trust domain, the adapter module stores at the adapter module a mapping between the user identity and the user credentials, and wherein the user identity in the first trust domain is fixed and used by services running in the first trust domain within the closed network. 10. The adapter module as claimed in claim 9 , wherein the adapter module is within the second trust domain. 11. The adapter module as claimed in claim 9 , wherein the identity provider is within the first trust domain. 12. The adapter module as claimed in claim 9 , wherein the adapter module is configured to obtain data required to access the account of the user at the identity provider. 13. The adapter module as claimed in claim 12 , wherein the adapter module is configured to obtain the data required to access the account of the user at the identity provider from a database. 14. The adapter module as claimed in claim 12 , wherein the data required to access the account of the user at the identity provider includes user credentials for the account. 15. The adapter module as claimed in claim 9 , wherein the adapter module is configured to perform protocol and/or format translation between the first trust domain on the one hand and the identity provider and/or the application on the other hand. 16. A system comprising a closed network and an adapter module, wherein: the closed network is within a first trust domain and outside a second trust domain; the adapter module is within the first trust domain; a user of the system has an account with the closed network; the user has an account with an application, wherein a server on which the application operates is within the second trust domain; the user has an account with an identity provider, which identity provider is within the second trust domain; and the adapter module is configured to access the account of the user at the identity provider and to obtain said user credentials of the user for the application from the identity provider, wherein when the user credentials at the identity provider are different from a user identity of the user in the first trust domain, the adapter module stores at the adapter module a mapping between the user identity and the user credentials, and wherein the user identity in the first trust domain is fixed and used by services running in the first trust domain within the closed network. 17. A system comprising an adapter module and an identity provider, wherein: the adapter module is in a first trust domain within a closed network; the identity provider is located in a second trust domain, wherein the second trust domain is located outside the closed network; a user of the system has an account with the identity provider; the user has an account with an application, wherein a server on which the application operates is within the second trust domain; and the adapter module is configured to access the account of the user at the identity provider and to obtain said user credentials of the user for the application from the identity provider, wherein when the user credentials at the identity provider are different from a user identity of the user in the first trust domain, the adapter module stores at the adapter module a mapping between the user identity and the user credentials, and wherein the user identity in the first trust domain is fixed and used by services running in the first trust domain within the closed network. 18. An apparatus, comprising: at least one hardware processor; and at least one memory including a computer program product, wherein the at least one memory and the computer program product are configured to, with the at least one processor, cause the apparatus at least to: access an application via a first trust domain within a closed network, wherein the computer program product is within the first trust domain and a server on which the application operates is within a second trust domain, wherein the second trust domain is located outside the closed network; access an account of the user at an identity provider at which the user has an account, wherein the identity provider is within the second trust domain; obtain user credentials of the user for the application from

Assignees

Inventors

Classifications

  • IP multimedia subsystem [IMS] · CPC title

  • providing single-sign-on or federations · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9749309B2 cover?
A system comprising an IMS network ( 104 ), an adapter module ( 106 ), an identity provider ( 108 ) and an application ( 110 ) is described. The adapter module ( 106 ) is within an IMS trust domain. The application ( 110 ) is within the trust domain of the identity provider. A user of the system can access the application ( 110 ) via the IMS network ( 104 ), regardless of whether the applicatio…
Who is the assignee on this patent?
Horn Günther, Moeller Wolf-Dietrich, Rajasekaran Hariharan, and 1 more
What technology area does this patent fall under?
Primary CPC classification H04L63/0815. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Aug 29 2017 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).