lib/client.js
function checkBasicSupport(client, metadata, properties) {
  try {
    const supported = client.issuer.token_endpoint_auth_methods_supported;
    if (!supported.includes(properties.token_endpoint_auth_method)) {
      if (supported.includes('client_secret_post')) {
        properties.token_endpoint_auth_method = 'client_secret_post';
      }
    }
  } catch (err) {}
}
function checkBasicSupport(client, metadata, properties) {
  try {
    const supported = client.issuer.token_endpoint_auth_methods_supported;
    if (!supported.includes(properties.token_endpoint_auth_method)) {
      if (supported.includes('client_secret_post')) {
        properties.token_endpoint_auth_method = 'client_secret_post';
      }
    }
  } catch (err) {}
}
function checkBasicSupport ( client , metadata , properties ) { try { const supported = client . issuer . token_endpoint_auth_methods_supported ; if ( ! supported . includes ( properties . token_endpoint_auth_method ) ) { if ( supported . includes ( 'client_secret_post' ) ) { properties . token_endpoint_auth_method = 'client_secret_post' ; } } } catch ( err ) { } }
if an OP doesnt support client_secret_basic but supports client_secret_post, use it instead this is in place to take care of most common pitfalls when first using discovered Issuers without the support for default values defined by Discovery 1.0
if an OP doesnt support client_secret_basic but supports client_secret_post use it instead this is in place to take care of most common pitfalls when first using discovered Issuers without the support for default values defined by Discovery 1 . 0