Skip to main content
Open credentials with the key icon. Agents can register credentials from command responses, payload containers can create them through RPC, and operators can add or update them manually.

​
Credential fields

Every credential has a type, account, realm, credential value, and comment. Mythic 4.0 also supports:
  • subtype for a more precise classification within a credential type
  • custom_display for a safe, operator-friendly label
  • validity state and update history
  • dedicated JWT and Kerberos renderers
Use custom_display to help operators identify a credential without placing the secret itself in views that do not require it. Credential updates retain one record instead of forcing an integration to create near-duplicates as metadata changes.
The table identifies the creating task (or Manual Entry), operator, timestamps, type and subtype, realm, account, and validity.

​
Use credentials in commands

A CredentialJson command parameter presents matching operation credentials in the tasking UI. A developer can further limit choices by credential type for a specific command parameter. The selected value reaches the payload type’s tasking function as a structured object. Mythic 4.0 also supports explicit references in string and structured parameters:
Mythic resolves references immediately before tasking, records the resolution on the task, and sends containers both the resolved parameter and resolution metadata. See Tasking References. Agents can register credentials in a normal response, while payload type code can use MythicRPC for create, search, and update workflows. See Hooking Features: Credentials.