Abstract: Technology for supporting multiple application program interfaces. A main application identifies an application program interface to employ with a program outside of the main program, such as a plug-in. In one instance, the main application employs an application program interface registration list to identify the proper application program interface to use with a desired program—allowing the proper application program interface to be identified before interacting with the desired program. The registration list includes a set of entries. Each entry identifies a program and a corresponding application program interface to use with the program. The main application accesses an entry in the registration list for the desired program to identify the corresponding application program interface. When an event occurs, the main application accesses an event catalog entry to identify a program that corresponds to the event and the application program interface that corresponds to the program.

Abstract: Technology is disclosed for automatically configuring attribute sets, such as object classes and classes of database tables. A system employing an object class, such as an Identity or Access System, configures the object class for use by the system. One version of the system employs a template that includes entries for attributes in the object class. An example entry identifies an attribute and a corresponding meta-attribute. Alternatively, the template may support multiple object classes and include entries with different types of information. During configuration, the system selects an attribute in the object class and identifies a corresponding template entry. The system configures the attribute, based on the information in the template entry. One type of configuration includes the system assigning a meta-attribute from the template entry to the attribute. The system repeats this procedure for each attribute in the object class or at least a subset of the attributes that need configuration.

Abstract: Technology is disclosed for securely persisting a network resource identifier, such as a URL, that addresses a network resource, such as a portal. The network resource identifier is persisted from one network resource to another. A system accessed through the portal receives requests for accessing network resources associated with the system's applications and resources. In one example, the system provides the applications and resources via web pages. The system generates a link selector, based on information persisted in the requests. Selection of the link selector immediately brings a system user to the portal. Each request includes a parameter that corresponds to the network resource identifier for the portal. The system employs this parameter to obtain the information necessary to generate the link selector, such as an image and mouse-over text. The system includes a parameter in outgoing requests that calls for persisting the network resource identifier for the portal.

Abstract: In response to a user request, an Identity System generates an Output XML containing raw identity information organized in accordance with a set of XML templates. The Identity System dynamically determines the desired response type and prepares the response from the Output XML. One response type is server-side processing—the Identity System combines the Output XML with XSL stylesheets to generate a HTML response. An alternative response type is client-side processing—the Identity System supplies the user with the Output XML. In further client-side embodiments, the Identity System provides XSL stylesheet references along with the Output XML. Additional embodiments provide for the Identity System to perform customized post-processing on the Output XML.

Abstract: An Identity System delivers customized request responses that integrate the results of multiple programs. The Identity System receives and translates a user request. The Identity Systems employs a program service to identify all the programs required to complete the request. The Identity System uses a XML data registry to retrieve a XML template and XSL stylesheet for each program. The Identity System executes all of the programs for the request and organizes their results into a single data structure, based on the templates for each program. The Identity System then applies attribute display characteristics to convert the data structure into a single Output XML. The Output XML can be provided directly to the user or receive further processing using the retrieved XSL stylesheets.

Abstract: Technology is disclosed for automatically configuring attribute sets, such as object classes and classes of database tables. A system employing an object class, such as an Identity or Access System, configures the object class for use by the system. One version of the system employs a template that includes entries for attributes in the object class. An example entry identifies an attribute and a corresponding meta-attribute. Alternatively, the template may support multiple object classes and include entries with different types of information. During configuration, the system selects an attribute in the object class and identifies a corresponding template entry. The system configures the attribute, based on the information in the template entry. One type of configuration includes the system assigning a meta-attribute from the template entry to the attribute. The system repeats this procedure for each attribute in the object class or at least a subset of the attributes that need configuration.

Abstract: Technology is disclosed for supporting multiple application program interfaces. A main application identifies an application program interface to employ with a program outside of the main program, such as a plug-in. In one instance, the main application employs an application program interface registration list to identify the proper application program interface to use with a desired program—allowing the proper application program interface to be identified before interacting with the desired program. The registration list includes a set of entries. Each entry identifies a program and a corresponding application program interface to use with the program. The main application accesses an entry in the registration list for the desired program to identify the corresponding application program interface. One example of a registration list is an event catalog with each entry correlating an event to a program and the application program interface used by the program.

Abstract: Technology is disclosed for securely persisting a network resource identifier, such as a URL, that addresses a network resource, such as a portal. The network resource identifier is persisted from one network resource to another. A system accessed through the portal receives requests for accessing network resources associated with the system's applications and resources. In one example, the system provides the applications and resources via web pages. The system generates a link selector, based on information persisted in the requests. Selection of the link selector immediately brings a system user to the portal. Each request includes a parameter that corresponds to the network resource identifier for the portal. The system employs this parameter to obtain the information necessary to generate the link selector, such as an image and mouse-over text. The system includes a parameter in outgoing requests that calls for persisting the network resource identifier for the portal.

Abstract: In response to a user request, an Identity System generates an Output XML containing raw identity information organized in accordance with a set of XML templates. The Identity System dynamically determines the desired response type and prepares the response from the Output XML. One response type is server-side processing—the Identity System combines the Output XML with XSL stylesheets to generate a HTML response. An alternative response type is client-side processing—the Identity System supplies the user with the Output XML. In further client-side embodiments, the Identity System provides XSL stylesheet references along with the Output XML. Additional embodiments provide for the Identity System to perform customized post-processing on the Output XML.

Abstract: An Identity System delivers customized request responses that integrate the results of multiple programs. The Identity System receives and translates a user request. The Identity Systems employs a program service to identify all the programs required to complete the request. The Identity System uses a XML data registry to retrieve a XML template and XSL stylesheet for each program. The Identity System executes all of the programs for the request and organizes their results into a single data structure, based on the templates for each program. The Identity System then applies attribute display characteristics to convert the data structure into a single Output XML. The Output XML can be provided directly to the user or receive further processing using the retrieved XSL stylesheets.