<?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: Tip: Easy Salesforce Logins</title>
	<atom:link href="http://www.judisohn.com/2009/06/tip_easy_salesforce_logins/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.judisohn.com/2009/06/tip_easy_salesforce_logins/</link>
	<description>It&#039;s a reason, not an excuse</description>
	<lastBuildDate>Mon, 15 Mar 2010 04:34:38 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Judi Sohn</title>
		<link>http://www.judisohn.com/2009/06/tip_easy_salesforce_logins/comment-page-1/#comment-20638</link>
		<dc:creator>Judi Sohn</dc:creator>
		<pubDate>Sun, 05 Jul 2009 13:58:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.judisohn.com/2009/06/tip_easy_salesforce_logins/#comment-20638</guid>
		<description>Good to know, thanks!</description>
		<content:encoded><![CDATA[<p>Good to know, thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas R. Hall</title>
		<link>http://www.judisohn.com/2009/06/tip_easy_salesforce_logins/comment-page-1/#comment-20637</link>
		<dc:creator>Thomas R. Hall</dc:creator>
		<pubDate>Sun, 05 Jul 2009 13:45:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.judisohn.com/2009/06/tip_easy_salesforce_logins/#comment-20637</guid>
		<description>JP Seabury beat me to it on the hex encoding. :)

Something else to consider about using a &quot;GET&quot; URL (where you provide your username and password as part of the URL) is that it is a bit more of a security risk. Even if that link is only on your machine, once you click on it, the full link is available in the web server logs on Salesforce&#039;s servers _in plain text_. So any sysadmin who has access to the web server logs would know your user ID and password. Just a word of caution. Using something like Roboform, KeePass, 1Password, etc. is a better way, if possible.

Note that if you use a &quot;POST&quot; request, the data is not passed as part of the URL, and thus not in the web server logs.</description>
		<content:encoded><![CDATA[<p>JP Seabury beat me to it on the hex encoding. <img src='http://www.judisohn.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Something else to consider about using a &#8220;GET&#8221; URL (where you provide your username and password as part of the URL) is that it is a bit more of a security risk. Even if that link is only on your machine, once you click on it, the full link is available in the web server logs on Salesforce&#8217;s servers _in plain text_. So any sysadmin who has access to the web server logs would know your user ID and password. Just a word of caution. Using something like Roboform, KeePass, 1Password, etc. is a better way, if possible.</p>
<p>Note that if you use a &#8220;POST&#8221; request, the data is not passed as part of the URL, and thus not in the web server logs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JP Seabury</title>
		<link>http://www.judisohn.com/2009/06/tip_easy_salesforce_logins/comment-page-1/#comment-20597</link>
		<dc:creator>JP Seabury</dc:creator>
		<pubDate>Mon, 29 Jun 2009 15:22:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.judisohn.com/2009/06/tip_easy_salesforce_logins/#comment-20597</guid>
		<description>Great tip.  In the past, I&#039;ve implemented this for a few members of our executive team -- who were constantly forgetting their passwords.  It is &quot;dangerous&quot;, so your warnings to use it sparingly and only in tightly controlled circumstances is spot on.

The %40 is the hex-format for the ascii control character code for the &quot;@&quot; symbol.  There are certain characters that you can&#039;t include in a URL address (like space, the &quot;@&quot; symbol, etc.).  For these, you need to encode them in their hex format.  For the desperately curious, more details here: http://www.csgnetwork.com/asciiset.html

If you&#039;re concerned about this method for security reasons, then I highly recommend RoboForm (http://www.roboform.com).  The application is free for up to 10 different accounts.  I fell in love with the mobile version of this, which lets me securely keep my passwords and logins to all my different Salesforce and Developer accounts on a USB drive.  It&#039;s definitely worth looking into.

Great post, Judi!</description>
		<content:encoded><![CDATA[<p>Great tip.  In the past, I&#8217;ve implemented this for a few members of our executive team &#8212; who were constantly forgetting their passwords.  It is &#8220;dangerous&#8221;, so your warnings to use it sparingly and only in tightly controlled circumstances is spot on.</p>
<p>The %40 is the hex-format for the ascii control character code for the &#8220;@&#8221; symbol.  There are certain characters that you can&#8217;t include in a URL address (like space, the &#8220;@&#8221; symbol, etc.).  For these, you need to encode them in their hex format.  For the desperately curious, more details here: <a href="http://www.csgnetwork.com/asciiset.html" rel="nofollow">http://www.csgnetwork.com/asciiset.html</a></p>
<p>If you&#8217;re concerned about this method for security reasons, then I highly recommend RoboForm (<a href="http://www.roboform.com" rel="nofollow">http://www.roboform.com</a>).  The application is free for up to 10 different accounts.  I fell in love with the mobile version of this, which lets me securely keep my passwords and logins to all my different Salesforce and Developer accounts on a USB drive.  It&#8217;s definitely worth looking into.</p>
<p>Great post, Judi!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
