Admin panels usually rely on a login and password, and passwords get reused, phished or guessed. Client certificate login works differently: a certificate is installed on the employee's computer or phone, and the server asks the browser for it before serving any page. From a device without the certificate, even the login page is out of reach.
What users see
When an employee opens admin.example.uz, the browser shows a small dialog listing installed certificates. They pick theirs, the operating system may ask for a PIN to unlock the key store, and the page loads as normal. The choice is remembered for the session. A stranger without a certificate is rejected during the handshake or gets a 403, never a password field, so brute-force attempts and bots hammering the login form simply disappear.
When it makes sense
This works best for a small, stable group, say five to ten staff members using their own work machines. For a public customer portal with hundreds of users it is impractical, because everyone would need help installing a certificate. A certificate does not replace the password; it adds a layer. The certificate proves an approved device, the password proves an approved person, so a stolen laptop alone is not enough.
Example: a school grading panel in Namangan
A private school in Namangan keeps grades and payments in a panel at admin.example.uz used by the director, two academic staff and the accountant. The logs show thousands of login attempts from foreign IP addresses. The school creates an internal certificate authority and issues each of the four staff a separate certificate. Bots no longer see the login page, and if the accountant leaves, only that one certificate is revoked.
Preparing a certificate for an employee
Assuming the internal CA (staff-ca.crt, staff-ca.key) already exists, create a key, a signed certificate and a PKCS#12 bundle for the browser:
openssl req -newkey rsa:2048 -nodes -keyout aziza.key -out aziza.csr -subj "/CN=Aziza Karimova/O=Maktab"
printf "extendedKeyUsage=clientAuth\n" > client.ext
openssl x509 -req -in aziza.csr -CA staff-ca.crt -CAkey staff-ca.key -CAcreateserial \
-out aziza.crt -days 365 -sha256 -extfile client.ext
openssl pkcs12 -export -in aziza.crt -inkey aziza.key -certfile staff-ca.crt \
-out aziza.p12 -name "Aziza Karimova"
OpenSSL asks for an export password; share it over a separate channel such as a phone call. If an older operating system cannot import a file made by OpenSSL 3, recreate it with the -legacy option. Keep staff-ca.key off the panel server.
Installing on devices
On Windows, double-click the .p12 file to launch the import wizard; Chrome and Edge use that store. On macOS, import it into Keychain Access for Safari and Chrome. Firefox has its own store, available in its certificate settings. On Android, use the certificate installation option in security settings, which varies by manufacturer. Afterwards delete the file from downloads and email.
Locking the panel in Nginx
Nginx applies client verification per server block, so put the panel on its own subdomain and leave the main site public:
server {
listen 443 ssl;
server_name admin.example.uz;
ssl_certificate /etc/letsencrypt/live/admin.example.uz/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/admin.example.uz/privkey.pem;
ssl_client_certificate /etc/nginx/staff-ca.crt;
ssl_verify_client optional;
location / {
if ($ssl_client_verify != SUCCESS) {
return 403;
}
proxy_pass http://127.0.0.1:8080;
}
}
optional records the result in $ssl_client_verify so you can return a clear 403; use ssl_verify_client on to refuse such connections outright, and ssl_crl to block revoked certificates. On Apache:
<VirtualHost *:443>
ServerName admin.example.uz
SSLEngine on
SSLCACertificateFile /etc/apache2/staff-ca.crt
SSLVerifyClient require
SSLVerifyDepth 2
</VirtualHost>
Limits and hosting
Certificates expire, new phones need new installs, and lost devices require immediate revocation, so give one person ownership and keep a list of issued certificates. Shared hosting does not let customers change web server settings, so a separate VPS is the practical home for such a panel, with a free Let's Encrypt server certificate. Both are managed from the sayt.uz cabinet, and support can help with setup questions.