Hi James.
Would be nice to track your progress on this project. We have also
engaged with the two factor HOTP token CAS extention project recently.
The great place to share some code ideas, snippets, etc. would be
Github gists. I'm also planning to put some prototype working code as
we go along
Hi all,
After following the Setting Up CAS Locally using the Maven2 WAR Overlay
Method I was able to get CAS authenticating against Active Directory
and I was able to switch Tomcat from using a self signed cert to using a
CA issued cert and I have it successfully listening on port 443 instead
Copy the one from cas-server-webapp/src/main/webapp/WEB-INF into your
WEB-INF directory and then make your changes, compile and deploy.
On Thu, Apr 5, 2012 at 12:27 PM, Brian Gibson
gibson_br...@wheatoncollege.edu wrote:
Hi all,
After following the Setting Up CAS Locally using the Maven2
Hi,
Has anyone tried to integrate CAS with weblogic using SAML? Weblogic has a
SAMLAuthentication provider out-of-the box. We have to configure a partner
source ID parameter in weblogic which is a HEX or base64 encoded string of
the CAS URL. I am not able to figure out which URL I can use to
Has anyone tried to integrate CAS with weblogic using SAML?
Doubtful in the way that's implied from subsequent discussion.
We have to configure a partner
source ID parameter in weblogic which is a HEX or base64 encoded string of
the CAS URL.
Just a guess: try base-64 encoding the
Hi Marvin,
Thanks for your response. I am using SAML v1.1.
For the source ID I did try base-64 encoding of the /samlValidate URI, but
that didn't work. Actually, the source ID is the base-64 encoding of the
SHA-1 digest of the source URL. As mentioned earlier, I tried various URI
combinations to
