Guess: start using file: in front of the path and try to avoid using back
slashes. They have cost humanity many lives.
--Misagh
From: cas-user@apereo.org [mailto:cas-user@apereo.org] On Behalf Of satnam
Sent: Tuesday, November 15, 2016 3:30 PM
To: CAS Community
Probably the cleanest way of doing this is to create RunAsManagers. One to
convert an OAuth2Authentication to a CasAuthenticationToken and one to do
the opposite.
Does anyone think that this is the correct method?
On Tuesday, 15 November 2016 16:11:02 UTC, Dmitriy Kopylenko wrote:
>
> That
That would probably be a question for Jérôme
D.
From: Lewis Henderson
Reply: cas-user@apereo.org
Date: November 15, 2016 at 10:04:13 AM
To: CAS Community
Cc: lewis.hender...@cobraflow.com
This is probably the least tested bit of the saml2 feature. Do open up an
issue, and provide your config and CAS logs so we can better diagnose this.
--Misagh
From: cas-user@apereo.org [mailto:cas-user@apereo.org] On Behalf Of Robert
Kornmesser
Sent: Tuesday, November 15, 2016 3:17 AM
To:
There’s this factory API you could try:
https://github.com/apereo/cas/blob/master/support/cas-server-support-oauth/src/main/java/org/apereo/cas/ticket/accesstoken/AccessTokenFactory.java
D.
From: Lewis Henderson
Reply: cas-user@apereo.org
When I declare it as below, CAS still use its UsernamePasswordCredential.
I could use MyUsernamePasswordCredential only if I change the var name in
the login-webflow and loginform as below :
However this lead me to another problems like :
java.lang.IllegalArgumentException: No
Everything is Spring Cloud based.
I have a CAS 5.0.0 service sitting behind a Zuul Gateway.
All the OAuth secured applications work properly!
I have an external CAS client that needs to talk to an OAuth resource
server behind Zuul via a proxyTicket.
The CAS client successfully authenticates
Hi,
First off thanks to Dmitriy and Travis for your help with my Duo question;
moving to version 5.0.0 would be what I would want to do but I think I have
a legacy dependency problem that I need to sort out before I can.
Currently I'm working to migrate an old CAS 3.5.2 installation to
Hi all,
I am successfully running a CAS 5.0.0 with SAML IdP. I can authenticate
against shibbolized service providers as long as i am not encrypting
assertions. When i activate "encryptAssertions" in my service i get this
error:
A valid authentication statement was not found in the incoming