Hi, we are using version 2.7 and saml, and from time to time we are getting 400 invalid request id
this is our config:
_meta:
type: “config”
config_version: 2
config:
dynamic:
authc:
basic_internal_auth_domain:
http_enabled: true
transport_enabled: true
order: 0
http_authenticator:
type: basic
challenge: false
authentication_backend:
type: internal
saml_auth_domain:
http_enabled: true
transport_enabled: false
order: 1
http_authenticator:
type: saml
challenge: true
config:
idp:
metadata_url: {{ metadata_url }}
entity_id: {{ entity_id }}
sp:
entity_id: kibana-saml
kibana_url: {{ kibana_url }}
roles_key: Role
exchange_key: {{ exchange_key }}
jwt:
expiry: AUTO+10080
authentication_backend:
type: noop
please any idea
Eugene7
2
Hi @taltsafrir ,
Could you please share opensearch_dashboards.yml
?
Also, could you please send a URL where you found the following configuration?
server.name: "{{ opensearch_dashboards_name }}"
server.host: "0.0.0.0"
data_source.enabled: true
opensearch.hosts:
- https://{{ node }}:9200
{% endfor %}
opensearch.requestHeadersAllowlist: [ authorization,securitytenant ]
opensearch.ssl.verificationMode: certificate
#opensearch.ssl.verificationMode: none
server.ssl.enabled: true
server.ssl.certificate: client.pem
server.ssl.key: client-key.pem
opensearch.ssl.certificateAuthorities: root-ca.pem
server.xsrf.allowlist: ["/_opendistro/_security/saml/acs/idpinitiated", "/_opendistro/_security/saml/acs", "/_opendistro/_security/saml/logout"]
opensearch_security.multitenancy.enabled: true
opensearch_security.multitenancy.tenants.preferred: ["Global"]
opensearch_security.cookie.secure: true
opensearch_security.cookie.ttl: 86400000
opensearch_security.session.ttl: 86400000
opensearch_security.session.keepalive: true
opensearch_security.auth.type: 'saml'
about the config, I found it in one of the threads in the forum
Where did you receive the 400 error message? Do you see any error messages in the OpenSearch or OpenSearch Dashboards logs?
I saw error 400 on opensearch dashboards log but nothing else
we receive those errors on chrome
Hi, I am also facing the same issue were you able to resolve it on Chrome? weirdly it works fine for me on Microsoft Edge
no, it’s not resolved
but we are not working with microsoft edge