> For the complete documentation index, see [llms.txt](https://docs.infraon.io/infraon-infrastructure-management-system/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infraon.io/infraon-infrastructure-management-system/user-guide/infraon-configuration/it-operations/device-credentials.md).

# Device Credentials

The Device Credentials module of Infraon is used by the administrator or authorized user to configure and store Device/Account information such as login credentials (username, password, and other protocol-relevant parameters) for a specific connection protocol. Device Credentials are used in ‘Discovery’ and are mandatory for discovering devices for monitoring and management.

Appropriate device communication protocol must be selected while configuring device credentials to build successful connectivity.

Each device shall be associated with a device credential at the time of discovery. Subsequent monitoring is done using these stored credentials. Should the login credentials (password) change, the administrator must update them to ensure seamless monitoring.

## **Devices and Protocols**

Infraon supports multiple protocols for monitoring and communicating with devices, applications, and cloud environments. The supported protocols include SNMP, SSH, WMI, HTTP, Application, TELNET, FTP, TFTP, SCP, SFTP, NETCONF, Cloud, Custom, CORBA, ODBA, and MERAKI. Refer to the table below for details of each supported protocol.

<table data-header-hidden><thead><tr><th width="117" valign="top"></th><th valign="top"></th><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>Protocols</strong></td><td valign="top"><strong>Description</strong></td><td valign="top"><strong>Supported Devices</strong></td><td valign="top"><strong>Protocol Parameters</strong></td></tr><tr><td valign="top">SNMP</td><td valign="top">SNMP v1 and v2c use community-based security models with Read &#x26; Write Community access. SNMP v3 uses a user-based security model with authentication and encryption. When SNMP v3 is selected, the related parameters must be configured. Refer to the SNMP v3 Parameters section for details.</td><td valign="top">Most network devices, servers, and other SNMP-supported devices.</td><td valign="top">SNMP v1/v2c: Read &#x26; Write Community, Port, Timeout, and Retries. SNMP v3: Username, Security Level, Authentication Type, SNMP v3 Password, Privacy Type, and Privacy Password.</td></tr><tr><td valign="top">SSH</td><td valign="top">SSH (Secure Shell) establishes an encrypted connection with network devices and provides secure CLI-based access.</td><td valign="top">Network devices, Linux/Unix-based servers, and Xen servers.</td><td valign="top">Login Name, Login Prompt, Password, Port, SSH Key File, Connection Command, Timeout, and Retries.</td></tr><tr><td valign="top">WMI</td><td valign="top">WMI (Windows Management Instrumentation) uses the CIM conceptual model to represent and manage various components of Windows devices.</td><td valign="top">Windows Servers.</td><td valign="top">Domain Name/User Name, Password, Authentication Level, Impersonation Level, Timeout, and Retries.</td></tr><tr><td valign="top">HTTP</td><td valign="top">HTTP (Hypertext Transfer Protocol) provides communication and data exchange between systems over web-based interfaces and APIs.</td><td valign="top">vCenter, VMware API, and CUCM Cluster.</td><td valign="top">Username and Password.</td></tr><tr><td valign="top">Application</td><td valign="top">Allows Infraon to connect to and monitor supported applications across databases, web applications, cloud environments, and message brokers. The available configuration parameters vary based on the selected application type.</td><td valign="top">Database: MSSQL, PostgreSQL, MySQL, Oracle, Cassandra, MongoDB, Redis. Web App: Apache Tomcat. Cloud: Docker. Message Broker: Kafka.</td><td valign="top">Database: Enable Authentication, User Name, Password, Port. Web App: Enable Authentication, User Name, Password, Port. Cloud: Connection Type (API, Advanced, API &#x26; Advanced), HTTP Protocol (TCP, HTTP, HTTPS), API Port. Message Broker: Exporter Type (JMX Exporter, Kafka Exporter, Both JMX and Kafka Exporter), JMX Authentication, JMX Remote Port, Kafka Authentication, Kafka Port. Advanced Configurations: Timeout (in seconds) and Retries.</td></tr><tr><td valign="top">TELNET</td><td valign="top">Allows Infraon to establish a TELNET connection with supported network devices for monitoring and communication.</td><td valign="top">Network devices that support TELNET-based access.</td><td valign="top">Customer Name, Description, Port, Login Name, Password, Login Prompt, Enable Password, Enable Prompt, Timeout (in seconds), and Retries.</td></tr><tr><td valign="top">FTP</td><td valign="top">Allows Infraon to establish an FTP connection with supported devices and systems for file transfer and communication.</td><td valign="top">Devices and systems that support FTP-based access.</td><td valign="top">Profile Name, Customer Name, Select Customer or Entity, Description, Port, Login Name, Password, Timeout (in seconds), and Retries.</td></tr><tr><td valign="top">TFTP</td><td valign="top">Allows Infraon to establish a TFTP connection with supported devices and systems for file transfer and communication.</td><td valign="top">Devices and systems that support TFTP-based access.</td><td valign="top">Profile Name, Customer Name, Select Customer or Entity, Description, Port, Login Name, Password, Timeout (in seconds), and Retries.</td></tr><tr><td valign="top">SCP</td><td valign="top">Allows Infraon to establish an SCP connection with supported devices and systems for secure file transfer.</td><td valign="top">Devices and systems that support SCP-based access.</td><td valign="top">Profile Name, Customer Name, Select Customer or Entity, Description, Port, Login Name, Password, Timeout (in seconds), and Retries.</td></tr><tr><td valign="top">SFTP</td><td valign="top">Allows Infraon to establish an SFTP connection with supported devices and systems for secure file transfer.</td><td valign="top">Devices and systems that support SFTP -based access.</td><td valign="top">Profile Name, Customer Name, Select Customer or Entity, Description, Port, Login Name, Password, Timeout (in seconds), and Retries.</td></tr><tr><td valign="top">NETCONF</td><td valign="top">Allows Infraon to establish a NETCONF connection with supported network devices for configuration and monitoring.</td><td valign="top">Network devices that support NETCONF-based communication.</td><td valign="top">Profile Name, Customer Name, Select Customer or Entity, Description, Port, Credential, RSA Private Key, Login Name, Password, Login Prompt, Enable Password, Enable Prompt, Timeout (in seconds), and Retries.</td></tr><tr><td valign="top">Cloud</td><td valign="top">Allows Infraon to connect to and monitor supported cloud platforms using configured cloud credentials.</td><td valign="top">Supported cloud platforms and services.</td><td valign="top">Profile Name, Customer Name, Select Customer or Entity, Description, and Cloud Platform.</td></tr><tr><td valign="top">Custom</td><td valign="top">Allows Infraon to configure a custom protocol connection based on specific monitoring or communication requirements.</td><td valign="top">Devices and systems supporting custom protocol configurations.</td><td valign="top">Profile Name, Customer Name, Select Customer or Entity, Description, Port, Login Name, Password, Timeout (in seconds), and Retries.</td></tr><tr><td valign="top">CORBA</td><td valign="top">Allows Infraon to establish a CORBA-based connection with supported devices and systems for secure file transfer.</td><td valign="top">Systems and applications that support CORBA-based communication.</td><td valign="top">Profile Name, Customer Name, Select Customer or Entity, Description, Port, Login Name, Password, Timeout (in seconds), and Retries.</td></tr><tr><td valign="top">ODBA</td><td valign="top">Allows Infraon to establish an ODBA-based connection with supported systems for monitoring and communication.</td><td valign="top">Systems and applications that support ODBA-based communication.</td><td valign="top">Profile Name, Customer Name, Select Customer or Entity, Description, Port, Login Name, Password, Timeout (in seconds), and Retries.</td></tr><tr><td valign="top">MERAKI</td><td valign="top">Allows Infraon to connect to and monitor supported Cisco Meraki environments using API-based authentication.</td><td valign="top">Cisco Meraki devices and environments.</td><td valign="top">Profile Name, Description, and API Key.</td></tr></tbody></table>

Click 'Test and Save' to test the credentials for authenticity before saving and proceeding to discovery.

## **What you see on the screen**

The device credentials page can be used to add, edit, and delete device credentials for SNMP, SSH, WMI, and HTTP.

Using the respective icon, the device credential view can be toggled between the card view and the list view.

Device Credentials | **Field Description**

<table data-header-hidden><thead><tr><th width="115.111083984375"></th><th width="113.888916015625"></th><th></th></tr></thead><tbody><tr><td><strong>Label</strong></td><td><strong>Action</strong></td><td><strong>Description/Example</strong></td></tr><tr><td>Search</td><td>Search</td><td>Allows users to search for specific device credentials.</td></tr><tr><td>Filter</td><td>Filter</td><td>Allows users to filter the credential list based on the available criteria.</td></tr><tr><td>List View</td><td>View Options</td><td>Displays the configured device credentials in a tabular format.</td></tr><tr><td>Grid View</td><td>View Options</td><td>Displays the configured device credentials in a grid or card format.</td></tr><tr><td>Name</td><td>Basic Details</td><td>Displays the name of the configured device credential. Example: Cisco EOX Credentials, Docker, Kubernetes, Oracle.</td></tr><tr><td>Protocol</td><td>Basic Details</td><td>Displays the protocol associated with the credential. Example: Custom, Application, HTTP, Kubernetes, Meraki, Cloud.</td></tr><tr><td>Description</td><td>Basic Details</td><td>Displays the description and purpose of the configured credential, where available.</td></tr><tr><td>No. of Nodes</td><td>Basic Details</td><td>Displays the number of nodes associated with the respective credential.</td></tr><tr><td>Action</td><td>Edit / Delete</td><td>Allows users to modify and delete the configuration details of an existing device credential.</td></tr><tr><td>Discovery</td><td>Discovery</td><td>Allows users to initiate device discovery using the configured credentials. <a href="/infraon-infrastructure-management-system/user-guide/infraon-configuration/it-operations/discovery.md">Click here</a> to know more. </td></tr></tbody></table>

<figure><img src="https://4009867068-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYX6NgONgHKMA5rMSqwFI%2Fuploads%2FrDpaFcd0cQZo4YXfz5Is%2Fimage.png?alt=media&amp;token=7afa6f85-425a-436a-9099-c1f8b5e1f7cf" alt=""><figcaption></figcaption></figure>

## **Instructions to 'Add Device Credential'**

* Go to Infraon Configuration -> IT Operations-> Device Credentials.
* Click on 'Add' and select 'Protocol' as desired.

There are two tabs on the 'Add Credential' page. Refer to the table for information.

Few fields vary based on the protocol selected. Refer to the 'Description' column for details.

Add **| Configuration**

<table data-header-hidden><thead><tr><th width="167.55560302734375" valign="top"></th><th width="262.111083984375" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>Label</strong></td><td valign="top"><strong>Action</strong></td><td valign="top"><strong>Description/Example</strong></td></tr><tr><td valign="top">Profile Name*</td><td valign="top">Add a name for the credential.</td><td valign="top">Applicable for all protocols. A name is usually used as an identifier.</td></tr><tr><td valign="top">Description</td><td valign="top">Add a brief description of the profile.</td><td valign="top">Applicable for all protocols.</td></tr><tr><td valign="top">Port</td><td valign="top">The default value is auto-populated. This, however, can be changed.</td><td valign="top">Applicable for SNMP and SSH.</td></tr><tr><td valign="top">Timeout (Seconds)</td><td valign="top">The default value is auto-populated. This, however, can be changed.</td><td valign="top"><p>Applicable for all protocols.</p><p>The number of seconds post which Infraon stops attempting to reach the device.</p></td></tr><tr><td valign="top">Retries</td><td valign="top">The default value is auto-populated. This, however, can be changed.</td><td valign="top"><p>Applicable for all protocols.</p><p>The number of instances Infraon tries to reach the device.</p></td></tr><tr><td valign="top">For SNMP</td><td valign="top">Select the SNMP version, as applicable. Based on the selection, additional fields appear.</td><td valign="top"><p>Applicable for SNMP only</p><p>V1 - Read Community*, Write Community</p><p>v2c - Read Community*, Write Community, Scan Requests</p><p>v3 - User Name, Context Name, Security Level, Authentication Protocol, Authentication Password*, Privacy Protocol, Privacy Password*, Scan Requests</p></td></tr><tr><td valign="top">For SSH</td><td valign="top">Select between Credential, and Public Key, as applicable. Based on the selection, additional fields appear.</td><td valign="top"><p>Applicable for SSH only</p><p>Credential - Login Name*, Password, Login Prompt, Enable Password, Enable Prompt</p><p>Public Key - Hash Key*</p><p>v3 - User Name, Context Name, Security Level, Authentication Protocol, Authentication Password*, Privacy Protocol, Privacy Password*, Scan Requests.</p></td></tr><tr><td valign="top">For WMI</td><td valign="top">Select between WMIC, and WinRM, as applicable. Based on the selection, additional fields appear.</td><td valign="top"><p>Applicable for WMI only</p><p>Login Name* and Password* are standard fields for WMIC and WinRM.</p><p>WMIC - Authentication</p><p>WinRM - WinRM Authentication Level, Protocol, WinRM Port, WinRM Certificate Validation, WinRM Certificate File, WinRM Public Key.</p></td></tr><tr><td valign="top">For HTTP</td><td valign="top">Select between HTTP, and HTTPS, as applicable. Based on the selection, additional fields appear.</td><td valign="top"><p>Applicable for HTTP/HTTPS only</p><p>HTTP - Username*, Password*</p><p>HTTPS - Username*, Password*,</p></td></tr><tr><td valign="top">For Application</td><td valign="top">Select the application type and configure the required connection and authentication details.</td><td valign="top">Applicable for Application only. The available fields depend on the selected application type: Database – Enable Authentication, User Name, Password, Port. Web App – Enable Authentication, User Name, Password, Port. Cloud – Connection Type, HTTP Protocol, API Port. Message Broker – Exporter Type, JMX Authentication, JMX Remote Port, Kafka Authentication, Kafka Port.</td></tr><tr><td valign="top"><p>For TELNET</p><p> </p></td><td valign="top">Configure the TELNET connection and authentication details</td><td valign="top">Applicable for TELNET only. Port, Login Name, Password, Login Prompt, Enable Password, Enable Prompt, Timeout (in seconds), and Retries.</td></tr><tr><td valign="top">For FTP</td><td valign="top">Configure the FTP connection and authentication details.</td><td valign="top">Applicable for FTP only. Port, Login Name, Password, Timeout (in seconds), and Retries.</td></tr><tr><td valign="top">For TFTP</td><td valign="top">Configure the TFTP connection and authentication details.</td><td valign="top">Applicable for TFTP only. Port, Login Name, Password, Timeout (in seconds), and Retries.</td></tr><tr><td valign="top">For SCP</td><td valign="top">Configure the SCP connection and authentication details.</td><td valign="top">Applicable for SCP only. Port, Login Name, Password, Timeout (in seconds), and Retries.</td></tr><tr><td valign="top">For SFTP</td><td valign="top">Configure the SFTP connection and authentication details.</td><td valign="top">Applicable for SFTP only. Port, Login Name, Password, Timeout (in seconds), and Retries.</td></tr><tr><td valign="top">For NETCONF</td><td valign="top">Configure the NETCONF connection and authentication details.</td><td valign="top">Applicable for NETCONF only. Port, Credential, RSA Private Key, Login Name, Password, Login Prompt, Enable Password, Enable Prompt, Timeout (in seconds), and Retries.</td></tr><tr><td valign="top">For Cloud</td><td valign="top">Select the cloud platform for the connection.</td><td valign="top">Applicable for Cloud only. Cloud Platform specifies the cloud platform to be used for the connection.</td></tr><tr><td valign="top">For MERAKI</td><td valign="top">Configure the API authentication details.</td><td valign="top">Applicable for MERAKI only. API Key is used to authenticate the connection with the Meraki environment.</td></tr><tr><td valign="top">For ODBA</td><td valign="top">Configure the ODBA connection and authentication details.</td><td valign="top">Applicable for ODBA only. Port, Login Name, Password, Timeout (in seconds), and Retries.</td></tr><tr><td valign="top">For CORBA</td><td valign="top">Configure the CORBA connection and authentication details.</td><td valign="top">Applicable for CORBA only. Port, Login Name, Password, Timeout (in seconds), and Retries.</td></tr><tr><td valign="top">For Custom</td><td valign="top">Configure the custom protocol connection and authentication details.</td><td valign="top">Applicable for Custom only. Port, Login Name, Password, Timeout (in seconds), and Retries.</td></tr></tbody></table>

Once all the parameters are defined, click ‘Submit’ to save the credentials.

The Link Credential page allows users to link a different protocol credential to the current profile. After completing the Configuration section, click **Next** to open the **Link Credential** page.

Add | **Link Credential**

<table data-header-hidden><thead><tr><th width="146.22222900390625" valign="top"></th><th width="201.00006103515625" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>Label</strong></td><td valign="top"><strong>Action</strong></td><td valign="top"><strong>Description/Example</strong></td></tr><tr><td valign="top">Select Protocol</td><td valign="top">Select a protocol from the list.</td><td valign="top">Allows users to select the protocol credential to be linked to the current profile. The available protocols are SNMP, SSH, WMI, and HTTP.</td></tr><tr><td valign="top">Select Profile</td><td valign="top">Select a credential profile.</td><td valign="top">Allows users to select the existing credential profile associated with the selected protocol.</td></tr></tbody></table>

{% hint style="info" %}
Access the **Link Credential** page by clicking **Next** from the **Configuration** section.
{% endhint %}

Configuration | **Test**

<table data-header-hidden><thead><tr><th width="128.44439697265625" valign="top"></th><th width="248.22222900390625" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Label</td><td valign="top">Action</td><td valign="top">Description/Example</td></tr><tr><td valign="top">IP Address*</td><td valign="top">Add an IP address to test the credentials.</td><td valign="top">Applicable for all protocols.</td></tr><tr><td valign="top">Agent*</td><td valign="top">Select an agent to test.</td><td valign="top">Applicable for all protocols</td></tr></tbody></table>

Click '**Test**.'

Saved credentials can be edited or deleted by using the respective action icons.

{% hint style="info" %}
Credentials must be correct to ensure seamless discovery.
{% endhint %}
