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
Rather than just enabling the handling of self-signed certificates by overwriting badCertification, it would be better to give users the option of uploading 1..n custom CAs to accommodate a wider range of scenarios. However, it is also important to retain the ability to overwrite badCertification for maximum flexibility. It is important to note that only one of these options should be enabled at a time.
This will require the usage of a SecurityContext when creating either an HTTP or WS client
The text was updated successfully, but these errors were encountered:
Wouldn't a simple popup letting the user trust the certificate presented by the web server suffice? Obviously while showing all the cert info, including the fingerprint.
Wouldn't a simple popup letting the user trust the certificate presented by the web server suffice? Obviously while showing all the cert info, including the fingerprint.
I will see how I do it.
Probably I will offer both options to tue User. However, the percentage of users to whom these feature is useful is very low anyway.
Rather than just enabling the handling of self-signed certificates by overwriting badCertification, it would be better to give users the option of uploading 1..n custom CAs to accommodate a wider range of scenarios. However, it is also important to retain the ability to overwrite badCertification for maximum flexibility. It is important to note that only one of these options should be enabled at a time.
This will require the usage of a
SecurityContext
when creating either an HTTP or WS clientThe text was updated successfully, but these errors were encountered: