fapi-1-baseline client policy enable secure-client-authenticator executor which only allow the following client authentication mode:

• Signed JWT
• Signed JWT with client secret
• Client x509 certificate

Where as Token Introspection Policy only support `Client ID and secret` mode.  The workaround  is configure RH-SSO to only apply fapi-1-baseline profile to certain client type.

However, it is worth investigating whether we need to support an authentication mode other than the "Client ID and secret" for Token Introspection Policy

Update 23/05/2024

After some investigation, the following auth mode should be added:

• private_key_jwt
• client_secret_jwt
• tls_client_auth