Abstract:
Online and on-premise applications identify trusted authentication providers. The applications are configured with a list of trusted issuers of authentication credentials. When an application receives a request requiring authentication, the application returns a 401 response that includes the trusted issuer list. The requesting application compares the trusted issuer list from the 401 response to its own list of authentication providers. If there is a match between the two lists, then the requesting application creates a self-issued token for the authentication provider. The authentication provider uses the self-issued token to generate an authentication token for the requesting application. The requesting application may also directly create a token for a target partner application, without an authentication provider, if there is a direct trust between the two applications.
Abstract:
Enterprise Identity Management systems control access to information derived from identity-related data stored in various data repositories. An identity-based management system can automatically and dynamically compute derived data when the source data changes. Rule-base tools can be used to compute derived data from arbitrary attribute-based datasets. Dynamic computation of identity-based attributes within information system servers allows data to be aggregated and normalized from multiple data sources deployed across an organization so that updated related information can be persisted and pushed to various servers in the organization.
Abstract:
Online and on-premise applications identify trusted authentication providers. The applications are configured with a list of trusted issuers of authentication credentials. When an application receives a request requiring authentication, the application returns a 401 response that includes the trusted issuer list. The requesting application compares the trusted issuer list from the 401 response to its own list of authentication providers. If there is a match between the two lists, then the requesting application creates a self-issued token for the authentication provider. The authentication provider uses the self-issued token to generate an authentication token for the requesting application. The requesting application may also directly create a token for a target partner application, without an authentication provider, if there is a direct trust between the two applications.