<?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>SMS &#8211; privacyID3A</title>
	<atom:link href="https://www.privacyidea.org/tag/sms/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.privacyidea.org</link>
	<description>flexible, Open Source Multi Factor Authentication (2FA)</description>
	<lastBuildDate>Thu, 30 Jun 2016 14:42:01 +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>SMS &#8211; privacyID3A</title>
	<link>https://www.privacyidea.org</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>privacyIDEA 2.13 released &#8211; Improved Text Messages and PIN</title>
		<link>https://www.privacyidea.org/privacyidea-2-13-released/</link>
					<comments>https://www.privacyidea.org/privacyidea-2-13-released/#respond</comments>
		
		<dc:creator><![CDATA[Cornelius Kölbel]]></dc:creator>
		<pubDate>Thu, 30 Jun 2016 14:05:56 +0000</pubDate>
				<category><![CDATA[release]]></category>
		<category><![CDATA[Whatsup]]></category>
		<category><![CDATA[notification]]></category>
		<category><![CDATA[PIN handling]]></category>
		<category><![CDATA[Policy]]></category>
		<category><![CDATA[SMS]]></category>
		<guid isPermaLink="false">https://www.privacyidea.org/?p=976</guid>

					<description><![CDATA[Yes I know. And I also always said, please do not use SMS for two factor authentication. Rely on a decent piece of hardware. Although you should stop using text for two factor authentication, privacyIDEA supports text messages or SMS besides a long list of other token types. Text message (SMS) enhancements Nevertheless privacyIDEA 2.13 [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>Yes I know. And I also always said, please do not use SMS for two factor authentication. Rely on a decent piece of hardware. Although <a href="https://www.wired.com/2016/06/hey-stop-using-texts-two-factor-authentication/" target="_blank">you should stop using text for two factor authentication</a>, privacyIDEA supports text messages or SMS besides a <a href="https://www.privacyidea.org/about/features/">long list of other token types</a>.<a href="https://www.privacyidea.org/wp-content/uploads/2016/06/iphone-388387_640.jpg"><img decoding="async" class="size-medium wp-image-978 alignright" src="https://www.privacyidea.org/wp-content/uploads/2016/06/iphone-388387_640-300x200.jpg" alt="iphone-388387_640" width="300" height="200" srcset="https://www.privacyidea.org/wp-content/uploads/2016/06/iphone-388387_640-300x200.jpg 300w, https://www.privacyidea.org/wp-content/uploads/2016/06/iphone-388387_640.jpg 640w" sizes="(max-width: 300px) 100vw, 300px" /></a></p>
<h2>Text message (SMS) enhancements</h2>
<p>Nevertheless privacyIDEA 2.13 comes with improved SMS handling. But be sure, SMS can not only be used for authentication but for many other things. privacyIDEA 2.13 now lets you define a central list of SMS gateways &#8211; just like with centrally defined <a href="https://www.privacyidea.org/privacyidea-2-10-released-all-for-the-user/">SMTP servers</a> and <a href="https://www.privacyidea.org/privacyidea-2-11-easy-migration-radius-policy/">RADIUS servers</a>. Now privacyIDEA can centrally define all communication channels it needs. Defining your SMS gateway centrally eases the setup of your SMS token type.</p>
<p>But text messages now can also be used to notify users in case of certain events. The <a href="https://www.privacyidea.org/privacyidea-2-12-released-event-handler-certificates-pkcs12-pkcs11-much/">event handling with user notification was added in version 2.12</a> with notification via email &#8211; now you can also use text messages.</p>
<p>These SMS gateways could be used for other features in the future like notifying administrators in case of certain errors&#8230; Feel free to <a href="https://github.com/privacyidea/privacyidea" target="_blank">open any feature request on github</a>.</p>
<h3>PIN handling</h3>
<p>The second main features is PIN handling. You may have noticed the new logo of privacyIDEA.</p>
<figure id="attachment_964" aria-describedby="caption-attachment-964" style="width: 300px" class="wp-caption alignnone"><a href="https://www.privacyidea.org/wp-content/uploads/2016/06/privacyIDEA-800px.png"><img decoding="async" class="wp-image-964 size-medium" src="https://www.privacyidea.org/wp-content/uploads/2016/06/privacyIDEA-800px-300x162.png" alt="privacyIDEA-800px" width="300" height="162" srcset="https://www.privacyidea.org/wp-content/uploads/2016/06/privacyIDEA-800px-300x162.png 300w, https://www.privacyidea.org/wp-content/uploads/2016/06/privacyIDEA-800px-768x415.png 768w, https://www.privacyidea.org/wp-content/uploads/2016/06/privacyIDEA-800px.png 800w" sizes="(max-width: 300px) 100vw, 300px" /></a><figcaption id="caption-attachment-964" class="wp-caption-text">privacyIDEA &#8211; the flexible, modular authentication system.</figcaption></figure>
<p>You can see the bottom line &#8220;Authentication System&#8221;. Already a while ago privacyIDEA left the track of a pure OTP system, when adding support for SSH keys, certificates and Yubikeys for LUKS.</p>
<p>privacyIDEA can now take care about PIN policies and require the user to change the PIN after a defined time span. You can also set a policy that a user will have to change the PIN after first use! I am curious what you think about the PIN thing. If you have any further ideas about passwords and PINs drop us a note, write a comment or and <a href="https://github.com/privacyidea/privacyidea" target="_blank">issue on github</a>.</p>
<h2>Further Enhancements</h2>
<p>&#8230;are</p>
<ul>
<li>Performence enhancements in the Web UI regarding the token view and the audit log.</li>
<li>An additional log level below &#8220;DEBUG&#8221;. Debug will log no passwords. If you need passwords in your debug output, set the loglevel to &#8220;9&#8221;.</li>
<li>Quick actions in the token list. Try and click on the Failcounter or the &#8220;active&#8221; column.</li>
<li>Intelligent proxy handling or &#8220;OverrideAuthorizationClient&#8221; setting, which allows to define, which proxy server is allowed to change the client information.</li>
</ul>
<p>The <a href="https://github.com/privacyidea/privacyidea/blob/master/Changelog" target="_blank">full changelog can be found here</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.privacyidea.org/privacyidea-2-13-released/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
