[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [provision] SPML identifier issues for the interop ...
Greg – thoughts?
========================================================= Darran Rolls http://www.waveset.com Waveset Technologies Inc drolls@waveset.com (512) 657 8360 =========================================================
-----Original Message-----
The problem is what if two users named John Smith both use the common RA. For the first one there is no problem. For the second one, a request will be made to add a user with the GUID of an already existing user. For our system that is an error and the second add request will fail. Since we are not supporting status, the second user won't know why his user ID/password combination that he entered will not allow him to log onto our system.
Now I could add special logic to make true GUID out of the GUID passed to our system to get around this, but since all of the PSPs should have similar issues, it makes sense to solve this in one place (the common RA). Can the common RA be configured to make sure that the CN is not reused? It would probably be a good idea to make sure the uid is not reused as well, if possible. We could also set the GUID id to the uid instead of the CN and just make sure that the uid is unique.
BTW, if you think having two CNs the same is unlikely, what if one user wants to run through the demo twice from two different vendors?
Jeff Bohren Product Architect OpenNetwork Technologies, Inc
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]