You need to send username and password in the request body as
application/x-www-form-urlencoded and not as URL request params.
Dmitriy.
Sent from my iPhone
On Apr 8, 2012, at 22:38, Tim Dalsing tdals...@vmware.com wrote:
Turned on DEBUG and got this in the logs:
2012-04-08 11:18:31,169
Hello all,
There is a possibility that we may have to integrate Shibboleth with our
existing CAS environment. How up2date is the Shibboleth-CAS documentation? I
also want to make sure that I understand how this will work (Shibboleth-CAS
integration). From reading the opening to the wiki
How up2date is the Shibboleth-CAS documentation?
If you're referring to
https://wiki.jasig.org/display/CASUM/Shibboleth-CAS+Integration, I
recently reviewed and updated it within the past 60 days.
As for your stated understanding of the behavior, it's correct. Note
that the CAS SSO
Unicon has done of bunch of these over the years and we usually
recommend turning off the Shib SSO auth handler so that only CAS
maintains the SSO session. This has the nice side effect of enabling
users to end the CAS/Shib SSO session via /cas/logout.
Ben, you might also be interested in an
We discussed on cas-dev months ago a proposal [1] to drop BDB support
for 3.5. I've created a Jira issue to move forward on the proposal:
https://issues.jasig.org/browse/CAS-1112
BDB support is slated for removal for two reasons:
- It's presumably not being used by a meaningful number of
Bill,
Many thanks for your reply. I hadn't heard of this project, so I am looking
into it now. I've also been reading about the CASShib project, but that seems
to be more of replace for CAS versus integrating Shibboleth into CAS. Not sure
which is going to be the best way to approach this
Greetings,
I'd be interested in hearing about other people's CAS integrations with
their account/password management systems. We're looking to more fully
transition from our homegrown single sign on solution to CAS, but we
still need to fill a few gaps. I'm going to look into the LPPE stuff
