authentication feature

[james8aus]

Hi,

I would like to know if the following feature is in the works, or already available, or could be implemented...

Using a pretty standard vnc config, when i remote control a user i am prompted to enter a password to authenticate (obviously this is part of uVNC already)

I would like to be able to make the user being remote controlled , re-authenticate/ prove their identity prior to the remote control session being accepted.

So if i step it through it would be like this:

1. User requires support
2. User calls support and provides ip address
3. Support initiates connection to PC via given IP address
4. Support is prompted to authenticate, prior to connecting to the users PC
4. Support authenticates successfully
5. User is prompted to enter their windows password (AD password, on a domain) - this is essentially the equivalent as the current feature where the user has to accept the connection.
6. User authenticates successfully
7. Remote connection is started
8. etc...

Anyone have any thoughts on this?

cheers
JP

[nobody3]

good ideaz

almost already implemented as SC http://uvnc.com/pchelpware/sc/index.html


So if modify step it through it would be like this: my additions are in red

1. User requires support
2. User calls support and provides ip address and downloads a customised SC from somewhere
3. Support initiates connection to PC via given IP address
4. Support is prompted to authenticate, prior to connecting to the users PC
4. Support authenticates successfully
since the user called there is no need to auth, some the user downloads is good enough auth
5. User is prompted to enter their windows password (AD password, on a domain) - this is essentially the equivalent as the current feature where the user has to accept the connection.
this will have to be added ...
6. User authenticates successfully
7. Remote connection is started
8. etc...

[james8aus]

Hi "nobody3",

thanks for the reply.

I am looking for this to be integrated into the core uVNC product, as we utilise that, not the SC product. The SC product is not suitable in a enterprise type environment as it connects back to a specific IP address (correct me if im wrong).

I will repeat my steps with additional details:

1. User requires support
1.1 User already has uVNC installed (as a service) and configured to authenticate against Active Directory (this has been deployed with configuration via a Software deployment tool)
2. User calls support and provides their ip address (uVNC is already installed)
3. Support initiates connection to PC via given IP address
4. Support is prompted to authenticate against Active Directory based on the uVNC configuration already deployed, prior to connecting to the users PC
4. Support authenticates successfully against Active Directory (this is definitely a requirement for me)
5. User is prompted to enter their windows password (AD password, on a domain) - this is essentially the equivalent as the current feature where the user has to accept the connection.
6. User authenticates successfully
7. Remote connection is started
8. etc...

As i am new to this forum and the development cycle for uVNC, is anyone able to tell me or direct me to a uVNC roadmap or goal features/timeframes between releases (if any).

cheers
JP