You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rename the TLS_CREDENTIAL_SERVER_CERTIFICATE enum to more appropriate name to indicate either Server or client public certificate in the TLS credential subsystem
#87330
Closed
VivekUppunda opened this issue
Mar 19, 2025
· 1 comment
· Fixed by #87341
Currently the enum values defined for tls_credential_type mention TLS_CREDENTIAL_SERVER_CERTIFICATE for public server certificate.
Either an enum value for client certificate be added or rather make the current enum value TLS_CREDENTIAL_SERVER_CERTIFICATE be renamed to a more appropriate name to indicate public certificates in general.
The text was updated successfully, but these errors were encountered:
I agree TLS_CREDENTIAL_SERVER_CERTIFICATE name is unfortunate, it implies server however in reality it doesn't really make difference if the public ceriticate is registered for a client or server device. Even in current codebase we use this credential type to in fact store client certificate (like for example in LwM2M, cc @SeppoTakalo):
Currently the enum values defined for tls_credential_type mention TLS_CREDENTIAL_SERVER_CERTIFICATE for public server certificate.
Either an enum value for client certificate be added or rather make the current enum value TLS_CREDENTIAL_SERVER_CERTIFICATE be renamed to a more appropriate name to indicate public certificates in general.
The text was updated successfully, but these errors were encountered: