📘A Complete Guide to Understanding the Namirasoft Credential Console

Guide Overview

This guide is designed to help you navigate and fully utilize the Namirasoft Credential Console. Whether you’re creating new AWS, GCP, or Azure credentials, reviewing existing records, or understanding each field’s purpose, this section‑by‑section walkthrough provides clear explanations and best practices to manage your cloud authentication securely and efficiently.

Introduction to Namirasoft Credential

Namirasoft Credential is a centralized authentication management solution that lets you register, store, and organize your AWS, GCP, and Azure credentials in one unified console. By providing intuitive Create and List views for each cloud provider, it ensures that every key, secret, or service‑account file is clearly labeled, auditable, and accessible to downstream Namirasoft applications under strict access controls.

• ID (string):  This is a unique ID automatically assigned to the watch (by Namirasoft Bill Watch) once it’s created. You don’t set this yourself; it’s used internally to reference the watch record.

• User ID (Namirasoft Account’s ID): This is the unique ID assigned to a user of the Namirasoft Account, which gives access to all Namirasoft apps. This ties the watch to a specific user (for access control and tracking). It does not directly affect the monitoring logic, but is used in the backend to manage permissions and history.

• Workspace ID (Namirasoft Workspace’s ID): This refers to a workspace created in the Namirasoft Workspace app, which allows users to group projects, teams, or environments. In Namirasoft Bill Watch, the workspace name is displayed (not just the ID), and it links directly to the Workspace app where it displays the ID for that workspace. This ensures that each watch is tied to the correct environment and only monitors credentials and accounts associated with that workspace.

• AWS Access Key (String): This is a public identifier issued by Amazon Web Services (AWS) when you create a new user or access role. It works like a username in API-based systems. When your Namirasoft app connects to AWS, the Access Key tells AWS who is making the request. This key must always be paired with the Secret Key to allow access.

• AWS Secret Key (String): This is a private, secret string generated along with the AWS Access Key. It functions like a password for your access identity. The Secret Key is used to create a secure digital signature when your app sends a request to AWS. Together with the Access Key, it ensures the request is authenticated and hasn’t been tampered with.

• GCP Credentials (JSON): This is a file in JSON format that contains everything needed to access Google Cloud Platform (GCP) programmatically. It includes a private key and metadata such as project ID, service account email, and token URI. This file allows Namirasoft to authenticate on your behalf using a specific service account without needing manual login.

• Azure Client ID (String): This is a unique identifier assigned to your registered application in Microsoft Azure. When your Namirasoft app wants to access Azure resources, this Client ID tells Azure which application is requesting access. It’s like a unique username for your app in Azure’s authentication system.

• Azure Client Secret (String): This is a confidential password-like string tied to your Azure Client ID. It’s used during the login process to prove that the application is authorized. When your app connects to Azure, it submits both the Client ID and Client Secret to receive an access token.

• Azure Tenant ID (String): This is the identifier of your Azure Active Directory (AD) instance. It tells Azure where to look for your app’s registration and user permissions. If your organization has its own Azure AD, this ID is what separates your directory from others. It’s required to make sure your app connects to the correct tenant.

• Name (String): This is a human‑friendly label you choose to identify the credential. This is required when creating a credential; helps you and your team recognize which credential is which. It has no impact on authentication itself.

• Description (String): This is an optional text field where you can explain the purpose, environment, or role of this credential. For example, you might note that it’s used for billing alerts in production or that it connects to a test project.

• Created At (DateTime): This shows the exact date and time when the credential was originally added to the Namirasoft Credential system. This value is automatically set when you create the credential and does not change over time.

• Updated At (DateTime): This shows the last time this credential was edited. Any change (like renaming it, updating the secret, or modifying the description) will update this timestamp. It helps you track when the credential was last maintained.