一、证书制作
1、证书制作前的准备工作
下载openvpn-2.1.1(http://openvpn.net/release/openvpn-2.1.1-install.exe),并在windows上安装。
进入C:\Program Files\OpenVPN\easy-rsa目录,首先运行init-config ,该命令生成vars.bat,我们可以对vars.bat中的KEY_COUNTRY、KEY_PROVINCE等信息进行修改:
修改完成后,运行vars.bat,以使参数生效,然后再运行clean-all.bat。
2、制作根证书
运行build-ca.bat,类似Country Name等之前已经在vars.bat中设置好的变量,可以直接按回车键通过,注意:
Common Name (eg, your name or your server's hostname) []:随便输入公司的名字即可。
Sign the certificate? [y/n]:输入y;
1 out of 1 certificate requests certified, commit? [y/n]输入y。
该名称运行成功后,在子目录keys下生成了根证书ca.crt,另外也生成了根证书的私钥文件ca.key。
3、制作服务器证书
运行build-key-server server,注意:
Common Name (eg, your name or your server's hostname) []:需要填入服务器的域名或者服务器的IP地址,注意这个域名或者IP地址需要和Apache httpd.conf中的ServerName一致。
Sign the certificate? [y/n]:输入y;
1 out of 1 certificate requests certified, commit? [y/n]输入y。
该命令运行成功后,在子目录keys下生成了server.crt(服务器证书)和server.key(服务器证书的私钥)。
4、制作客户端访问证书
运行build-key-pkcs12 <证书名称>,例如build-key-pkcs12 sunny。
注意:
Common Name (eg, your name or your server's hostname) []输入授权用户的名称,比如Sunny;
Sign the certificate? [y/n]:输入y;
1 out of 1 certificate requests certified, commit? [y/n]输入y。
二、服务器端的代码编写
<?php
function greet($param) {
$retval = 'Hello '.$param;
return new SoapParam($retval, 'greetReturn');
}
function accessAuthLogin($para){
$retval = "";
return new SoapParam($retval,'accessAuthLoginRES');
}
$server = new SoapServer(null, array('uri' => 'http://wso2.org/wsf/php/helloService'));
$server->addFunction('greet');
$server->addFunction('accessAuthLogin');
$server->handle();
?>
三、客户端代码编写
<?php try { $client = new SoapClient(null, array( 'local_cert'=>'mycert.pem', 'location' => 'https://192.168.1.81/wccenter_server.php', 'uri' => 'http://wso2.org/wsf/php/helloService')); $header = new SoapHeader('http://net-east.com/soapheader/', 'commandType', 'greet'); $client->__setSoapHeaders($header); $result = $client->__soapCall('greet', array(new SoapParam('Sam', 'name'))); printf("Result = %s", $result); } catch (Exception $e) { print_r($e); } ?>
四、Apache的ssl配置
#
# This is the Apache server configuration file providing SSL support.
# It contains the configuration directives to instruct the server how to
# serve pages over an https connection. For detailing information about these
# directives see <URL:http://httpd.apache.org/docs/2.2/mod/mod_ssl.html>
#
# Do NOT simply read the instructions in here without understanding
# what they do. They're here only as hints or reminders. If you are unsure
# consult the online docs. You have been warned.
#
LoadModule ssl_module modules/mod_ssl.so
#
# When we also provide SSL we have to listen to the
# the HTTPS port in addition.
#
Listen 443
##
## SSL Global Context
##
## All SSL configuration in this context applies both to
## the main server and all SSL-enabled virtual hosts.
##
#
# Some MIME-types for downloading Certificates and CRLs
#
AddType application/x-x509-ca-cert .crt
AddType application/x-pkcs7-crl .crl
# Pass Phrase Dialog:
# Configure the pass phrase gathering process.
# The filtering dialog program (`builtin' is a internal
# terminal dialog) has to provide the pass phrase on stdout.
SSLPassPhraseDialog builtin
# Inter-Process Session Cache:
# Configure the SSL Session Cache: First the mechanism
# to use and second the expiring timeout (in seconds).
#SSLSessionCache dc:UNIX:/var/cache/mod_ssl/distcache
SSLSessionCache shmcb:/var/cache/mod_ssl/scache(512000)
SSLSessionCacheTimeout 300
# Semaphore:
# Configure the path to the mutual exclusion semaphore the
# SSL engine uses internally for inter-process synchronization.
SSLMutex default
# Pseudo Random Number Generator (PRNG):
# Configure one or more sources to seed the PRNG of the
# SSL library. The seed data should be of good random quality.
# WARNING! On some platforms /dev/random blocks if not enough entropy
# is available. This means you then cannot use the /dev/random device
# because it would lead to very long connection times (as long as
# it requires to make more entropy available). But usually those
# platforms additionally provide a /dev/urandom device which doesn't
# block. So, if available, use this one instead. Read the mod_ssl User
# Manual for more details.
SSLRandomSeed startup file:/dev/urandom 256
SSLRandomSeed connect builtin
#SSLRandomSeed startup file:/dev/random 512
#SSLRandomSeed connect file:/dev/random 512
#SSLRandomSeed connect file:/dev/urandom 512
#
# Use "SSLCryptoDevice" to enable any supported hardware
# accelerators. Use "openssl engine -v" to list supported
# engine names. NOTE: If you enable an accelerator and the
# server does not start, consult the error logs and ensure
# your accelerator is functioning properly.
#
SSLCryptoDevice builtin
#SSLCryptoDevice ubsec
##
## SSL Virtual Host Context
##
<VirtualHost _default_:443>
# General setup for the virtual host, inherited from global configuration
#DocumentRoot "/var/www/html"
#ServerName www.example.com:443
# Use separate log files for the SSL virtual host; note that LogLevel
# is not inherited from httpd.conf.
ErrorLog logs/ssl_error_log
TransferLog logs/ssl_access_log
LogLevel warn
# SSL Engine Switch:
# Enable/Disable SSL for this virtual host.
SSLEngine on
# SSL Protocol support:
# List the enable protocol levels with which clients will be able to
# connect. Disable SSLv2 access by default:
SSLProtocol all -SSLv2
# SSL Cipher Suite:
# List the ciphers that the client is permitted to negotiate.
# See the mod_ssl documentation for a complete list.
SSLCipherSuite ALL:!ADH:!EXPORT:!SSLv2:RC4+RSA:+HIGH:+MEDIUM:+LOW
# Server Certificate:
# Point SSLCertificateFile at a PEM encoded certificate. If
# the certificate is encrypted, then you will be prompted for a
# pass phrase. Note that a kill -HUP will prompt again. A new
# certificate can be generated using the genkey(1) command.
SSLCertificateFile /etc/httpd/keys/test81.crt
# Server Private Key:
# If the key is not combined with the certificate, use this
# directive to point at the key file. Keep in mind that if
# you've both a RSA and a DSA private key you can configure
# both in parallel (to also allow the use of DSA ciphers, etc.)
SSLCertificateKeyFile /etc/httpd/keys/test81.key
# Server Certificate Chain:
# Point SSLCertificateChainFile at a file containing the
# concatenation of PEM encoded CA certificates which form the
# certificate chain for the server certificate. Alternatively
# the referenced file can be the same as SSLCertificateFile
# when the CA certificates are directly appended to the server
# certificate for convinience.
#SSLCertificateChainFile /etc/pki/tls/certs/server-chain.crt
# Certificate Authority (CA):
# Set the CA certificate verification path where to find CA
# certificates for client authentication or alternatively one
# huge file containing all of them (file must be PEM encoded)
SSLCACertificateFile /etc/httpd/keys/ca.crt
# Client Authentication (Type):
# Client certificate verification type and depth. Types are
# none, optional, require and optional_no_ca. Depth is a
# number which specifies how deeply to verify the certificate
# issuer chain before deciding the certificate is not valid.
SSLVerifyClient require
SSLVerifyDepth 1
# Access Control:
# With SSLRequire you can do per-directory access control based
# on arbitrary complex boolean expressions containing server
# variable checks and other lookup directives. The syntax is a
# mixture between C and Perl. See the mod_ssl documentation
# for more details.
#<Location />
#SSLRequire ( %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \
# and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \
# and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \
# and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \
# and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20 ) \
# or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/
#</Location>
# SSL Engine Options:
# Set various options for the SSL engine.
# o FakeBasicAuth:
# Translate the client X.509 into a Basic Authorisation. This means that
# the standard Auth/DBMAuth methods can be used for access control. The
# user name is the `one line' version of the client's X.509 certificate.
# Note that no password is obtained from the user. Every entry in the user
# file needs this password: `xxj31ZMTZzkVA'.
# o ExportCertData:
# This exports two additional environment variables: SSL_CLIENT_CERT and
# SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
# server (always existing) and the client (only existing when client
# authentication is used). This can be used to import the certificates
# into CGI scripts.
# o StdEnvVars:
# This exports the standard SSL/TLS related `SSL_*' environment variables.
# Per default this exportation is switched off for performance reasons,
# because the extraction step is an expensive operation and is usually
# useless for serving static content. So one usually enables the
# exportation for CGI and SSI requests only.
# o StrictRequire:
# This denies access when "SSLRequireSSL" or "SSLRequire" applied even
# under a "Satisfy any" situation, i.e. when it applies access is denied
# and no other module can change it.
# o OptRenegotiate:
# This enables optimized SSL connection renegotiation handling when SSL
# directives are used in per-directory context.
#SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
<Files ~ "\.(cgi|shtml|phtml|php3?)$">
SSLOptions +StdEnvVars
</Files>
<Directory "/var/www/cgi-bin">
SSLOptions +StdEnvVars
</Directory>
# SSL Protocol Adjustments:
# The safe and default but still SSL/TLS standard compliant shutdown
# approach is that mod_ssl sends the close notify alert but doesn't wait for
# the close notify alert from client. When you need a different shutdown
# approach you can use one of the following variables:
# o ssl-unclean-shutdown:
# This forces an unclean shutdown when the connection is closed, i.e. no
# SSL close notify alert is send or allowed to received. This violates
# the SSL/TLS standard but is needed for some brain-dead browsers. Use
# this when you receive I/O errors because of the standard approach where
# mod_ssl sends the close notify alert.
# o ssl-accurate-shutdown:
# This forces an accurate shutdown when the connection is closed, i.e. a
# SSL close notify alert is send and mod_ssl waits for the close notify
# alert of the client. This is 100% SSL/TLS standard compliant, but in
# practice often causes hanging connections with brain-dead browsers. Use
# this only for browsers where you know that their SSL implementation
# works correctly.
# Notice: Most problems of broken clients are also related to the HTTP
# keep-alive facility, so you usually additionally want to disable
# keep-alive for those clients, too. Use variable "nokeepalive" for this.
# Similarly, one has to force some clients to use HTTP/1.0 to workaround
# their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and
# "force-response-1.0" for this.
SetEnvIf User-Agent ".*MSIE.*" \
nokeepalive ssl-unclean-shutdown \
downgrade-1.0 force-response-1.0
# Per-Server Logging:
# The home of a custom SSL log file. Use this when you want a
# compact non-error SSL logfile on a virtual host basis.
CustomLog logs/ssl_request_log \
"%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"
</VirtualHost>
五、放入相关文件 其中mycert.pem文件如下方法生成: [root@localhost portal]# cat testclient.key > mycert.pem [root@localhost portal]# cat testclient.crt >> mycert.pem
相关推荐
手把手教你搭建https服务器,部署ssl证书到php java服务器(Nginx-Apache PHP-Tomcat java+SSL证书) 1.购买免费的SSL证书 2.下载SSL证书 3.往nginx上新增ssl 4.往Apache上新增ssl 5.往Tomcat上新增ssl 6.解决警告 7....
MySQL5.0\\data或MySQL4.0\\data 4、网站根目录[HTML,PHP]www\\htdocs [ASP]www\\asp [CGI,Perl]www\\cgi-bin<br>5、访问本机请用http://127.0.0.1/或https://127.0.0.1/ (如果开启SSL) 6、非默认端口,...
5、访问本机请用http://127.0.0.1/或https://127.0.0.1/ (如果开启SSL) 6、非默认端口,网址为http://127.0.0.1:端口/或https://127.0.0.1:端口/ 7、如果在“扩展功能”中选择使用Memcached,它的端口为:11211 8、...
5、访问本机请用http://127.0.0.1/或https://127.0.0.1/ (如果开启SSL) 6、非默认端口,网址为http://127.0.0.1:端口/或https://127.0.0.1:端口/ 7、如果在“扩展功能”中选择使用Memcached,它的端口为:...
nginx SSL 变量与 Apache mod_ssl 模块相比,这会在 nginx 中创建向后兼容的 SSL 变量; 访问 SSL 客户端证书特别有趣。 一些变量由 nginx 提供,其他一些变量必须通过带有 Lua-OpenSSL 接口的 nginx-Lua 计算。 ...
运行下载好的“apache_2.0.55-win32-x86-no_ssl.msi”,出现如下界面: 出现Apache HTTP Server 2.0.55的安装向导界面,点“Next”继续 确认同意软件安装使用许可条例,选择“I accept the terms in the ...
5.支持访问控制。 6.支持重定向和重写规则 7.支持ssl。 pache HTTP Server(简称Apache)是Apache软件基金会的一个开放源码的网页服务器,可以在大多数计算机操作系统中运行,由于其多平台和安全性被广泛使用,是最...
5、访问本机请用http://127.0.0.1/或https://127.0.0.1/ (如果开启SSL) 6、非默认端口,网址为http://127.0.0.1:端口/或https://127.0.0.1:端口/ 7、APMServ集成了以下软件: Apache 2.2.3 [HTTP服务器] ...
主要介绍了Nginx、Apache、Lighttpd禁止目录执行php配置示例,本文给出了单个目录、多个目录的禁止执行PHP的方法,需要的朋友可以参考下
Web服务器:Apache 1.3,Apache 2.x,Nginx或Microsoft IIS PHP版本:PHP 5.6+到PHP 7.4 MySQL 版本:5.1+ 到 5.7 安装并创建数据库 SSH 或 FTP 访问(向您的托管服务询问您的凭据) 在 PHP 配置中,要求您的提供商...
5、访问本机请用http://127.0.0.1/或https://127.0.0.1/ (如果开启SSL) 6、非默认端口,网址为http://127.0.0.1:端口/或https://127.0.0.1:端口/ 7、如果在“扩展功能”中选择使用Memcached,它的端口为:...
5、访问本机请用http://127.0.0.1/或https://127.0.0.1/ (如果开启SSL) 6、非默认端口,网址为http://127.0.0.1:端口/或https://127.0.0.1:端口/ 7、如果在“扩展功能”中选择使用Memcached,它的端口为:11211 8、...
1.4.3 使用phpinfo()确认Apache与PHP 1.4.3 的安装成功 12 1.4.4 Apache的启动与关闭 12 1.4.5 Apache的配置文件httpd.conf与 1.4.5 .htaccess的简介 13 1.4.6 PHP的配置文件php.ini的简介 13 1.4.7 PHP常用参数的...
2.服务器组件/扩展要求:伪静态 PHP扩展开启OPEN_SSL 外网可访问 二、安装程序 1.解压程序文件包 2.将mysql/xiaodai.sql导入数据库中 3.修改web/application/database.php中的数据库连接信息 4.将web/下所有文件上传...
方法一: 在php中,抓取https的网站,提示如下的错误内容: ...apache服务器的话,可以同时启用mod_ssl模块测试。 如果不方便修改服务器配置,可以参考使用如下的函数来解决: 代码示例: <?ph
5、访问本机请用http://127.0.0.1/或https://127.0.0.1/ (如果开启SSL) 6、非默认端口,网址为http://127.0.0.1:端口/或https://127.0.0.1:端口/ 7、如果在“扩展功能”中选择使用Memcached,它的端口为:11211 8、...
5、访问本机请用http://127.0.0.1/或https://127.0.0.1/ (如果开启SSL) 6、非默认端口,网址为http://127.0.0.1:端口/或https://127.0.0.1:端口/ 7、APMServ集成了以下软件: Apache 2.2.3 [HTTP服务器] ...
5、访问本机请用http://127.0.0.1/或https://127.0.0.1/ (如果开启SSL) 6、非默认端口,网址为http://127.0.0.1:端口/或https://127.0.0.1:端口/ 7、如果在“扩展功能”中选择使用Memcached,它的端口为:11211 8、...