To allow real usage of the WASM builds, the library should support X509 certificates support.
Use case:
Running an MLS/CGKA client in a browser, and the application is using X.509 certificates to manage the user identities through an internal PKI. The certificate is accessed for example through the file system web api, or loaded through another mechanism.
Implementation discussion (Optional)
I saw there are traits for the identity provider. My initial plan is to implement a new crate, where I add support similarly to what is done in mls-rs-identity-x509, and use some rust crates compatible with WASM builds to perform the parsing of the certificates.
During my thesis work I have used x509_parser crate. I was thinking around certificates from an internal CA server, and the use case covered would be that the application has locally a copy of the CA certificate for verification of the other client identities. Any thoughts? :)
Description of feature:
To allow real usage of the WASM builds, the library should support X509 certificates support.
Use case:
Running an MLS/CGKA client in a browser, and the application is using X.509 certificates to manage the user identities through an internal PKI. The certificate is accessed for example through the file system web api, or loaded through another mechanism.
Implementation discussion (Optional)
I saw there are traits for the identity provider. My initial plan is to implement a new crate, where I add support similarly to what is done in mls-rs-identity-x509, and use some rust crates compatible with WASM builds to perform the parsing of the certificates. During my thesis work I have used
x509_parsercrate. I was thinking around certificates from an internal CA server, and the use case covered would be that the application has locally a copy of the CA certificate for verification of the other client identities. Any thoughts? :)