Most of the hits seem to relate to SharePoint, unfort. so I'm going to
ask here:
Can a asp .net web application be setup to use dual-authentication.
EG: If Active Directory, pass-through; failing that, authenticate by
userid/password (AD or SQL)?
Give some more back-end info.
Our AD has a 'members OU' (many sub-OUs) that our service desk
has control of. I was wanting to see if it were possible to code a
add/delete/reset that the service desk could use and have it so that
an admin of a sub-OU could admin their OWN users as well (limit access
to their own OU)...
Service desk brings up web app...They authomatically (no login needed,
they are a domain user - higher than the 'member OU') w/ full control
over all the members. Member hits the page, MUST login, and can only
see/work w/ the others in their own sub-OU (should be easy enough to
pull the info as it's part of their distinguished name)
Any ideas or pointers??
Thanks again,
David D.
ask here:
Can a asp .net web application be setup to use dual-authentication.
EG: If Active Directory, pass-through; failing that, authenticate by
userid/password (AD or SQL)?
Give some more back-end info.
Our AD has a 'members OU' (many sub-OUs) that our service desk
has control of. I was wanting to see if it were possible to code a
add/delete/reset that the service desk could use and have it so that
an admin of a sub-OU could admin their OWN users as well (limit access
to their own OU)...
Service desk brings up web app...They authomatically (no login needed,
they are a domain user - higher than the 'member OU') w/ full control
over all the members. Member hits the page, MUST login, and can only
see/work w/ the others in their own sub-OU (should be easy enough to
pull the info as it's part of their distinguished name)
Any ideas or pointers??
Thanks again,
David D.