Basic Auth Console Guide

This page provides a clear and complete guide to the Basic Auth section of the Namirasoft Credential Console. It explains what Basic Authentication is, how Namirasoft Credential stores it securely, and how it can be used across Namirasoft applications.

What Is Basic Authentication?

Basic Authentication is a widely used method for verifying identity by sending a username and password with each request. Many services, APIs, webhooks, and integrations still rely on Basic Auth because it is simple, reliable, and widely supported.

 

Despite its simplicity, Basic Auth must be handled with strict security. Exposed usernames or passwords can provide direct access to systems, meaning credentials need to be stored and managed with strong encryption.

 

Why Managing Basic Authentication Can Be Risky

Storing Basic Auth credentials directly in application code, configuration files, or developer machines increases risks such as:

 

• Accidental exposure in logs or repositories

 

• Using outdated or shared credentials

 

• Lack of rotation or auditing

 

• Difficulty managing credentials across multiple apps or environments

 

Without proper storage practices, these vulnerabilities can lead to unauthorized access or system compromise.

 

How Namirasoft Credential Secures Basic Auth

Namirasoft Credential does not store your Basic Auth username or password. When you create a Basic Auth record:

 

• The User Name and Password are sent directly to Namirasoft Secret, where they are fully encrypted and stored as secret values.

 

• Namirasoft Credential only keeps references to those encrypted secrets. It never stores the sensitive values themselves.

 

• When a Namirasoft application needs to use your Basic Auth record, Namirasoft Credential retrieves the encrypted values from Namirasoft Secret, groups them into a complete credential, and delivers the final information to the requesting app.

 

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

 

Overview of Basic Auth Fields and Options

The sections below explain every field visible in the Create and List pages for Basic Auth. Understanding these fields will help you store credentials correctly and manage them with accuracy, security, and confidence.

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

• User ID (Namirasoft Account’s ID): This is the unique ID assigned to a user of the Namirasoft Account that created the Basic 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

• User Name (String): This is the actual username used for the Basic Auth login. Enter it exactly as required by the system or service you want to connect to, such as the username of an API account, a service account, or an internal application login. After saving, this username is automatically encrypted and stored inside Namirasoft Secret.

• Password (String): This is the actual password that pairs with the username for Basic Auth authentication. Enter the correct password for the same service or application. Once saved, the password is immediately encrypted and stored in Namirasoft Secret.

• Name (String): This is the readable label you assign to this Basic Auth credential while creating it. Choose a name that clearly tells you what the credential is for.

• Description (String):This optional field lets you explain the purpose or usage of the Basic Auth credential, such as which system it connects to or what team uses it. Adding a description is helpful when working with multiple credentials in a shared workspace because it makes it easier to identify each one later.

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

• Updated At (DateTime): This shows the exact date and time when the Basic Auth credential was most recently modified.