Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Overview

Armor uses ADFS and OAUTH workflow for the portal and API authentication.  By presenting a retrieved Bearer id_token to the API a user can leverage the API documentation to access all endpoints from both the Legacy and v2 API.  Below is documentation to retrieve a token from Armor’s SSO platform using your Armor user account with MFA.


Postman Example

Armor Auth Collection.postman_collection.json
 

Instructions:

Create a postman environment named “Armor” (https://learning.postman.com/docs/postman/variables-and-environments/managing-environments/)

    • Ensure that Armor is your selected environment
    • Add amp-account-id with your Account Number (e.g. 1000)
      • amp-account-id can be auto populated with the first account in your account with “[Example] Get User Account Info”

Add your Username and Password under 'Body' of Armor Auth Collection -> 1. SSO Auth 

Execute step “1. SSO Auth”

  • mfa token will be set in your Environment

Execute step “2. Get Bearer (You will receive MFA call)”

  • id_token will be set in your Environment

Follow the [Example] requests to leverage the Armor API, the new id_token is auto populated for these requests.

  • No labels