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 How To
Tornado Networking Service Management - Incident Response IT Operation Analytics - Telemetry Identity Provider (IdP) Configuration
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

Identity Provider (IdP) Configuration

How To setup Microsoft Active Directory Federation Services (MSADFS) in Keycloak with SAML

This guide explains how to configure Microsoft Active Directory Federation Services (MSADFS) as an Identity Provider (IdP) in Keycloak.

Note

This guides assumes that you have access to the Authentication Admin Console and to your MSADFS console.

Note

You need the federation metadata endpoint URL from your MSADFS console. This URL is used to configure the IdP in Keycloak. Usually, the URL is in the format https://<ADFS_HOST>/FederationMetadata/2007-06/FederationMetadata.xml.

Keycloak Configuration

To configure MSADFS as an IdP in Keycloak, you need to go to the Authentication Admin Console and follow these steps:

  • Go to Identity Providers > Add provider > SAML v2.0.

  • Select an alias for the IdP, for example, MSADFS.

  • Insert the federation metadata endpoint URL from your MSADFS console

  • Click on Save.

Note

Following configurations depends on your MSADFS setup. Please refer to your MSADFS documentation for more information. We recommend to set the following configuration parameters that usually work for most setups

  • NameID Policy Format: Unspecified

  • Want AuthnRequests Signed: TRUE

  • SAML Signature Key Name: CERT_SUBJECT

  • Validate Signature: TRUE

  • Use metadata descriptor URL: TRUE

Now we need to create a new mapper in Mappers with the following settings:

  • Name: username

  • Mapper Type: Attribute Importer

  • Attribute Name: http://schemas.microsoft.com/2012/12/certificatecontext/field/subjectname

  • User Attribute Name: username

Note

The Attribute Name MAY be different for you, referer to your claim names, in this configuration we use the subject name.

At this point, you can complete the rest of the configuration with common settings, please refer to Common IdP configuration and IdP After Setting up configuration sections to find all the information you need.

MSADFS Configuration

Now you need to configure the Keycloak as a relying party in your MSADFS console. You can follow this guide to add a new relying party in your MSADFS console:

Note

You can use the federation metadata URL from Keycloak to automatically configure the ADFS relying party. You can find it in the provider settings in the Identity Providers section.

Warning

If the metadata URL is not working, you can download the XML from keycloak at the same federation metadata URL and upload it in the MSADFS console.

After you have configured the relying party, you need to add the claim rules to map the user attributes to the SAML token. You can follow this guide to map your LDAP attributes to SAML attributes.

At the very minimum you need to map the username to the SAML token. In our how-to guide, we have mapped the sAMAccountName field in MSADFS as Subject Name, but it can be mapped depending on your setup.

LDAP Attribute

Outgoing Claim Type

sAMAccountName

Subject Name

Note

Remember to complete the rest of the configuration with common settings, please refer to Common IdP configuration and IdP After Setting up configuration sections to find all the information you need.

How To setup FortiAuthenticator in Keycloak with OIDC

This guide explains how to configure FortiAuthenticator (6.6.2) as an Identity Provider (IdP) in Keycloak.

Note

This guide assumes that you have access to the Authentication Admin Console and to your FortiAuthenticator console.

Note

You need the discovery info endpoint URL from your FortiAuthenticator instance. This URL is used to configure the IdP auto-discovery in Keycloak. Following this guide the URL should be https://<FORTIAUTHENTICATOR_HOST>/api/v1/oauth/.well-known/openid-configuration/.

Client and Keycloak Configuration

To configure FortiAuthenticator as an IdP in Keycloak, you need to go to the Authentication Admin Console and follow these steps:

  • Go to Identity Providers > Add provider > OpenID Connect v1.0.

  • Select an alias for the IdP, for example, Fortinet and copy the redirect URL.

  • Open a new page and go to your FortiAuthenticator console.

Next, we need to create a new OIDC client in FortiAuthenticator, you can follow this guide to create a new client. Feel free to configure the settings as needed, however, it is recommended to use the following parameters:

Field

Value

Client type

confidential

Authorization grant types

Authorization Code

Scopes

openid. You can read this guide to create scopes

Claims

With openid you need to add at least one claim: the username. You can read this guide to create claims

Redirect URIs

The redirect URL from Keycloak

Note

Other parameters have to be configured depending on your own setup.

Now you can copy the client id and the secret, and put them in the Keycloak configuration. After that, simply click on Save.

Next step is adding a new mapper in Mappers with the following settings:

  • Name: username

  • Mapper Type: Attribute Importer

  • Attribute Name: **username**

  • User Attribute Name: username

Note

The Attribute Name MAY be different for you, refer to your claim names to make sure. In this configuration we used username.

At this point, you can complete the rest of the configuration with common settings, please refer to Common IdP configuration and IdP After Setting up configuration sections to find all the information you need.

How To setup PingFederate in Keycloak with OIDC

This guide explains how to configure PingFederate as an Identity Provider (IdP) in Keycloak.

Note

This guide assumes that you have access to the Authentication Admin Console and to your PingFederate instance.

Note

You need the discovery info endpoint URL from your PingFederate instance. This URL is used to configure the IdP auto-discovery in Keycloak. Following this guide the URL should be https://<PINGFEDERATE_HOST>/.well-known/openid-configuration.

Client and Keycloak Configuration

To configure PingFederate as an IdP in Keycloak, you need to go to the Authentication Admin Console and follow these steps:

  • Go to Identity Providers > Add provider > OpenID Connect v1.0.

  • Select an alias for the IdP, for example, PingFederate and copy the redirect URL.

  • Open a new page and go to your PingFederate console.

Next, we need to create a new OIDC client in PingFederate, you can follow this guide to create a new client. Feel free to configure the settings as needed, however, it is recommended to use the following parameters:

Field

Value

Client Authentication

Client Secret

Allowed Grant Types

Select at least Authorization Code

Scopes

At least openid and profile

Redirection URI

The redirect URL from Keycloak

Note

Other parameters have to be configured depending on your own setup.

Now you can copy the client id and the secret, and put them in the Keycloak configuration. After that, simply click on Save.

Next step is adding a new mapper in Mappers with the following settings:

  • Name: username

  • Mapper Type: Attribute Importer

  • Attribute Name: sub

  • User Attribute Name: username

Note

The Attribute Name MAY be different for you, refer to your claim names to make sure. In this configuration we used sub that is the default with profile scope

At this point, you can complete the rest of the configuration with common settings, please refer to Common IdP configuration and IdP After Setting up configuration sections to find all the information you need.

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