Andreas Steffen
7c5a2974b9
For documentation purposes the new folders ikev1-algs, ikev2-algs, ikev1-multi-ca and ikev2-multi-ca have been created. Most of the test cases have now been converted to the vici interface. The remaining legacy stroke scenarios yet to be converted have been put into the ikev2-stroke-bye folder. For documentation purposes some legacy stroke scenarios will be kept in the ikev1-stroke, ikev2-stroke and ipv6-stroke folders.
17 lines
1019 B
Plaintext
17 lines
1019 B
Plaintext
This scenario tests the <b>revocation = ifuri</b> option which enforces a
|
|
strict CRL policy for a given CA if at least one OCSP or CRL URI is known
|
|
for this CA at the time of the certificate trust path verification.
|
|
On the gateway <b>moon</b> two different Intermediate CAs control the access
|
|
to the hosts <b>alice</b> and <b>venus</b>. Access to <b>alice</b> is granted
|
|
to users presenting a certificate issued by the Research CA whereas <b>venus</b>
|
|
can only be reached with a certificate issued by the Sales CA.
|
|
<p/>
|
|
The roadwarrior <b>carol</b> has a certificate from the Research CA which does not
|
|
contain any URIs. Therefore a strict CRL policy is <b>not</b> enforced and the
|
|
connection setup succeeds, although the certificate status is unknown.
|
|
<p/>
|
|
The roadwarrior <b>dave</b> has a certificate from the Sales CA which contains
|
|
a single OCSP URI but which is not resolvable. Thus because of the known URI
|
|
a strict CRL policy is enforced and the unknown certificate status causes the
|
|
connection setup to fail.
|