Hi,
We have some old code in our CAS implementation which is essentially swapping
out the username specified by the server with an internal user id we use
throughout applications.
I’m playing with CAS 4.0 RC2 and am very happy that I now can remove all this
code and use built-in attribute mapping with service registry to achieve the
same thing.
However. The CAS 1.0 protocol does not respect the setting in the service
registry. Since I’m afraid that we may actually have some old hacks that are
using 1.0 validation, I still have to modify this view, but I wonder if this
really shouldn’t be the default behavior? It is a minor change.
Any thoughts?
@@ -50,7 +51,7 @@
if (this.successResponse) {
response.getWriter().print(
"yes\n"
- +
assertion.getChainedAuthentications().get(0).getPrincipal()
+ + assertion.getPrimaryAuthentication().getPrincipal()
.getId() + "\n");
} else {
response.getWriter().print("no\n\n");
Best regards,
/Fredrik
--
Fredrik Jönsson, M.Sc. Email: [email protected]<mailto:[email protected]>
System architect Phone: +46 8 790 66 03
Kungliga tekniska högskolan (KTH) Mobile: +46 73 595 66 03
KTH/UF/ITA/Infosys
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-dev
