I would suggest that asking the web service y directory for information about
provisioning an account (eith by the user x or a provisioning system) be
considered out of scope. The web server y will likely not be able to provide
this, which is one of the reasons that the provisioning systems exist. There
may be some cases where this is supported but in most case these systems are
back-ended by a system that defines acounts for the web service. This account
information would be managed by the provisioning system.
Should the provisioning system provide the information (data required and
process) needed for user x to get an account for web service y? I think that
should be in the scope of psml.
"Silva, Carlos" wrote:
I would like to start a discussion about our proposed scope of work.
This is a user provisioning use case where a user wants to use a simple
web service and needs to get an account with such a service:
1. User requests to use the web service (user x wants to use service y)
either through the provisioning service or through the web service
2. User or provisioning service asks the web service for the data and
needed to provision an account in its service (what data does this
need to create an account and what is the procedure)
3. Web service answers with the data and procedure needed to provision an
4. User or provisioning service follows the procedure and provides data
to create an account in web service y.
5. Account is created in web service y
6. User is notified and can start using the web service.
Is it within our scope to provide all of the XML messaging formats involved
the above? What is in our scope, what is not, and why?
Carlos A Silva
Senior XML Architect
VeriSign XML Trust Services