We need an abstraction layer around the NT security
roles. I would like to leave the authentication (i.e.
passwords, etc.) handled by Active Directory and
Windows NT. SharpSchedule would provide a means to
wrap NT user roles over to internal groups roles (see
Plone security for an example:
I am not sure if managing a set of internal roles will
scale but the goal is to:
- make it easier to switch between forms and NT
- not store password/ usernames inside of the
application (i.e. the application should just be handed
an authentication token)
- provide an easier way for managing security when
using domain authentication (currently file level
permission is being used).
Log in to post a comment.