<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
	
	>
<channel>
	<title>
	Comments on: privacyIDEA 2.4 released &#8211; OTP for Hosted Environments	</title>
	<atom:link href="https://www.privacyidea.org/privacyidea-2-4-released-otp-for-hosted-environments/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.privacyidea.org/privacyidea-2-4-released-otp-for-hosted-environments/</link>
	<description>flexible, Open Source Multi Factor Authentication (2FA)</description>
	<lastBuildDate>Tue, 29 Dec 2015 19:01:42 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>
		By: privacyIDEA 2.10: User self registration and notification		</title>
		<link>https://www.privacyidea.org/privacyidea-2-4-released-otp-for-hosted-environments/#comment-533</link>

		<dc:creator><![CDATA[privacyIDEA 2.10: User self registration and notification]]></dc:creator>
		<pubDate>Tue, 29 Dec 2015 19:01:42 +0000</pubDate>
		<guid isPermaLink="false">https://www.privacyidea.org/?p=650#comment-533</guid>

					<description><![CDATA[[&#8230;] The classical concept of privacyIDEA was: You have a user database &#8211; a user store &#8211; and privacyIDEA just reads this user store. In classical scenarios such as the enterprise environment with the Active Directory user base this is a perfect concept, because users are already existing. Over time I had to learn that this covers only 95% of the real world. So in version 2.4 we added user management &#8211; or editable userIdResolvers. [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] The classical concept of privacyIDEA was: You have a user database &#8211; a user store &#8211; and privacyIDEA just reads this user store. In classical scenarios such as the enterprise environment with the Active Directory user base this is a perfect concept, because users are already existing. Over time I had to learn that this covers only 95% of the real world. So in version 2.4 we added user management &#8211; or editable userIdResolvers. [&#8230;]</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
