From 4c78eceff17ed7a249b2468a4e1b77ccb24fa4a4 Mon Sep 17 00:00:00 2001
From: Taylor Thomas <thomastaylor312@gmail.com>
Date: Wed, 21 Jun 2017 22:48:52 -0700
Subject: [PATCH] fix(docs): Clarifies login flow for IAM auth (#49)

* fix(docs): Clarifies login flow for IAM auth

There was some missing information on an intermediate step for
decrypting a payload. This clarifies the decryption step.

* Minor edit
---
 API.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/API.md b/API.md
index 139e907d3..32bc5a8e9 100644
--- a/API.md
+++ b/API.md
@@ -157,7 +157,11 @@ This endpoint takes IAM ARN information and generates an base 64 encoded KMS enc
             }
 
 + Response 200 (application/json)
-
+    + The response will be a simple JSON payload with the encrypted data
+            {
+                "auth_data": "long-encrypted-string"
+            }
+    + Once you have the encrypted string, you need to make a call to AWS Key Management Service (KMS) to decrypt the response. The decrypted response will contain the body below with the token needed to access Cerberus
     + Body
 
             {