Hi again,
It seems there was a regression between v2.8 and v3.0 on OCSP support for nonce values.
With v2.8, when I executed:
```
New-Object PKI.OCSP.OCSPRequest $cert, $true
```
I got in return `Nonce=$true` and `NonceValue=random_value` but now with 3.0 `Nonce` is still `$true` but `NonceValue` is now empty.
When looking at the source, `NonceValue` indeed does not seem to be initialized anywhere and the private m_encode method was simplified and does not generate a nonce anymore.
Jordan
Comments: Yes, NonceValue property is not updated by the code. However, Nonce value is added to the request object (you can see it in the RawData property of OCSPRequest object). I'll update this part. if you can compile sources, you can add this line at the end of IF clause (line 192): ``` C# NonceValue = listExtensions[listExtensions.Count - 1].Format(false); ```
It seems there was a regression between v2.8 and v3.0 on OCSP support for nonce values.
With v2.8, when I executed:
```
New-Object PKI.OCSP.OCSPRequest $cert, $true
```
I got in return `Nonce=$true` and `NonceValue=random_value` but now with 3.0 `Nonce` is still `$true` but `NonceValue` is now empty.
When looking at the source, `NonceValue` indeed does not seem to be initialized anywhere and the private m_encode method was simplified and does not generate a nonce anymore.
Jordan
Comments: Yes, NonceValue property is not updated by the code. However, Nonce value is added to the request object (you can see it in the RawData property of OCSPRequest object). I'll update this part. if you can compile sources, you can add this line at the end of IF clause (line 192): ``` C# NonceValue = listExtensions[listExtensions.Count - 1].Format(false); ```