If it's adequate to just identify the company/organization, you could issue them a client key/cert pair, do client-certificate auth and skip worrying about your customer's organizational changes. ![]() If you need to identify users, you'll need a process for customer employees to request access as well as a way to revoke access. In this case, you'll need to setup an authentication mechanism. NOTE: I'm assuming the "from any device with password protection" stanza means access to your site's protected not the user's device. While TLS is technically optional, it's likely your IT department will require it (your internal IT department should be able to give you a key/cert pair). ![]() Install nginx or apache as a webserver (this might already be done for you).The methodology will be something like the following (NOTE: this assumes you have a Unix-like VM with an external IP address, domain, a DNS name for your VM and root authority): ![]() I've deployed two shiny servers on VMs for personal use.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |