hi
I've never really used interop an I have a question for you all.
I have an web based app which currently resets users Active Directory
passwords. The function which resets the password uses a specific
username and password to access AD and reset the passwords (thats all
this user account can do), this function is in pagename.aspx.vb. I
think it would make more sense to wrap the function that does the
password reset into a COM object, mainly so the username and password
that has rights to reset the accounts is harder to get hold of. Does
this makes sense, is this the right way to go about things?
thanks
david dot bargna at sonyericsson dot com
Paul Clement - 24 Sep 2003 15:03 GMT
¤ hi
¤
¤ I've never really used interop an I have a question for you all.
¤
¤ I have an web based app which currently resets users Active Directory
¤ passwords. The function which resets the password uses a specific
¤ username and password to access AD and reset the passwords (thats all
¤ this user account can do), this function is in pagename.aspx.vb. I
¤ think it would make more sense to wrap the function that does the
¤ password reset into a COM object, mainly so the username and password
¤ that has rights to reset the accounts is harder to get hold of. Does
¤ this makes sense, is this the right way to go about things?
Probably a good idea to use a component. That is what I've done using ADSI and it allows me to
re-use the code in other development environments.
If the code isn't extensive you may also want to look at the System.DirectoryServices .NET library,
which will enable you to build a native .NET component and eliminate the need for interop.
Paul ~~~ pclement@ameritech.net
Microsoft MVP (Visual Basic)
David Bargna - 25 Sep 2003 07:54 GMT
> ¤ hi
> ¤
[quoted text clipped - 17 lines]
> Paul ~~~ pclement@ameritech.net
> Microsoft MVP (Visual Basic)
thanks for the info, I have built a DLL containing my code (which uses
system.directoryservices) call this from my aspx.vb and this seems to
work well
thanks
d
Paul Clement - 25 Sep 2003 13:10 GMT
¤ hi
¤
¤ I've never really used interop an I have a question for you all.
¤
¤ I have an web based app which currently resets users Active Directory
¤ passwords. The function which resets the password uses a specific
¤ username and password to access AD and reset the passwords (thats all
¤ this user account can do), this function is in pagename.aspx.vb. I
¤ think it would make more sense to wrap the function that does the
¤ password reset into a COM object, mainly so the username and password
¤ that has rights to reset the accounts is harder to get hold of. Does
¤ this makes sense, is this the right way to go about things?
¤
Probably a good idea to use a component. That is what I've done using ADSI and it allows me to
re-use the code in other development environments.
If the code isn't extensive you may also want to look at the System.DirectoryServices .NET library,
which will enable you to build a native .NET component and eliminate the need for interop.
Paul ~~~ pclement@ameritech.net
Microsoft MVP (Visual Basic)