|
I
think there's a need to reinvestigate the idea that a single directory doesn't
need to exist in a single product.
For
instance, we're probably a few months away from completing a project in which we
have a single directory of our customers, but portions of that directory exist
in our CRM and ERP platforms, as well as our own network services platform.
However, the data itself is scoped such that the only data relevant to a
specific platform is available in that platform. The combination of attributes
and objects together make a single directory.
Roger
--------------------------------------------------------------
Roger D. Seielstad -
MTS MCSE MS-MVP
Sr. Systems Administrator
Inovis Inc.
Personally I'm with you on the privacy reasons. (can you say
HIPAA?) But its a
matter of bringing all the options with pro's and con's to the table so
management can make an informed decision. The HR (peoplesoft), the web
team (coldfusion), and Security (excel & access databases) departments
want to tie all their databases together (or replace them) for better
identity management without buying something like waveset www.waveset.com.
The
main idea 'on the table' is use Active Directory as the central
authority with a feed from Peoplesoft for user adds/deletes and a feed to
peoplesoft for things like email addrs, user locations, phone numbers etc.
Also use AD via LDAP as the authentication point for all
intranet/extranet web content.
I think using the "EmployeeID" attribute and locking it down
would meet the needs as stated to me so far. But if the
requirements change / expand I want to make sure I am prepared to address
it.
Clyde
Besides the obvious, "don't put SSN in the directory for
privacy reasons" I'd have to ask what requirements you have. For
example, why create a new attribute? Why not use an existing that you
won't use anyway?
Al
Does anyone have
any advice for do's and dont's with regards to adding new attributes into
Active Directory?
Thanks
Clyde
Burns
Norton
Healthcare
This message is confidential, intended only
for the named recipient(s) and may contain information that is privileged or
exempt from disclosure under applicable law. Any patient health information
must be delivered immediately to intended recipient(s). If you are not the
intended recipient(s), you are notified that the dissemination, distribution
or copying of this message is strictly prohibited. If you receive this message
in error, or are not the named recipient(s), please notify the sender at
either the e-mail address or telephone number above and discard this e-mail.
Thank you.
This message is confidential, intended only for the named
recipient(s) and may contain information that is privileged or exempt from
disclosure under applicable law. Any patient health information must be
delivered immediately to intended recipient(s). If you are not the intended
recipient(s), you are notified that the dissemination, distribution or copying
of this message is strictly prohibited. If you receive this message in error,
or are not the named recipient(s), please notify the sender at either the
e-mail address or telephone number above and discard this e-mail. Thank
you.
|
