Host Token Auth Console Guide

This page provides a clear and complete guide to the Host Token Auth section of the Namirasoft Credential Console. Host Token Auth extends Token Authentication by adding the network location of the target service, so the credential carries both the token and the destination (host and port) in a single record.

What Is Host Token Auth?

Host Token Auth combines a secret token with the network address of the service you want to reach. Use it when an application must authenticate with a token against a specific host and port, such as an internal API or a service behind a fixed address.

 

It is closely related to Token Auth. Choose Token Auth when you only need the token, and Host Token Auth when the credential should also carry the host and port of the target service.

 

Why Secure Token Management Matters

A token works like a key. Any application that holds it can access the service with the permissions the token was granted. Storing a token in application code, configuration files, or developer machines increases the risk of:

 

• Accidental exposure in logs or repositories

 

• Reusing or sharing the same token across many systems

 

• Lack of rotation or auditing

 

• Unauthorized access if the token is leaked

 

A leaked token can give direct access to your service with the same permissions it was granted, making it as sensitive as a password.

 

How Namirasoft Credential Secures Host Token Auth

Namirasoft Credential does not store your token. When you create a Host Token Auth record:

 

• The Token is sent directly to Namirasoft Secret, where it is fully encrypted and stored as a secret value.

 

• Namirasoft Credential only keeps a reference to that encrypted secret, along with the host and port. It never stores the token itself.

 

• When a Namirasoft application needs to connect, Namirasoft Credential retrieves the encrypted token from Namirasoft Secret and assembles the complete credential for the requesting app.

 

This way, Namirasoft Secret handles encryption and storage, while Namirasoft Credential handles secure assembly and controlled delivery.

 

Overview of Host Token Auth Fields and Options

The sections below explain every field visible in the Create and List pages for Host Token Auth. Understanding these fields will help you store your token correctly and manage it with accuracy, security, and confidence.

• ID (String): This is the unique identifier automatically generated by Namirasoft Credential when a Host Token Auth record is created. You do not enter or modify this value. It is used internally for tracking, linking, and referencing the entry across the Namirasoft ecosystem.

• User ID (Namirasoft Account’s ID): This is the unique ID assigned to the Namirasoft Account that created the Host Token Auth record. It serves as a link between the credential and the user who owns or manages it.

• Workspace ID (Namirasoft Workspace’s ID): This refers to a workspace created in the Namirasoft Workspace app, which allows users to organize credentials by project, environment, or team. The workspace name is displayed along with the ID, and it links back to the Namirasoft Workspace app where the workspace details can be viewed.

• Name (String): This is a human friendly label you choose to identify the credential, such as Internal API Token or Monitoring Service. It helps you and your team recognize which credential is which and has no impact on authentication itself.

• Host (String): This is the network address of the service you are authenticating to. Enter it as a public IP address, private IP address, or domain name, exactly as required to reach the service from the Namirasoft environment.

• Port (Integer): This is the network port the target service listens on. Enter the port number configured for the service. Common examples include 80 for HTTP, 443 for HTTPS, and 8080 for alternative HTTP endpoints.

• Token (String): This is the secret token issued by the service you want to connect to. Paste it exactly as the service provided it. For general guidance on obtaining a token, see the Token Auth guide.

• Created At (DateTime): This shows the exact date and time when the Host Token Auth record was first created. This value is automatically set when you create the record and does not change over time.

• Updated At (DateTime): This shows the exact date and time when the Host Token Auth record was most recently modified. It helps you track when the credential was last maintained.