<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Token Asserter on Speedle</title>
    <link>https://engine.speedle.io/tags/token-asserter/</link>
    <description>Recent content in Token Asserter on Speedle</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 21 Jan 2019 09:28:30 +0800</lastBuildDate>
    
	<atom:link href="https://engine.speedle.io/tags/token-asserter/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Token asserter</title>
      <link>https://engine.speedle.io/docs/assertor/</link>
      <pubDate>Mon, 21 Jan 2019 09:28:30 +0800</pubDate>
      
      <guid>https://engine.speedle.io/docs/assertor/</guid>
      <description>What does a token asserter do? A configured asserter validates a token and returns explicit principals, including their identity domains. Speedle can then evaluate policies using those identities. A production implementation must validate the token&amp;rsquo;s signature or introspection result, issuer, audience, expiry and any provider-specific requirements. The webhook alone does not establish compatibility with arbitrary OAuth/OIDC tokens.
The Token Assertion Plugin API uses integer errCode and an optional attribute object, not a typed attribute array.</description>
    </item>
    
  </channel>
</rss>