Mike,
Ideally the user would select which attribute(s) to release, radio buttons,
check boxes, etc. Not sure if the custom attribute scripts could do this, but
would probably also require changes to the log in flow.
Ray
On Mon, 2020-05-18 at 10:19 -0700, mbar...@scad.edu wrote:
At our
If the double-account people are still the exception rather than the rule
(even with a couple hundred), I recommend a consistent naming scheme for
them with a prefix or something (like our "adm_netid"). Then you can just
refer to "your xyz account" where "xyz" is the prefix, and it's always
clear
Thank you again for responding. I wish we didn't split email, but we did
a long time ago - during the initial email implementation - and we never
tried to consolidate.
Fortunately, I don't have the "which account" problems. Students get a
pretty clear setup, and anything extra would go to
In our case no, because the "staff" account is really just an
"administrator" account -- so it's the one used to be an application (or
system) admin rather than the user's regular account. Most of the people
who have those are IT people, although a few non-IT people are starting to
get them as we
David, Richard,
Thank you very much. Did you or do you have issues with students/staff
getting confused on which account to use? Any tips for handling that other
than FAQs? We've got several hundred people with dual accounts.
Thank you,
Mike
On Monday, May 18, 2020 at 2:05:05 PM UTC-4,
We do pretty much the same thing Richard is doing. The different accounts
are in different OUs in AD, and IAM handles the provisioning. Way back
when, we configured CAS with multiple "directories" that are the same AD
server with different DNs (one for each OU). We could probably stop doing
that
We just have separate accounts in AD, which is where we are
authenticating and doing attribute release from. The IAM system is
responsible for correctly populating the directory and end application
if needed in the correct way for each account. This requires multiple
accounts and passwords, and
At our university, we have some applications where one person will only
have one account and the application is aware of the different "roles" a
person might have, i.e., student, staff, faculty and/or alumni. We also
have some other applications where a person may have a student account and