What methods of authentication are supported by the VDS?
In terms of authentication, VDS acts as an intermediary between a client and the virtualized data sources. Different methods are supported. Proxy Authentication, Delegation of Credentials: In the simplest case, the credentials is a password to check against an existing data source. In this case, the VDS acts as a proxy and routes the request to the relevant application. The authentication is delegated to the underlying application. However, even in this simple case, volume and scalability can sometimes be an issue since this method tends to generate many connections (one for each user bind/authenticate against the underlying identity store).
In terms of authentication, VDS acts as an intermediary between a client and the virtualized data sources. Different methods are supported. Proxy Authentication, Delegation of Credentials: In the simplest case, the credentials is a password to check against an existing data source. In this case, the VDS acts as a proxy and routes the request to the relevant application. The authentication is delegated to the underlying application. However, even in this simple case, volume and scalability can sometimes be an issue since this method tends to generate many connections (one for each user bind/authenticate against the underlying identity store). Direct Authentication by VDS: Another approach is to have VDS maintain the connection (using VDS connection pooling capability) with the data source and providing the authentication itself (a compare credentials operation requiring only a read on an established connection on the data source instead of a full connection and an authentication). User
