When you start Skedler Reports as Kibana plugin and if you come across the below error,
Error in accessing ES Client - Authentication Exception :: {“path”:”/_nodes’,’query”; {},”statuscode”:,”response”:Authentication finally failed”}
[ERROR] [reports_4.11.0] - Skedler Plugin - Error in accessing ES Client - { Error: Authentication Exception
at respond (/opt/skedler/node_modules/elasticsearch/src/lib/transport.js:315:23)
at checkRespForFailure (/opt/skedler/node_modules/elasticsearch/src/lib/transport.js:274:13)
at HttpConnector.<anonymous> (/opt/skedler/node_modules/elasticsearch/src/lib/connectors/http.js:159:7)
at IncomingMessage.bound (/opt/skedler/node_modules/elasticsearch/node_modules/lodash/dist/lodash.js:729:21)
at IncomingMessage.emit (events.js:194:15)
at endReadableNT (_stream_readable.js:1103:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
status: 401,
displayName: 'AuthenticationException',
message: 'Authentication Exception',
path: '/_nodes',
query: {},
body: undefined,
statusCode: 401,
response: 'Authentication finally failed',
toString: [Function],
toJSON: [Function] }
Do the following to resolve this issue,
Please check whether the Skedler admin credentials which are configured in the skedler_reports.yml and reporting.yml are the same. If they are not configured, please configure them to resolve the issue.
However, we support the security plugins like X-pack, open distro, search guard, Nginx, and security onion. SAML, LDAP, Azure ADFS is still under progress and currently, we don’t support them.