[isalist] Re: OWA 2007 with RSA

  • From: Jim Harrison <Jim@xxxxxxxxxxxx>
  • To: "isalist@xxxxxxxxxxxxx" <isalist@xxxxxxxxxxxxx>
  • Date: Thu, 7 Feb 2008 08:35:55 -0800

http://www.ISAserver.org
-------------------------------------------------------

You can't bridge RSA auth.
IOW, you can have it at ISA or you can have it at the CAS, but not both.

-----Original Message-----
From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On 
Behalf Of D PIETRUSZKA USWRN INTERLINK INFRA ASST MGR
Sent: Thursday, February 07, 2008 7:30 AM
To: isalist@xxxxxxxxxxxxx
Subject: [isalist] OWA 2007 with RSA

Hello all, this is already driving me crazy. Did anybody publish OWA 2007 with 
RSA authentication?

It is pretty easy to have the forms asking you for the token, but my problem is 
that our users are using just RSA to login, there is no password for them (well 
there is but they don't know it).

The point is: ISA should authenticate the user using  RSA and then pass the 
credentials to the CAS server, so when the user reach the CAS this one already 
have the token and authorize the user to see his/her mailbox.



Today I have the form asking for passcode, then the CAS asking for the passcode 
again (which is pretty crappy).

I can publish the CAS directly on Internet, so the users will be asked just 
once for the passcode but I would like to have ISA stopping the users and 
asking for authentication.



Anybody?





Regards

Diego R. Pietruszka

------------------------------------------------------
List Archives: //www.freelists.org/archives/isalist/
ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp
ISA Server Articles and Tutorials: http://www.isaserver.org/articles_tutorials/
ISA Server Blogs: http://blogs.isaserver.org/
------------------------------------------------------
Visit TechGenix.com for more information about our other sites:
http://www.techgenix.com
------------------------------------------------------
To unsubscribe visit http://www.isaserver.org/pages/isalist.asp
Report abuse to listadmin@xxxxxxxxxxxxx

Other related posts: