AMPS
  • What is AMPS?
  • Getting Started
    • Installation
      • Docker
      • Kubernetes
        • Local
        • Openshift
        • AWS
    • Setup
  • Fundamentals
    • Admin
      • Monitoring
        • Message Events
        • Sessions
        • Service Monitoring
        • System Logs
        • Audit Log
        • Consumers
      • Onboarding
        • Groups
        • Users
      • Message Configuration
        • Topics
        • Actions
        • Services
        • Scripts
        • Templates
        • Routing Rules
        • API Endpoints
        • Metadata Fields
        • Keys
        • Jobs
      • Data Configuration
        • Providers
        • Environments
        • Packages
      • Tools
      • System Configuration
    • End User
      • Mailboxes
      • Universe File Agent
      • Auth Tokens
    • Python
  • Use Cases
    • For Engineers
      • GitHub Integration
    • For Support
      • Intercom Integration
  • Guides
    • Creating your first project
    • Creating your first task
    • Advanced permissions
Powered by GitBook
On this page
  1. Fundamentals
  2. End User

Auth Tokens

PreviousUniverse File AgentNextPython

Last updated 2 years ago

Auth Tokens are ID-Secret pairs used to authenticate an AMPS User on any AMPS Service or UFA Agent. Auth Tokens can be created by specifying a name, and a Token ID and Token Secret are automatically generated and stored. The Token Secret can be retrieved from the UI by pressing the key icon in the grid.

When using Auth Tokens to authenticate an AMPS HTTP Service (Mailbox API or Gateway) the ID and Secret are provided as the username and password, respectively, in an . When downloading a UFA Agent, users are required to specify a corresponding auth token to use for authenticating on behalf of the user, which is subsequently downloaded in the configuration file alongside the agent.

In order to revoke an Auth Token, it can simply be deleted from the UI, after which it will no longer be able to authenticate.

HTTP Basic Auth Header