I have an opensource video conferencing software package installed on a hosted Debian VPS. This is currently working with no functionality issues I am aware of
The objective is for me to be able to create muliple VPS instances from an optised image which will be offered / sold to customers (businesses). Each VPS instance will have a dedicated domain resolving to the public IP of the VPS
A Quick Glossary of Terms
Server Hosts - the company which I am paying for the VPS's
- Admin - the administrator of the server instance/s upon which the software is installed (me)
- Client / Customer - the person or company who will be using the software in order to create video conferences and invite participants to join them
- Participant/s - the 3rd party / parties who will be joining a video meeting request which has been setup by the client / customer
------------------------------
There are two elements of authentication which need to be considered with this project one of which appears to be in place by default
1) when my client creates a meeting room for which participants are to join in order to video conference, participants need to be prompted for a username / password in order to join this meeting. This is inbuilt functionality within the software so as far as I can ascertain this element is okay.
2) - THE JOB REQUIREMENT: as insane as this sounds, the opensource software does not have any method of preventing anyone (knowing either the domain or the IP to which is resolves) from accessing the web UI and then fully utilising the software (creating conferences etc)
Therefore, what I am looking for is (and my terminology and approach could be wrong here) a form of reverse proxy authentication whereby anyone attempting to visit the domain is firstly prompted for a username and password.
It appears there are various options here such as cloudflare, or Windows Domain Controller options, however where I am struggling is a scenario where
Meeting A is arrange for participants XYZ > a meeting request is sent to participants XYZ who are firstly prompted for the "global username / password" to in effect access the server (or the web UI) > then prompted for the user / pass for the specific meeting instance
That's all fine, however unless the "global username / password" is then changed afterwards, the participants would then have access to the web UI again being able to then create their own meetings / use the services.
I'm looking for someone who can review the software and suggest the best course of action, and am happy to provide access to the demo server for the right candidate.
Canidates must have a proven track record within this arena and must be within the UK as well as being immediately available for start.
There is a great opportunity for ongoing work for general web development. Ideal skill sets would be
Javascript HTML vB Terminal server admin skills IIS API programming skills ASP SQL MySQL MS Access
A good communicator with the ability to clearly communicate timescales, justify budgets and timescales and work to deadlines.
Process will be a review of CV / previous projects followed by a 10 - 20 minute call with MD to ensur a cultural fit.
£40 is topend per hour rate and experience will reflect rate offered.
