<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>plugins &#8211; privacyID3A</title>
	<atom:link href="https://www.privacyidea.org/tag/plugins/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.privacyidea.org</link>
	<description>flexible, Open Source Multi Factor Authentication (2FA)</description>
	<lastBuildDate>Wed, 30 Jan 2019 20:50:00 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://www.privacyidea.org/wp-content/uploads/2016/06/cropped-only-logo-white-background-32x32.png</url>
	<title>plugins &#8211; privacyID3A</title>
	<link>https://www.privacyidea.org</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>privacyIDEA ownCloud Plugin allows client specific 2FA</title>
		<link>https://www.privacyidea.org/privacyidea-owncloud-plugin-allows-client-specific-2fa/</link>
		
		<dc:creator><![CDATA[Cornelius Kölbel]]></dc:creator>
		<pubDate>Wed, 30 Jan 2019 20:48:18 +0000</pubDate>
				<category><![CDATA[release]]></category>
		<category><![CDATA[Whatsup]]></category>
		<category><![CDATA[ownCloud]]></category>
		<category><![CDATA[plugins]]></category>
		<guid isPermaLink="false">https://www.privacyidea.org/?p=1482</guid>

					<description><![CDATA[The new release 2.5 of the privacyIDEA ownCloud app allows the administrator to define which client should require 2FA and which is ok with only a password. This is based on the IP address of the clients. This way e.g. users would not need a second factor when accessing ownCloud from the LAN, while they [&#8230;]]]></description>
										<content:encoded><![CDATA[
<figure class="wp-block-image"><img fetchpriority="high" decoding="async" width="1024" height="576" src="https://www.privacyidea.org/wp-content/uploads/2019/01/cloud-computing-2001090_1280-1024x576.jpg" alt="" class="wp-image-1483" srcset="https://www.privacyidea.org/wp-content/uploads/2019/01/cloud-computing-2001090_1280-1024x576.jpg 1024w, https://www.privacyidea.org/wp-content/uploads/2019/01/cloud-computing-2001090_1280-300x169.jpg 300w, https://www.privacyidea.org/wp-content/uploads/2019/01/cloud-computing-2001090_1280-768x432.jpg 768w, https://www.privacyidea.org/wp-content/uploads/2019/01/cloud-computing-2001090_1280-1110x624.jpg 1110w, https://www.privacyidea.org/wp-content/uploads/2019/01/cloud-computing-2001090_1280-528x297.jpg 528w, https://www.privacyidea.org/wp-content/uploads/2019/01/cloud-computing-2001090_1280.jpg 1280w" sizes="(max-width: 1024px) 100vw, 1024px" /></figure>



<p>The new release 2.5 of the privacyIDEA ownCloud app allows the administrator to define which client should require 2FA and which is ok with only a password. This is based on the IP address of the clients.</p>



<p>This way e.g. users would not need a second factor when accessing ownCloud from the LAN, while they would need to provide a second factor when they want to access their critical data over the internet.</p>



<p>The privacyIDEA ownCloud App is available from the <a rel="noreferrer noopener" aria-label="ownCloud Marketplace (opens in a new tab)" href="https://marketplace.owncloud.com/apps/twofactor_privacyidea" target="_blank">ownCloud Marketplace</a> and via <a rel="noreferrer noopener" aria-label="Github (opens in a new tab)" href="https://github.com/privacyidea/privacyidea-owncloud-app" target="_blank">Github</a>.</p>



<p>I will give a talk about the privacyIDEA ownCloud App <a href="https://fosdem.org/2019/schedule/event/owncloud_2fa/" target="_blank" rel="noreferrer noopener" aria-label="at FOSDEM this sunday (opens in a new tab)">at FOSDEM this sunday</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
