<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">

 
 
  <channel>
    <title>CryptoJS on ServiceNow Developer Blog</title>
    <link>https://developer.servicenow.com/blog.do?p=/tags/cryptojs/</link>
    <description>Recent content in CryptoJS on ServiceNow Developer Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 31 Mar 2017 05:40:00 +0000</lastBuildDate>
    
        
        
         
        <atom:link href="https://developer.servicenow.com/blog.do?p=/tags/cryptojs/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Live Coding Happy Hour Recap for March 17, 2017 - Sift API and Request Signature Generation</title>
      <link>https://developer.servicenow.com/blog.do?p=/post/live-coding-happy-hour-recap-for-march-17-2017-sift-api-and-request-signature-generation/</link>
      <pubDate>Fri, 31 Mar 2017 05:40:00 +0000</pubDate>
      
      <guid>https://developer.servicenow.com/blog.do?p=/post/live-coding-happy-hour-recap-for-march-17-2017-sift-api-and-request-signature-generation/</guid>
      <description>YouTube video: https://youtu.be/R1Qgz51T4wI The Live Coding Team: dave.slusher, ctomasi, josh.nerius
In this episode, we work with the Sift API in order to parse emails. Specifically, the involved generation of the signature in order to validate the request is the main thrust of this session. We begin with two requests that outwardly seem the same and work through why they signatures first are different and then generate different results between using NodeJS and the integration from a ServiceNow instance.</description>
    </item>
    
  </channel>
</rss>