|
I think that I have enough information
about what needs to be done. ADAM is definitely a require solution to this
problem. I have been reading more on the use and functionality of ADAM and it
fits the bill. In fact, the example that is provided in the ADAM documentation
provide by Microsoft is just about as close to the real life situation I am
facing as you can get. Thank you all for your replies, Edwin From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Al Mulnick A little more on the overall picture. What you seem to be
describing is an identity lifecycle management environment (call that
marketecture :) To play back requirements: 1) system must be able to account for identities for undertemined
amount of time for the purposes of reporting 2) system must be resilient to usage patterns 3) system must be securable in its final implementation 4) system must be able to authenticate user objects utilizing name and
password credential pair. Some thoughts: regardless of the identity store you use, you'll want to pay particular
attention to identity lifecycle. That is, what happens to the identity from
cradle to the grave? An identity archive might be more of a solution.
Maybe a separate directory or even a database somewhere else that stores
information about past identities for the purposes of reporting. The rest
of the stuff(day to day) is pretty straightforward and is easily solvable based
on the information you've given. The process of archiving a user, i.e.
what to do, what to keep, etc is something you'll have to define for your
company. Make it flexible and comprehensible enough that you don't have
to revisit very often, but that you could if you had to. Not sure synchronization fits the bill here because you haven't said
that all accounts must live in AD. In fact, I suspect that some may
not. Is that the case? Al
On 2/28/06, Tomasz
Onyszko <[EMAIL PROTECTED]>
wrote: Edwin wrote: |
