Certificate-based authentication between CAS client & server

[GoogleCodeExporter]

What steps will reproduce the problem?
1. At, CAS client side, do we need to have secure certificate to connect 
to CAS server?
2. if so, where we have to configure it?
3.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?

Please provide any additional information below.

Original issue reported on code.google.com by sgod...@gmail.com on 22 Feb 2008 at 5:39

[GoogleCodeExporter]

No, the client does not need a certificate. The client connects to the CAS 
server via
SSL like a normal web browser. There is no need to manually configure a 
certificate
on the client side.

I suppose t might be interesting to add a client-authentication feature, where 
the
CAS client would have to authenticate with the server prior to doing any 
transactions
via certificates. But for most purposes I don't think this is necessary.

Original comment by matt.zuk...@gmail.com on 22 Feb 2008 at 4:23

[GoogleCodeExporter]

Thank you for the quick response. I got it.

Original comment by sgod...@gmail.com on 22 Feb 2008 at 8:52

[GoogleCodeExporter]

Original comment by matt.zuk...@gmail.com on 27 Feb 2008 at 8:08

• Changed title: Certificate-based authentication between CAS client & server
• Changed state: Accepted
• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Original comment by matt.zuk...@gmail.com on 27 Feb 2008 at 8:08

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

See
http://groups.google.com/group/rubycas-server/browse_thread/thread/6beda6521ba3a
e8e?hl=en

And
http://code.google.com/p/rubycas-server/source/browse/trunk/lib/casserver/authen
ticators/client_certificate.rb

Original comment by matt.zuk...@gmail.com on 26 May 2008 at 6:23

[GoogleCodeExporter]

Original comment by matt.zuk...@gmail.com on 26 May 2008 at 6:23

• Changed state: Started