<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>sitecore-hardening on bramstoop.com</title>
    <link>https://www.bramstoop.com/tags/sitecore-hardening/</link>
    <description>Recent content in sitecore-hardening on bramstoop.com</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Fri, 11 Aug 2017 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.bramstoop.com/tags/sitecore-hardening/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Sitecore hardening using Azure App Authentication</title>
      <link>https://www.bramstoop.com/posts/2017/08/2017-08-11-sitecore-hardening-using-azure-app-authentication/</link>
      <pubDate>Fri, 11 Aug 2017 00:00:00 +0000</pubDate>
      
      <guid>https://www.bramstoop.com/posts/2017/08/2017-08-11-sitecore-hardening-using-azure-app-authentication/</guid>
      <description>BACK TO BLOG OVERVIEW
  With Azure App Authentication it is easy to secure your app with an identity provider. The steps to take are described at the following page: https://docs.microsoft.com/en-us/azure/app-service-mobile/app-service-mobile-how-to-configure-active-directory-authentication .
For securing certain url paths it is required to set Action to take when request is not authenticated to Allow request (no action).
When you have followed the instructions above, the next step is to create a authorization.</description>
    </item>
    
  </channel>
</rss>