AD LDS and Occasionally Connected

[RichS]

I'm looking into a security model in which we will have an occasionally connected (Click Once) application.

(Briefly: Our users use tablet PCs to collect data while in the field. If they have a broadband connection they can access network resources. Without a connection they can still capture data and MS Synch Services will synch things up when a connection is available.)

We use Active Directory for managment of Domain users and I'm looking to see if the Lightweight Directory Services (LDS) can be used when disconnected from our Domain to check authentication and authorization for the application while disconnected. Any ideas?

 

[jmeckley]

i wouls start in forum774.
a slightly different approach:
1. always assume a disconnected mode and authenticate locally.
2. only use network access when the client must sync with the server(s).

the idea of using network authentication when on the network and LDS when disconnected may seem logical, but your adding complications to the system architecture. by assuming the user is always disconnected you are only concerned with 1 authentication store.

Isolate any processes that require network resources. when they are needed confirm the user is connected and authenticated before proceeding.

Jason Meckley
Programmer
Specialty Bakers, Inc.

 

[RichS]

J, thanks for the response. All our apps currently authenticate locally. Our security team is considering a policy whereas no user information is maintained in application tables. So it's a potential policy that is driving this research. Thanks for the link to the LDAP forum.

Rich