RSA and VMware View iPad App

One of the nifty things about the current VMware View iPad App is it's ability to import a RSA token.  Unfortunately, the documentation on how to do this is a bit scarce.  These steps may work for Android too, but I don't have an Android tablet to test with.

PreReqs:

  1. RSA Server 7.1 SP4 <-- This is what I tested against.
  2. View 4.5+ w/ RSA enabled.
  3. VMware View iPad application
Simply go to your RSA self-service page and request a new token.  If it's enabled you should have an option like this:
You'll want to select "I need a specific software token" then select "RSA SecurID Token for iPhone and iPAD/iPOD"

Once you or your RSA admin approve your request, you should get a link and activation code that looks something like this:

Joe, your new or additional software token request has been approved with the following comments from your administrator:
 RSAAdmin: approved
 Please ensure that the RSA SecurID application is installed on your device before attempting to import your software token.
 Download the SecurID Application: com.rsa.securid://ctkip?url=https://yourRSAServer:7004/ctkip/services/CtkipService

How To Import Your Software Token ( true ) Please follow the instructions provided by your administrator to import a token using the following information:
 Link: https://yourRSAServer:7004/ctkip/services/CtkipService
 Activation Code: 0000000000000

To import the software token into your iPad View app, you can copy the simply change the link that is prefixed w/ com.rsa.securid to viewclient-securid.  So the link would look something like this instead:

When you type/copy/paste this link into safari, it should open up the view ipad client and ask for you activation code.

Once done, you will be able to simply type your PIN for RSA credentials.

Comments

Phil said…
We do not have wireless at our organization and our RSA server is on the LAN. Do you have any tips on how to do this?
October 9, 2012 at 2:38 PM
Zsoldier said…
You'll need to make your RSA server's self service console available via external methods
October 9, 2012 at 9:03 PM
Post a Comment

Popular posts from this blog

NSX-T: Release associated invalid node ID from certificate

Image
Summary: Basically had an expiring certificate registered in NSX-T that was associated to a node_id that is no longer valid.  Long story short, there wasn't anything obvious in API to delete or disassociate a certificate from a node_id for 3.2.2.  Not sure how things got in this state, but annotating for future reference.  This may change in future revisions, so always check API for latest. Details: Effectively had a stale node associated w/ a certificate that was expiring.  Could not delete certificate until that node was disassociated from the certificate. To get certificate details and associated node_id's, you can use the following curl call (UI works too): curl -k -X GET -H "Content-Type: application/json" -u admin https://<manager ip>/api/v1/trust-management/certificates/<cert UUID> Above will return something like this: Below must be run from one of the manager nodes via elevation to root: ONLY RUN THIS IF YOU ARE ABSOLUTELY SURE OF WHAT YOU ARE DO...
Read more

NSX-T: vCenter and NSX-T Inventory out of Sync (Hosts in vSphere not showing up in NSX-T)

Image
Summary: NSX-T loses synch w/ vCenter inventory, but statuses don't appear to show an issue.  Basically, you add a host to a vCenter cluster, NSX-T bits should start to automatically installing on new host.  Assuming you've created a Transport Node Profile and associated w/ the cluster.  The problem is that NSX-T doesn't see the new host and its link to the compute manager (vCenter) looks fine. Looks fine, Y U NO WORK!? So what's going on here?  This appears to affect NSX-T 2.5 and 2.5.1.  Cause is unknown. Workaround: Restart the cm-inventory service on each NSX-T mgmt/controller node using API or CLI. Details: If you were to query the status of the cm-inventory via API or CLI, you could query all 3 manager/controller nodes and get a status of running.  Even if the primary node associated w/ the VIP, if configured, is not necessarily in charge of inventory.  So you could restart the cm-inventory service till you are blue in the face ...
Read more

MacOS: AnyConnect VPN client was unable to successfully verify the IP forwarding table modifications.

Image
The VPN client was unable to successfully verify the IP forwarding table modification.  A VPN connection will not be established. Summary: I started running into issue utilizing Cisco AnyConnect on my Mac basically complaining about not able to overwrite IP forwarding tables.  This was on 4.6.x.  Since my VPN endpoints were not providing me w/ an updated client and w/ no access to Cisco Anyconnect downloads, my only option was to try openconnect.  It was totally worth it, here is why and how to set it up. PreReqs: Homebrew Installing OpenConnect: Launch MacOS Terminal brew install openconnect Getting VPN IP's/DNS Endpoints from AnyConnect: The information is typically located in your profile xml files located here: /opt/cisco/anyconnect/profile/somethingsomething.xml In the xml file, you are looking for "<HostAddress>typicallyaDNSName.com</HostAddress>" entry.  These are your VPN endpoints that you would need to pass to openconnec...
Read more