User Guide Functional Overview Requirements Architecture System Installation NetEye Additional Components Installation Setup The neteye Command Director NetEye Self Monitoring Tornado Business Service Monitoring IT Operation Analytics - Telemetry Geo Maps NagVis Audit Log Shutdown Manager Reporting ntopng Visual Monitoring with Alyvix Elastic Stack IT Operations (Command Orchestrator) Asset Management Service Level Management Cyber Threat Intelligence - SATAYO NetEye Update & Upgrade How To NetEye Extension Packs Troubleshooting Security Policy Glossary
module icon Troubleshooting
Setup Configure swappiness Restarting Stopped Services Enable stack traces in web UI How to access standard logs Director does not deploy when services assigned to a host have the same name How to enable/disable debug logging Activate Debug Logging for Tornado Modules/Services do not start Sync Rule fails when trying to recreate Icinga object How to disable InfluxDB query logging Managing an Elasticsearch Cluster with a Full Disk Some logs are not indexed in Elasticsearch Elasticsearch is not functioning properly Reporting: Error when opening a report Debugging Logstash file input filter
NetEye Update & Upgrade How To NetEye Extension Packs Troubleshooting Security Policy Glossary Introduction to NetEye Monitoring Business Service Monitoring IT Operation Analytics Visualization Network Visibility Log Management & Security Orchestrated Datacenter Shutdown Application Performance Monitoring User Experience Service Management Service Level Management & Reporting Requirements for a Node Cluster Requirements and Best Practices NetEye Satellite Requirements TCP and UDP Ports Requirements Additional Software Installation Introduction Single Node Cluster NetEye Master Master-Satellite Architecture Underlying Operating System Acquiring NetEye ISO Image Installing ISO Image Single Nodes and Satellites Cluster Nodes Configuration of Tenants Satellite Nodes Only Nodes behind a Proxy Additional NetEye Components Single Node Cluster Node Satellites Nodes only Verify if a module is running correctly Accessing the New Module Cluster Satellite Security Identity and Access Management External Identity Providers Configure federated LDAP/AD Emergency Reset of Keycloak Configuration Advanced Configuration Authorization Resources Tuning Advanced Topics Basic Concepts & Usage Advanced Topics Monitoring Environment Templates Monitored Objects Import Monitored Objects Data Fields Deployment Icinga 2 Agents Configuration Baskets Dashboard Monitoring Status VMD Permissions Notifications Jobs API Configuring Icinga Monitoring Retention Policy NetEye Self Monitoring 3b Concepts Collecting Events Add a Filter Node WHERE Conditions Iterating over Event fields Retrieving Payload of an Event Extract Variables Create a Rule Tornado Actions Test your Configuration Export and Import Configuration Example Under the hood Development Retry Strategy Configuration Thread Pool Configuration API Reference Configure a new Business Process Create your first Business Process Node Importing Processes Operators The ITOA Module Configuring User Permissions Telegraf Metrics in NetEye Telegraf Configuration Telegraf on Monitored Hosts Visualizing Dashboards Customizing Performance Graph The NetEye Geo Map Visualizer Map Viewer Configuring Geo Maps NagVis 3b Audit Log 3b Overview Shutdown Manager user Shutdown Manager GUI Shutdown Commands Advanced Topics Overview User Role Management Cube Use Cases ntopng and NetEye Integration Permissions Retention Advanced Topics Overview User Roles Nodes Test Cases Dashboard Use Cases Overview Architecture Authorization Elasticsearch Overview Enabling El Proxy Sending custom logs to El Proxy Configuration files Commands Elasticsearch Templates and Retentions El Proxy DLQ Blockchain Verification Handling Blockchain Corruptions El Proxy Metrics El Proxy Security El Proxy REST Endpoints Agents Logstash Elastic APM Elastic RUM Log Manager - Deprecated Overview Authorization in the Command Orchestrator Module Configuring CLI Commands Executing Commands Overview Permissions Installation Single Tenancy Multitenancy Communication through a Satellite Asset collection methods Display asset information in monitoring host page Overview Customers Availability Event Adjustment Outages Resource Advanced Topics Introduction Getting Started SATAYO Items Settings Managed Service Mitre Attack Coverage Changelog Before you start Update Procedure Single Node Upgrade from 4.41 to 4.42 Cluster Upgrade from 4.41 to 4.42 Satellite Upgrade from 4.41 to 4.42 DPO machine Upgrade from 4.41 to 4.42 Create a mirror of the RPM repository Sprint Releases Feature Troubleshooting Tornado Networking Service Management - Incident Response IT Operation Analytics - Telemetry Identity Provider (IdP) Configuration Introduction to NEP Getting Started with NEPs Online Resources Obtaining NEP Insights Available Packages Advanced Topics Upgrade to NetEye 4.31 Setup Configure swappiness Restarting Stopped Services Enable stack traces in web UI How to access standard logs Director does not deploy when services assigned to a host have the same name How to enable/disable debug logging Activate Debug Logging for Tornado Modules/Services do not start Sync Rule fails when trying to recreate Icinga object How to disable InfluxDB query logging Managing an Elasticsearch Cluster with a Full Disk Some logs are not indexed in Elasticsearch Elasticsearch is not functioning properly Reporting: Error when opening a report Debugging Logstash file input filter Bugfix Policy Reporting Vulnerabilities Glossary 3b

Setup

Authentication

Generic Keycloak problems resolution with logs

If you are experiencing problems with the authentication, IDP integration, errors printed out in the web UI of Keycloak, etc, you can check the Keycloak logs to understand what is happening. Keycloak logs pretty much everything that is happening and can be very useful to understand what is going wrong.

The activation of the debug log can be done by setting log-level=DEBUG in the /neteye/shared/keycloak/conf/keycloak.conf file and then restarting the service. To restart the service run systemctl restart keycloak in single node installations and pcs resource restart keycloak in cluster installations.

Email already exists (multiple accounts with the same email)

If during the login process you receive an error message like

Email already exists

it means that there are multiple accounts with the same email.

The same problem can be found by analyzing the Keycloak logs by finding a message like

Failed during import user from LDAP: org.keycloak.models.ModelDuplicateException: Can't import user 'USER1' from LDAP because email 'user1@example.com' already exists in Keycloak. Existing user with this email is 'USER2'

There are two ways to solve this problem:

  1. Change the email of the user in the LDAP/AD server: This is the best solution because it will prevent the problem from happening again. The email is a unique field in Keycloak, so it is not possible to have multiple accounts with the same email. After changing the email in the LDAP server, you can trigger a synchronization in Keycloak to update the user information.

  2. Allow duplicate emails in Keycloak: This is a solution that can be used if you can’t change the email in the LDAP/AD server. To allow duplicate emails in Keycloak, in Realm settings / Login, disable the Login with email option and enable the Duplicate emails option. This will allow multiple accounts with the same email in Keycloak, with the downside that it will not to be possible to login with emails anymore, but only usernames.

The migrated LDAP connection doesn’t work in Keycloak

When this problem occurs, you can check out the logs of Keycloak to understand what is happening. To do this, you should raise the log level of the Keycloak service as described in the section above.

This can be done by setting log-level=DEBUG in the /neteye/shared/keycloak/conf/keycloak.conf file and then restarting the service. To restart the service run systemctl restart keycloak in single node installations and pcs resource restart keycloak in cluster installations.

After that, you can read the logs in the service journal, opened with the command journalctl -fu keycloak. In cluster installations be sure to check the logs of the node where the Keycloak service is running. Keeping the terminal opened, navigate to the Keycloak admin console with your browser. You can can find more details at in this section.

Once logged in the Keycloak admin console, you can test the LDAP configuration. From the left menu, navigate to User federation and click on the LDAP provider that is not working. In the Connection and authentication settings, you can find the Test connection button, that will allow you to see the logs in the terminal to understand what is happening. If the test connection succeeds, you can also try out the Test authentication button.

Blog Online Demo Training
Contact Us
© 2025, Wuerth Phoenix S.r.l.
VAT ID 01054690217
Privacy Cookies