🤖 What is an Agent in REL-ID?

In REL-ID, an Agent refers to a registered application or service that uses the SDK to interact with the REL-ID ecosystem.

• It represents a trusted app or integration (e.g., a specific version of your mobile banking app).
• Each agent is uniquely identified by an Agent ID.
• The Agent ID is configured during SDK initialization or provisioning.

🔍 Purpose of an Agent:

• Scopes cryptographic contexts (e.g., session keys, identity).
• Enables multi-tenant support (each app/client can have its own Agent ID).
• Useful for secure logging, auditing, and context-aware operations.

🔐

Data encrypted with one Agent ID typically cannot be decrypted using another, supporting secure compartmentalization.

GetAgentID API

The getAgentID API provides the unique identifier of the agent configured in the REL-ID SDK. This identifier is vital for identifying the active agent context within the mobile application and is often used for logging, auditing, or scope-limited operations.

🎯 Purpose

Use this API to:

• Retrieve the configured Agent ID for the current SDK session.
• Support multi-agent or environment-specific logic.
• Add traceability to logs or transaction metadata.

🔁 API Flow

1. Initialize the SDK.
2. Call getAgentID().
3. Use the returned agent ID string for display or tracking.

🧾 Response

Returns the agent ID as a String value.

🔧 Example Response:

AGENT_001

💻 Code Snippets

RdnaClient.getAgentID((response) => {
  const agentId = response.response;
});

final agentId = await rdnaClient.getAgentID();

com.uniken.rdnaplugin.RdnaClient.getAgentID(successCallback, errorCallback);

NSString* agentId = [rdnaClient getAgentID];

String agentId = rdnaClient.getAgentID();

⚠️ Error Codes

🧠 Developer Notes

• Agent ID is unique per application agent registration.
• Useful for multi-tenant apps or environments.
• Should be logged with each secured transaction for traceability.