provision message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Subject: [provision] SPML: Assumptions about Directories and RDBMS
- From: "DeSouza, Edwin" <edesouza@jamcracker.com>
- To: provision@lists.oasis-open.org
- Date: Tue, 12 Nov 2002 19:39:58 -0500
Title: Message
Hi,
Within a Corporate
setting, Provisioning is primarily viewed as a security/administrative
function.
However, at
Jamcracker (and any other such Provider), Provisioning is fundamentally about
Billing. Yes, Provisioning enables us to centrally control access, update
user profiles, etc. But, it really is about Billing. All
Provisioning activities result in Billing. This is a very key difference
between how a Corporate IT vs a Provider looks at
Provisioning.
At Jamcracker, we
have made a business decision that all Billing activities *must* happen in the
database. Any thing that could be disputed by the customer, anything that
the customer will want Reports on, etc. This includes AddUser, DeleteUser,
etc. Who did it, when, etc. Only after the database is updated, do
we go and update the Directory. The Directory is
secondary.
So, we would
recommend that SPML remain neutral on the data store. (See how SAML and
XACML remain neutral)
regards,
Edwin.
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Powered by eList eXpress LLC