Obtener certificado del servidor

Mediante el siguiente comando obtienes el certificado del servidor. De esta manera puedes añadir el certificado, el que lo firma (que debe ir tambien en el certificado), en el fichero cacerts de java.

openssl s_client -showcerts -connect server:port > ./certificadoServidor.cer </dev/null
Anuncios
Obtener certificado del servidor

Crear KeyStores para cliente y servidor

Sigue los siguientes pasos para obtener un keystore para el cliente y el servidor. La contraseña comun a todos los certificados y keysotre sera: 18091980

Ficheros necesarios

Estos ficheros tienen que estar en la misma carpeta donde ejecutemos los comandos

Bibliografia:
wso2 documentation

Comandos

openssl req -x509 -newkey rsa:1024 -keyout cakey.pem -out cacert.pem -config openssl.cnf
Generating a 1024 bit RSA private key
........++++++
..........++++++
writing new private key to 'cakey.pem'
Enter PEM pass phrase:
Verifying - Enter PEM pass phrase:
-----
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [ES]:ES
State or Province Name (full name) [Pontevedra]:P
Locality Name (eg, city) []:V
Organization Name (eg, company) [SA]:T
Organizational Unit Name (eg, section) []:T
Common Name (eg, YOUR name) []:JMP
Email Address []:JMP@JMP.ES
keytool -genkey -alias client -keyalg RSA -keystore client.jks
Escriba la contraseña del almacén de claves:  18091980
Volver a escribir la contraseña nueva: 18091980
¿Cuáles son su nombre y su apellido?
  [Unknown]:  p
¿Cuál es el nombre de su unidad de organización?
  [Unknown]:  t
¿Cuál es el nombre de su organización?
  [Unknown]:  T
¿Cuál es el nombre de su ciudad o localidad?
  [Unknown]:  V
¿Cuál es el nombre de su estado o provincia?
  [Unknown]:  P
¿Cuál es el código de país de dos letras de la unidad?
  [Unknown]:  ES
¿Es correcto CN=p, OU=t, O=T, L=V, ST=P, C=ES?
  [no]:  si

Escriba la contraseña clave para <client>
        (INTRO si es la misma contraseña que la del almacén de claves):

keytool -list -v -keystore client.jks -storepass 18091980
keytool -genkey -alias service -keyalg RSA -keystore service.jks
Escriba la contraseña del almacén de claves:  18091980
Volver a escribir la contraseña nueva: 18091980
¿Cuáles son su nombre y su apellido?
  [Unknown]:  JMP
¿Cuál es el nombre de su unidad de organización?
  [Unknown]:  T
¿Cuál es el nombre de su organización?
  [Unknown]:  T
¿Cuál es el nombre de su ciudad o localidad?
  [Unknown]:  V
¿Cuál es el nombre de su estado o provincia?
  [Unknown]:  P
¿Cuál es el código de país de dos letras de la unidad?
  [Unknown]:  ES
¿Es correcto CN=JMP, OU=T, O=T, L=V, ST=P, C=ES?
  [no]:  si

Escriba la contraseña clave para <service>
        (INTRO si es la misma contraseña que la del almacén de claves):
keytool -certreq -keystore client.jks -storepass 18091980 -alias client -file client.cert.req
keytool -certreq -keystore service.jks -storepass 18091980 -alias service -file service.cert.req
openssl ca -config openssl.cnf -out service.pem -infiles service.cert.req
openssl ca -config openssl.cnf -out client.pem -infiles client.cert.req
openssl x509 -outform DER -in client.pem -out client.cert
openssl x509 -outform DER -in service.pem -out service.cert
openssl x509 -outform DER -in cacert.pem -out cacert.cert
keytool -import -file cacert.cert -keystore service.jks -storepass 18091980 -alias ca
keytool -import -file cacert.cert -keystore client.jks -storepass 18091980 -alias ca
keytool -import -file client.cert -keystore client.jks -storepass 18091980 -alias client
keytool -import -file service.cert -keystore service.jks -storepass 18091980 -alias service
keytool -import -file client.cert -keystore service.jks -storepass 18091980 -alias client
keytool -import -file service.cert -keystore client.jks -storepass 18091980 -alias service

openssl.cnf

#
# OpenSSL example configuration file.
# This is mostly being used for generation of certificate requests.
#

# This definition stops the following lines choking if HOME isn't
# defined.
HOME			= .
RANDFILE		= $ENV::HOME/.rnd

# Extra OBJECT IDENTIFIER info:
#oid_file		= $ENV::HOME/.oid
oid_section		= new_oids

# To use this configuration file with the "-extfile" option of the
# "openssl x509" utility, name here the section containing the
# X.509v3 extensions to use:
# extensions		= 
# (Alternatively, use a configuration file that has only
# X.509v3 extensions in its main [= default] section.)

[ new_oids ]

# We can add new OIDs in here for use by 'ca' and 'req'.
# Add a simple OID like this:
# testoid1=1.2.3.4
# Or use config file substitution like this:
# testoid2=${testoid1}.5.6

####################################################################
[ ca ]
default_ca	= CA_default		# The default ca section

####################################################################
[ CA_default ]

dir		= .			# Where everything is kept
certs		= $dir/certs		# Where the issued certs are kept
crl_dir		= $dir/crl		# Where the issued crl are kept
database	= $dir/index.txt	# database index file.
#unique_subject	= no			# Set to 'no' to allow creation of
					# several ctificates with same subject.
new_certs_dir	= $dir  		# default place for new certs.

certificate	= $dir/cacert.pem 	# The CA certificate
serial		= $dir/serial 		# The current serial number
#crlnumber	= $dir/crlnumber	# the current crl number must be
					# commented out to leave a V1 CRL
crl		= $dir/crl.pem 		# The current CRL
private_key	= $dir/cakey.pem# The private key
RANDFILE	= $dir/private/.rand	# private random number file

x509_extensions	= usr_cert		# The extentions to add to the cert

# Comment out the following two lines for the "traditional"
# (and highly broken) format.
name_opt 	= ca_default		# Subject Name options
cert_opt 	= ca_default		# Certificate field options

# Extension copying option: use with caution.
# copy_extensions = copy

# Extensions to add to a CRL. Note: Netscape communicator chokes on V2 CRLs
# so this is commented out by default to leave a V1 CRL.
# crlnumber must also be commented out to leave a V1 CRL.
# crl_extensions	= crl_ext

default_days	= 365			# how long to certify for
default_crl_days= 30			# how long before next CRL
default_md	= md5			# which md to use.
preserve	= no			# keep passed DN ordering

# A few difference way of specifying how similar the request should look
# For type CA, the listed attributes must be the same, and the optional
# and supplied fields are just that 🙂
policy		= policy_match

# For the CA policy
[ policy_match ]
countryName		= match
stateOrProvinceName	= match
organizationName	= match
organizationalUnitName	= optional
commonName		= supplied
emailAddress		= optional

# For the 'anything' policy
# At this point in time, you must list all acceptable 'object'
# types.
[ policy_anything ]
countryName		= optional
stateOrProvinceName	= optional
localityName		= optional
organizationName	= optional
organizationalUnitName	= optional
commonName		= supplied
emailAddress		= optional

####################################################################
[ req ]
default_bits		= 1024
default_keyfile 	= privkey.pem
distinguished_name	= req_distinguished_name
attributes		= req_attributes
x509_extensions	= v3_ca	# The extentions to add to the self signed cert

# Passwords for private keys if not present they will be prompted for
# input_password = secret
# output_password = secret

# This sets a mask for permitted string types. There are several options. 
# default: PrintableString, T61String, BMPString.
# pkix	 : PrintableString, BMPString.
# utf8only: only UTF8Strings.
# nombstr : PrintableString, T61String (no BMPStrings or UTF8Strings).
# MASK:XXXX a literal mask value.
# WARNING: current versions of Netscape crash on BMPStrings or UTF8Strings
# so use this option with caution!
string_mask = nombstr

