Skip to content

Conversation

@pdamoune
Copy link
Member

Proposed changes

  • Implement the X509V3ExtensionsType fields on X509Certificate

Related issues

Checklist

  • I consider the submitted work as finished
  • I tested the code for its functionality
  • I wrote test cases for the relevant uses case
  • I added/update the relevant documentation (either on github or on notion)
  • Where necessary I refactored code to improve the overall quality

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

@pdamoune pdamoune self-assigned this Oct 27, 2025
@pdamoune pdamoune added the filigran team use to identify PR from the Filigran team label Oct 27, 2025
@pdamoune pdamoune force-pushed the issue/1023-missing-x509certificate-fields-mapping-on-creation branch from b9fcf1b to 13f031d Compare October 27, 2025 10:22
@labo-flg
Copy link
Member

Could you please add/update the test suite with these fields ?

@pdamoune pdamoune force-pushed the issue/1023-missing-x509certificate-fields-mapping-on-creation branch 7 times, most recently from 68c181f to 64b49a4 Compare November 3, 2025 14:21
@pdamoune pdamoune force-pushed the issue/1023-missing-x509certificate-fields-mapping-on-creation branch 8 times, most recently from 269c279 to 0c025e8 Compare November 7, 2025 10:43
@pdamoune pdamoune force-pushed the issue/1023-missing-x509certificate-fields-mapping-on-creation branch from 0c025e8 to 5793e69 Compare November 7, 2025 10:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

filigran team use to identify PR from the Filigran team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[client] Missing the X509V3ExtensionsType fields on X509Certificate

3 participants