Hello,

We were wondering if that was possible to generate TLS protocol negotation with WRP request logfiles (or any other way) ? We are interested to know if we have clients internally still using outdated protocols and in which proportion.

That is something easily achievable with Apache/IHS/Nginx/.. but it seems it is a bit more complex with Webseal.

Any advice/experience regarding this ?

Thanks,

Cédric

------------------------------
Cedric Servais
------------------------------

Hi Cédric,

Yes, you can log the TLS protocol used by configuring it in the "request-log-format".
This is the format we use:

request-log-format = %{host}i %h %l %u [%t] "%r" %s %b "%{referer}i" "%{user-agent}i" %T "%F" "%{tagvalue_user_session_id}C" "%{AZN_CRED_QOP_INFO}C"

The TLS protocol is logged with the statement "%{AZN_CRED_QOP_INFO}C", which logs the value from the credential.

From the doc:

# %{attribute}C:
# Attribute from the TAM credential named 'Attribute'

------------------------------
Laurent LA Asselborn
------------------------------

Thank you Laurent,

This is exactly what we werel ooking for :)

------------------------------
Cedric Servais
------------------------------

Original Message:
Sent: Fri November 29, 2019 01:47 AM
From: Laurent LA Asselborn
Subject: TLS Protocol analysis on WRP

Hi Cédric,

Yes, you can log the TLS protocol used by configuring it in the "request-log-format".
This is the format we use:

request-log-format = %{host}i %h %l %u [%t] "%r" %s %b "%{referer}i" "%{user-agent}i" %T "%F" "%{tagvalue_user_session_id}C" "%{AZN_CRED_QOP_INFO}C"

The TLS protocol is logged with the statement "%{AZN_CRED_QOP_INFO}C", which logs the value from the credential.

From the doc:

# %{attribute}C:
# Attribute from the TAM credential named 'Attribute'

------------------------------
Laurent LA Asselborn
------------------------------