Temporary Workaround for AAD JWT Token Signing Algorithm Issue

[gladjohn]

Fixes #4690

• Because of a bug in Azure Active Directory (AAD) related to handling JWT tokens signed with certain algorithms. This bug prevents the successful utilization of SHA2 and PSS signing algorithms under specific conditions, leading to authentication failures.
• As a temporary measure to circumvent this AAD issue, we have disabled the use of SHA2 and PSS for creating client credentials from certificates. This is achieved by setting IsSha2CredentialSupported to false. This change ensures compatibility with AAD's current capabilities and allows token acquisition to proceed without encountering the identified bug.

Changes proposed in this request

• Modified the IsSha2CredentialSupported property to always return false, bypassing the SHA2 and PSS check for certificate-based client credentials

Testing

• unit tests

Performance impact
none

Documentation

• All relevant documentation is updated.

[neha-bhargava]

Approve with suggestion

[bgavrilMS]

I recommend opening a GH issue to track re-enabling this. Not a bad idea to link the issue from the code.

[gladjohn]

#4695