Open GypsyJR777 opened 9 months ago
[Triage] This seems like a bug and I am seeing OpenSearch 1.3 in the stacktrace. We would want to take a quick look at this and see if there is a bug that needs fixing.
Version 1.3 is the versioning that I gave to my build. In fact, version 2.11 is used.
What is the bug? An error occurs when using OpenID and PKCS12:
How can one reproduce the bug? Steps to reproduce the behavior:
config: dynamic: http: anonymous_auth_enabled: false xff: enabled: false authc: openid_auth_domain: description: Authenticate via proxy http_enabled: true transport_enabled: true order: 0 http_authenticator: type: openid challenge: false config: openid_connect_url: my_url openid_connect_idp: enable_ssl: true verify_hostnames: false jwks_uri: my_uri subject_key: preferred_username roles_key: realm_access roles_sub_key: roles authentication_backend: type: noop basic_internal_auth_domain: description: "Authenticate via HTTP Basic against internal users database" http_enabled: true transport_enabled: true order: 1 http_authenticator: type: basic challenge: false authentication_backend: type: intern
plugins.security.ssl.transport: enabled: true keystore_type: PKCS12 truststore_type: PKCS12 keystore_filepath: "/etc/opensearch/certs/self/node.p12" truststore_filepath: "/etc/opensearch/certs/self/node.p12" enabled_protocols: ["TLSv1.2", "TLSv1.3"] enabled_ciphers: ["TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384", "TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256"] enforce_hostname_verification: true