# req_extensions = v3_req # The extensions to add to a certificate request

[ req_distinguished_name ]
countryName			= Country Name (2 letter code)
countryName_default		= LK
countryName_min			= 2
countryName_max			= 2

stateOrProvinceName		= State or Province Name (full name)
stateOrProvinceName_default	= Some-State

localityName			= Locality Name (eg, city)

0.organizationName		= Organization Name (eg, company)
0.organizationName_default	= Internet Widgits Pty Ltd

# we can do this but it is not needed normally 🙂
#1.organizationName		= Second Organization Name (eg, company)
#1.organizationName_default	= World Wide Web Pty Ltd

organizationalUnitName		= Organizational Unit Name (eg, section)
#organizationalUnitName_default	=

commonName			= Common Name (eg, YOUR name)
commonName_max			= 64

emailAddress			= Email Address
emailAddress_max		= 64

# SET-ex3			= SET extension number 3

[ req_attributes ]
challengePassword		= A challenge password
challengePassword_min		= 4
challengePassword_max		= 20

unstructuredName		= An optional company name

[ usr_cert ]

# These extensions are added when 'ca' signs a request.

# This goes against PKIX guidelines but some CAs do it and some software
# requires this to avoid interpreting an end user certificate as a CA.

basicConstraints=CA:FALSE

# Here are some examples of the usage of nsCertType. If it is omitted
# the certificate can be used for anything *except* object signing.

# This is OK for an SSL server.
# nsCertType			= server

# For an object signing certificate this would be used.
# nsCertType = objsign

# For normal client use this is typical
# nsCertType = client, email

# and for everything including object signing:
# nsCertType = client, email, objsign

# This is typical in keyUsage for a client certificate.
# keyUsage = nonRepudiation, digitalSignature, keyEncipherment

# This will be displayed in Netscape's comment listbox.
nsComment			= "OpenSSL Generated Certificate"

# PKIX recommendations harmless if included in all certificates.
subjectKeyIdentifier=hash
authorityKeyIdentifier=keyid,issuer:always

# This stuff is for subjectAltName and issuerAltname.
# Import the email address.
# subjectAltName=email:copy
# An alternative to produce certificates that aren't
# deprecated according to PKIX.
# subjectAltName=email:move

# Copy subject details
# issuerAltName=issuer:copy

#nsCaRevocationUrl		= http://www.domain.dom/ca-crl.pem
#nsBaseUrl
#nsRevocationUrl
#nsRenewalUrl
#nsCaPolicyUrl
#nsSslServerName

[ v3_req ]

# Extensions to add to a certificate request

basicConstraints = CA:FALSE
keyUsage = nonRepudiation, digitalSignature, keyEncipherment

[ v3_ca ]


# Extensions for a typical CA


# PKIX recommendation.

subjectKeyIdentifier=hash

authorityKeyIdentifier=keyid:always,issuer:always

# This is what PKIX recommends but some broken software chokes on critical
# extensions.
#basicConstraints = critical,CA:true
# So we do this instead.
basicConstraints = CA:true

# Key usage: this is typical for a CA certificate. However since it will
# prevent it being used as an test self-signed certificate it is best
# left out by default.
# keyUsage = cRLSign, keyCertSign

# Some might want this also
# nsCertType = sslCA, emailCA

# Include email address in subject alt name: another PKIX recommendation
# subjectAltName=email:copy
# Copy issuer details
# issuerAltName=issuer:copy

# DER hex encoding of an extension: beware experts only!
# obj=DER:02:03
# Where 'obj' is a standard or added object
# You can even override a supported extension:
# basicConstraints= critical, DER:30:03:01:01:FF

[ crl_ext ]

# CRL extensions.
# Only issuerAltName and authorityKeyIdentifier make any sense in a CRL.

# issuerAltName=issuer:copy
authorityKeyIdentifier=keyid:always,issuer:always

serial

01

index.txt

empty-vacio-sin_nada
Crear KeyStores para cliente y servidor