Abstract:
Policy controls for Web service resource objects in a hierarchical resource space are loosely coupled so that policy changes are applied and enforced across the objects. This technique ensures that different policies are not applied unintentionally to the same resource (for example, one at the Web services entry level, and the other at the resource level). By synchronizing the object in the manner described, neither the entity that deploys the applicat ion nor the security administrator need to be aware of the differences between the various types of requests that occur within a Web services environment. In a representative embodiment, resource objects are linked within a hierarchical resource space to provide synchronized policy control, where the policy is an audit policy, a quality-of-service (QoS) policy, a service level agreement (SLA) policy, a governance policy, a compliance policy, a patch management/vulnerability management policy, a user management policy, or a rights management policy.
Abstract:
A NETWORK SYSTEM SERVER THAT PROVIDES PASSWORD SYNCHRONIZATION BETWEEN A MAIN DATA STORE (102) AND A PLURALITY OF SECONDARY DATA STORES (108) IS DISCLOSED. THE NETWORK SERVER FURTHER INCLUDES A SECURITY SERVER (104), WHICH IS COUPLED TO THE MAIN DATA STORE, A PLURALITY OF CLIENTS (114), COUPLED TO THE SECURITY SERVER FOR ACCESSING THE MAIN DATA STORE WHEREIN EACH CLIENT MAINTAINS A UNIQUE, MODIFIABLE PASSWORD, AND A PASSWORD SYNCHRONIZATION SERVER (106), COUPLED TO THE SECURITY SERVER AND THE PLURALITY OF SECONDARY DATA STORES, THAT PROVIDES PASSWORD PROPAGATION SYNCHRONIZATION TO EACH OF THE SECONDARY DATA STORES FROM A USER ASSOCIATED WITH ONE OF THE PLURALITY OF CLIENTS SO THAT USER IS ABLE TO MAINTAIN A SINGLE, UNIQUE PASSWORD AMONG PLURALITY OF SECONDARY DATA STORES. THE PASSWORD PROPAGATION IS IMPOSED ON THE PLURALITY OF SECONDARY DATA STORES REGARDLESS OF THE CURRENT PASSWORD STATUS OF THE SECONDARY DATA STORES.
Abstract:
A network system server that provides password synchronization between a main data store and a plurality of secondary data stores is disclosed. The network server further includes a security server, which is coupled to the main data store, a plurality of clients, coupled to the security server for accessing the main data store. Also disclosed is a network system server that provides password composition checking for a plurality of clients.
Abstract:
A method of refactoring or normalising databases to convert soft type information, e.g. tuples of or columns of XML data into hard type information, comprising: profiling the soft type data to generate an attribute list with mapping suggestions to a hardened database structure; generating a data model definition and extract, transform, and load logic for transforming the soft type data based on the attribute list and mapping suggestions; executing the data model definition to create a new or modified database structure; moving data from an existing database structure to the new or modified database structure; and regenerating a services interface for access to the data.
Abstract:
Bei Verfahren zum Bereitstellen von Sicherheit in einem Datenverarbeitungssystem mit Identitätsvermittlungsrichtlinien, die vom Enterprise-Service-Bus (EBS) unabhängig sind, führt eine Vermittlungskomponente auf der Dienstebene Operationen wie z. B. das Vermitteln von Nachrichten (message brokering), die Vermittlung und die Umsetzung von Identitäten durch, um die Interoperabilität zwischen Dienstnutzern und Dienstanbietern zu verbessern. Eine Vermittlerkomponente kann außerdem mit der Identität zusammenhängende Operationen an einen Token-Service oder Handler delegieren. Zur Identitätsvermittlung können Operationen wie z. B. die Identitätsermittlung oder „Erkennung”, die Authentifizierung, Berechtigung, Identitätsumsetzung und Sicherheitsüberprüfung gehören.
Abstract:
The invention provides federated functionality within a data processing system by means of a set of specialized runtimes. Each of the plurality of specialized runtimes provides requested federation services for selected ones of the requestors according to configuration data of respective federation relationships of the requestors with the identity provider. The configuration data is dynamically retrieved during initialization of the runtimes which allows the respective runtime to be specialized for a given federation relationship. Requests are routed to the appropriate specialized runtime using the first requestor identity and the given federation relationship. The data which describes each federation relationship between the identity provider and each of the plurality of requestors is configured prior to initialization of the runtimes. Configuration data is structured into global specified data, federation relationship data and requestor specific data to minimize data change, making the addition or deletion of requestors very scalable.
Abstract:
Provided are techniques for secure matching supporting fuzzy data. A first bloom filter for a first data element is retrieved, wherein each of the characters in the data element has been encrypted with a beginning offset position of the character and encrypted with an end offset position of the character to produce two encrypted values that are added to the first bloom filter. A second bloom filter for a second data element is retrieved. The first bloom filter and the second bloom filter are compared to determine whether there is a match between the first data element and the second data element.
Abstract:
The invention provides federated functionality within a data processing system by means of a set of specialized runtimes. Each of the plurality of specialized runtimes provides requested federation services for selected ones of the requestors according to configuration data of respective federation relationships of the requestors with the identity provider. The configuration data is dynamically retrieved during initialization of the runtimes which allows the respective runtime to be specialized for a given federation relationship. Requests are routed to the appropriate specialized runtime using the first requestor identity and the given federation relationship. The data which describes each federation relationship between the identity provider and each of the plurality of requestors is configured prior to initialization of the runtimes. Configuration data is structured into global specified data, federation relationship data and requestor specific data to minimize data change, making the addition or deletion of requestors very scalable.
Abstract:
A method, system, apparatus, and computer program product are presented for processing certificate revocation lists (CRLs) in a data processing system. Rather than using CRLs for authentication purposes, CRLs are used for authorization purposes, and the responsibility of processing CRLs is placed on a monitoring process within a centralized authorization subsystem rather than the applications that authenticate certificates. A monitoring process obtain newly published CRLs and determines whether revoked certificates are associated with users that possess authorized privileges. If so, then the monitoring process updates one or more authorization databases to reduce or eliminate the authorized privileges for those users.
Abstract:
Bei Verfahren zum Bereitstellen von Sicherheit in einem Datenverarbeitungssystem mit Identitätsvermittlungsrichtlinien, die vom Enterprise-Service-Bus (EBS) unabhängig sind, führt eine Vermittlungskomponente auf der Dienstebene Operationen wie z. B. das Vermitteln von Nachrichten (message brokering), die Vermittlung und die Umsetzung von Identitäten durch, um die Interoperabilität zwischen Dienstnutzern und Dienstanbietern zu verbessern. Eine Vermittlerkomponente kann außerdem mit der Identität zusammenhängende Operationen an einen Token-Service oder Handler delegieren. Zur Identitätsvermittlung können Operationen wie z. B. die Identitätsermittlung oder „Erkennung”, die Authentifizierung, Berechtigung, Identitätsumsetzung und Sicherheitsüberprüfung gehören.