Secure Identity Provider Configuration Catalog
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In federated computing environments, there is a lack of secure methods to configure and manage trusted identity providers (IdPs) for service providers (SPs), leading to potential security risks from rogue administrators and uncontrolled use of IdP certificates.
Innovation Solution
A secure database is implemented to store configurations of trusted IdPs, with access controls ensuring only authorized administrators can manage the information, including artifacts for cryptographic operations and website specifications, allowing SPs to securely validate user identity assertions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If IdP configuration information is stored in a publicly accessible directory with wide access permissions, then ease of access and operation is improved, but security and protection against unauthorized modification deteriorates
Solution Approach 1:
The patent segments the system into two distinct components: a public directory for storing IdP configuration information and a secure database for storing service provider configuration information. This segmentation allows different access permissions for different types of data, resolving the contradiction by separating read-accessible configuration data from write-protected service provider configurations.
Solution Approach 2:
The patent introduces a secure database as an intermediary layer between the public directory and the service provider application. This intermediary protects the service provider configuration from unauthorized modification while still allowing the application to access necessary IdP information through controlled interfaces.
2Reliability
If access controls are implemented to restrict configuration management to authorized administrators only, then security is improved, but ease of operation and administrative flexibility deteriorates
Solution Approach 1:
The patent applies local quality by implementing different access control levels for different operations and data types. The secure database allows read access to authorized administrators and service provider applications, while write access is restricted to highly privileged administrators. This granular access control resolves the contradiction by providing appropriate security without overly restricting legitimate administrative operations.
3Ease of operation
If a rogue administrator can access configuration, then ease of operation is maintained, but harmful factors and security risks increase
Solution Approach 1:
The patent implements preliminary anti-action by preemptively protecting the service provider configuration database from unauthorized modification attempts. The secure database structure and access controls are designed to prevent rogue administrators from tampering with configurations before they can cause harm, while still allowing legitimate administrators to perform necessary operations.
Data Source
AI summary
A secure database includes a catalog of information about one or more identity providers (IdPs) that are trusted by a service provider (SP) to authenticate users on the SP's behalf. The catalog securely stores one or more IdP configurations. An entry in the database stores information associated with the trusted IdP including artifacts to identify the IdP, artifacts used by the IdP for cryptographic operations, and a specification of one or more website(s) serviced by the trusted identity provider. Upon receipt by the SP of identity information representing a user that has authenticated to an IdP, information in the catalog of information is used to determine whether the IdP is trusted to authenticate the user on the service provider's behalf. The determination verifies that the SP uses the IdP and that a binding between an IdP identifier and at least one IdP cryptographic artifact is valid.