ID FF 1.2 in Version 2.0 Beta: usage of LoadBalancer and SSL termination
"Hiller, Jochen" <[email protected]> Wed, 9 Mar 2005 08:57:35 +0100
| Newsgroups | gmane.comp.sourceid.sso.user |
|---|---|
| Message-ID | <[email protected]> |
Hello all,
we are using ID FF 1.2 in Version 2.0 Beta in following configuration:
(Use Courier-Font for correct view)
-----
| L | HTTP ---------- HTTP ---------
| O | ------> | Apache | -----> | jBoss |
------ HTTPS | A | | mod_jk | | |
| SP | -------> | D | ---------- ---------
------ | B |
| A |
| L | HTTP ---------- HTTP ---------
| A | ------> | Apache | -----> | jBoss |
| C | | mod_jk | | |
| E | ---------- ---------
| R |
-----
LoadBalancer will do:
- SSL Termination
- Dispatching
- Session stickyness via JSESSIONID
We got some problems when doing SSL Termination at LoadBalancer, and
using HTTP protocol only for further communication within Apchae, jBoss =
and the SourceID framework.
1. SoapEndpoint: AuthenticationFailure
- It will be checked, whether an SSL connection (via HTTPS) will be =
used.
If not, an exception will be raised.
2. SOAP Authentication via certificates
- Does a certificate based SOAP authentication will work in such a
configuration ? I assume NOT, if SSL termination will be done at
LoadBalancer.
Are there any standard approaches, how to configure such an environment?
Thanks a lot for any help!
Bye, Jochen Hiller