Contents

User's Guide
Overview
What It Is
What's New
Key Features List
ClearBox Enterprise vs ClearBox
System Requirements
Purchasing Licenses
Getting Started
Quick Start
Understanding Server Components
Managing User Accounts
Configuring RADIUS Realms
Realm Settings
Realm Rules
Dynamic Realm Rules
Authentication
Authentication Protocols Compatibility
Logging Authentication Packets
Logging Discarded Requests
Authorization
Accounting
Account Log Files
Realm Settings
Configuring SQL Queries
Private RADIUS Attributes
Regular Expressions Syntax
RADIUS Clients
RADIUS Client Settings
Dynamic Clients Settings
SQL Data Sources
SQL Data Source Settings
LDAP Servers
LDAP Server Settings
Remote RADIUS Servers
Remote RADIUS Server Settings
State Servers
State Server Settings
Meta Configuration
Meta Configuration
Meta Configuration Settings
Meta Base Schema
TLS Settings
Creating SSL Certificates
Creating Server Sertificate
Requesting Server Certificate
Creating Client Certificates
Revoking a Certificate or Renewing CRL
Exporting CA Certificate
Issuing a Certificate in Active Directory CA
Remote Configuration
Advanced ISP Billing Integration
DTH Billing Integration
Platypus Billing System Intergration
OnDO SIP Server Integration
How Do I...
Wi-Fi Security
Wireless Authentication
Wi-Fi and RADIUS
Supported EAP Authentication Types
Security Considerations
10 Tips for Wireless Network Security
Administering the Server
Logging
Debug Logs
Troubleshooting
Using Client Tool
List of Server Errors
Maintaining RADIUS Dictionary
Basic Concepts
AAA
Authentication
Wireless Authentication
Authentication Protocols
Authorization
Accounting
RADIUS
RADIUS
Realms
RADIUS Proxy
RADIUS Attributes
Example of RADIUS Packet Transactions
List of Standard RADIUS Attributes
Glossary
Technical Support
Purchasing Licenses
Contacts

 
Home
ClearBox Enterprise Server 2.0 Online Manual
Prev Page Next Page
 
 
ClearBox Enterprise Serverâ„¢ 2.0. User's Guide

Creating Client Certificates

Some authentication protocols, like EAP-TLS, require that a user should present his digital certificate to an authentication server to identify itself to the server. This in turn leads to the need for a Public Key Infrastructure (PKI). Since the requirements of maintaining a PKI are substantial, most organizations opt instead to use PEAP, which require a digital certificate for the server only.

Anyway, if you plan to use EAP-TLS, a client certificate may be obtained from some existing certificate authority (which is already exists in your organization or purchased from a commercial CA). Still you may have created your own certificate authority and have issued the server certificate by yourself. The same CA may issue client certificates.

Run Certificates Wizard and select the fourth option:

Specify the root CA password which you defined during its setup:

Click Next. Input the client personal information, its password (will be used later when the client installs the certificate):

Click Next and input the client location information:

Click Next and specify where the new certificate is saved:

Click Next.

After some time depending on the server machine performance you'll be shown the success message:

It means that the client certificate is created successfully. Deliver it on a client computer and run it. Click Next to install, Next, type in the password you have specified during the certificate creation. Click Next. Agree with Automatically select the certificate store choice and click Next. Finally click Finish.

NOTE. Client public certificate copy is saved automatically in <Server installation path>\CA\ClientCerts\. Their name have the form client<Year><Month><Day><Hour><Minutes><Seconds>.crt. Don't remove them as they may be used for certificates management (listing, revoking. blocking, etc).


© 2001-2007 XPerience Technologies. www.xperiencetech.com
Converted from CHM to HTML with chm2web Pro 2.7 (unicode)