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
Currently both implementations of the x509 crypto use the common name field to get the publisher's name. We should use the SAN field.
When moving, we need to make sure we check all the SAN values (as there can be many) when doing authorization. Patrick suggested that for compatibility, we might add the Common Name to the list of SANs for checking purposes though and issue a warning if the CN was not in any SAN values.
The text was updated successfully, but these errors were encountered:
Currently both implementations of the x509 crypto use the common name field to get the publisher's name. We should use the SAN field.
When moving, we need to make sure we check all the SAN values (as there can be many) when doing authorization. Patrick suggested that for compatibility, we might add the Common Name to the list of SANs for checking purposes though and issue a warning if the CN was not in any SAN values.
The text was updated successfully, but these errors were encountered: