We've never tested against the Aladdin tokens, but someone else on this forum ran into that problem and posted the solution. Here's a link to the thread:
 | Date | | Topic |
 | 11/09/2002 | 11 | eToken Pro & Notes (Jan-Piet Mens) |
| 11/11/2002 | 10 | Solved by Eli (Jan-Piet Mens) |
| 11/11/2002 | 9 | Re: eToken Pro & Notes (Dave Kern) |
| 11/12/2002 | 8 | RE: Re: eToken Pro & Notes (Jan-Piet Mens) |
| 11/13/2002 | 7 | RE: Re: eToken Pro & Notes (Dave Kern) |
| 11/14/2002 | 6 | RE: Re: eToken Pro & Notes (Jan-Piet Mens) |
| 11/15/2002 | 5 | RE: Re: eToken Pro & Notes (Dave Kern) |
| 11/17/2002 | 4 | Error (Jan-Piet Mens) |
| 11/18/2002 | 3 | Notes requires the CKM_RSA_PKCS mechanism (Dave Kern) |
| 11/19/2002 | 2 | Asking Aladdin (Jan-Piet Mens) |
| 12/05/2002 | 1 | Response from Aladdin (Jan-Piet Mens) |
| 12/06/2002 | | RE: Response from Aladdin (Dave Kern) |
However, it doesn't sound like the Aladdin eToken Pro supports the cryptographic mechanisms in hardware that Notes needs to use keys stored on the token, so you might not have much success beyond protecting your ID file with the token. However, Aladdin may have updated their driver software in the past 9 months, so it's probably worth checking just to be sure. :)
If you're using 6.0.2 or later, you can write a simple C API program to determine if a given token provides what Notes needs. Check out the documentation for SECManipulateSC --- calling that function with the SC_manip_CheckCard opcode will tell you if the token is likely to work with Notes or not. The call is well documented in the "Lotus C API Notes/Domino 6.0.2 Reference".
Good luck,
dave
PS - the actual sequence of opcodes would be SC_manip_InitializeContext, then SC_manip_CheckCard, then SC_manip_TerminateContext.
Return to top
. . . . 
. . The solution was posted in a past t... (~Tanita Desweve... 9.Aug.03)
Print this page
