HP Jetdirect 610n HP Jetdirect Print Servers - HP Jetdirect and SSL/TLS - Page 84

Subject

Page 84 highlights

Figure 38 - Subject We can se there are several things in the Subject - but the most critical is the Common Name. Here we can see why the browser URL of "https://192.168.0.20" would fail to pass the certificate check but "https://NPIC1F319.example.internal" would not fail. This interesting fact comes as a surprise to most people - the IP address is not usually part of the certificate (Note: IP addresses can be included in certificates). Another way of verifying the name is to use the SubjectAlternateName. To see this, we need to look at the trace of the LDAPS connection shown in Figure 39 - SubjectAltName. 84

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95

84
Figure 38 - Subject
We can se there are several things in the Subject – but the most critical is the Common Name.
Here
we can see why the browser URL of “https://192.168.0.20” would fail to pass the certificate check
but “https://NPIC1F319.example.internal” would not fail. This interesting fact comes as a surprise to
most people – the IP address is not usually part of the certificate (Note: IP addresses can be included
in certificates).
Another way of verifying the name is to use the SubjectAlternateName.
To see this,
we need to look at the trace of the LDAPS connection shown in Figure 39 – SubjectAltName.