Apple treats all iPhone developers equally – like crap

Today Google released Google Latitude for the iPhone, something BlackBerry and Android users have been enjoying for quite some time.

One paragraph in particular jumped out at me, emphasis mine:

We worked closely with Apple to bring Latitude to the iPhone in a way Apple thought would be best for iPhone users. After we developed a Latitude application for the iPhone, Apple requested we release Latitude as a web application in order to avoid confusion with Maps on the iPhone, which uses Google to serve maps tiles.

So Google was working "closely" with Apple, built a native iPhone application1 for Latitude, and then Apple essentially rejected it and told them to build a web application. Isn't building an entire application only to have it wholly rejected one of the leading complaints about the nightmarish App Store approval process?

  1. I'd love to see a build of this leaked out so jailbreak users could run it [back]

Why carriers shouldn't control OS distribution

Paul Haddad from Tapbots writes about the iPhone OS 3.0 adoption rate he's seen among his users.  Granted it's a relatively small sample size based on request headers from 3500 unique requests per day, but it shows the benefits of having the handset manufacturer also controlling the distribution of the OS to end-users.

Tapbots - iPhone OS 3.0 adoption rate
From Tapbots: Percentage of users running a given OS.  x-axis is days in the month of June.

Look at the abuse that BlackBerry users take at the hands of carriers, especially Verizon. It took Verizon 175 days to release an update for the Storm, and even then it came out 33 days after the OS was leaked and unofficially made available.9530 OS Releases
BlackBerry 9530 OS Releases

Just as Apple only has to worry about a relatively small number of drivers for their desktop OS, they only have 5 device models running their mobile OS.  RIM currently has 4-5 that number on GSM, CDMA and IDEN (more on that later), and they are dependent on the carriers to certify and and make an OS update available.

But why should the carriers bother to issue OS updates? Most users are under contract, so the only entity that has something to lose is RIM1 – mostly in the form of negative publicity.

  1. More on this later too [back]

Deploying tokens to the RSA SecurID iPhone Application

OK, so you've got the SecurID soft token app installed on your iPhone, but now what? Installing a token isn't as simple as it is on the BlackBerry.

One method is to use the RSA Authentication Manager to generate CT-KIP URLs which can be sent to the end-users. You can read more about this from the RSA iPhone page after downloading the documentation and device definition file.

My preference is to use the Compressed Token Format (CTF) which will compress a .sdtid soft token file into an 81-digit string.

Clarification

I don't want there to be any confusion about the intent of this post – I'm demonstrating one possible way to install a token on your device without involving an administrator.  In most cases your ACE administrator will probably be willing to assist you with the installation of a token, and none of this will be necessary.

Preparing the Token

You can use the Token Converter application from RSA, or the web-based token converter on my projects page. Paste the contents of your .sdtid file into the form, supply your password if it requires one and create the CTF link.

Distributing the CTF SecurID Token

You can email links to the CTF token file or link to an HTML page containing the link. Both work, although the current version (1.0.5) of the RSA SecurID iPhone Application is overly sensitive to malformed links.  Sending an HTML email from Outlook will generate a malformed link, but as Phil noted in the comments composing a message in RTF format containing the link will work.

Malformed Links

Correct: com.rsa.securid.iphone://ctf?...
Malformed: com.rsa.securid.iphone://ctf/?....

If you are going to email the link make sure that it doesn't append the extra trailing slash after ctf. Do not use Outlook to send the email in HTML format as it always appends the extra slash – compose a RTF message instead.

You may need to change your Outlook options to retain RTF emails when sending to internet recipients.  In Outlook open Options > Mail Format > Internet Format. Under "When sending Outlook Rich Text messages to Internet recipients, use this format:" change the option to "Send using Outlook Rich Text format".

Outlook - Send using RTF

Emailing the CTF Link

For iPhone users running OS 2.x you can compose a plain text message with the CTF link (com.rsa.securid.iphone://ctf?ctfData=<token>) between angle brackets.

<com.rsa.securid.iphone://ctf?ctfData=200010059123075173498074908439042057320570235870932850239850433809854092834893835>

This will only work with OS 2.x, and not with the GM release of OS 3.0.

For all users running OS 2.x and OS 3.x you can send an HTML-formatted email with a hyperlink to the CTF URL, like Click here to install Token.  As mentioned above this will NOT work with Outlook, which adds an extra forward slash that the SecurID application cannot understand.

Linking to a page containing a CTF Link

The third option is to use Mobile Safari to open a web page containing a hyperlink to the CTF URL.  You can put this page somewhere on your own servers, or use my RSA CTF Hyperlink Generator to dynamically build these links. Opening http://coreygilmore.com/rsa/<CTF> will automatically  display an iPhone-ready hyperlink  to install the token.  View a sample page.

Resources

Updated 6/18/09: Added information about composing Outlook RTF emails to successfully send token installation links, brief clarification about the intent of this post.

RSA SecurID Soft Token client for the iPhone

RSA iPhone Soft Token

On Monday RSA launched a soft-token application for the iPhone. Similar to the BlackBerry soft token application, this will store a single token and allow you to generate a one-time password.

You can download the RSA iPhone SecurID application from iTunes (ITMS link) and read more about it on the RSA site at http://rsa.com/iphone.

Screenshots

RSA iPhone SecurID Application - Enter PIN RSA iPhone SecurID Application - Token Information RSA iPhone SecurID Application - Passcode

Installation

Read Deploying tokens to the RSA SecurID iPhone Application for a rundown of the various deployment and provisioning options.

Updated June 16, 2009: Misread documentation; the application will only store one token.


© 2007-2012, Corey Gilmore | Posts RSS Feed | Comments RSS Feed | Contact

 

The views expressed on these pages are mine alone and not those of any past or present employer. All information presented on this site was obtained lawfully and not through disclosure under the terms of an NDA.