Service Provisioning Markup Language: Difference between revisions

Revision as of 10:39, 7 February 2005

Revision as of 10:47, 7 February 2005

Line 1:

{{stub}}

SPML stands for Service Provisioning Markup Language (SPML). SPML is usedan as[[XML]]-based aframework, markupbeing languagedeveloped thatby describes/defines[[OASIS the(organization)|OASIS]], servicesfor thatexchanging areuser, availableresource toand usersservice ofprovisioning aninformation between ITcooperating systemorganizations.

==SPML Protocol==

Line 12:

(this information was copied from http://www.openspml.org/spml_faq.html)

==Goal of SPML==

The goal of SPML is to allow organizations to securely and quickly set up user interfaces for Web services and applications, by letting enterprise platforms such as Web portals, application servers, and service centers generate provisioning requests within and across organizations. This can lead to automation of user or system access and entitlement rights to electronic services across diverse IT infrastructures, so that customers are not locked into proprietary solutions.

For example, a supply partner (Company A) goes to its partner's (Company B) supply chain portal and requests access to its inventory data, which is stored in a back-office system. In response, Company B initiates a request using SPML to communicate with SPML-enabled identity management software. After automatically acquiring the appropriate permissions, Company B grants the appropriate access levels to Company A to gain access to the data it needs.

This process takes place without the need for the portal environment to have an intimate understanding of the back-office environment. In other words, it's all automatic. The prototype encompasses all of the provisions of the proposed SPML standard while also leveraging the benefits of the Security Assertion Markup Language ([[SAML]]).

(this info copied from http://www.nwfusion.com/details/5623.html)

==External Links==