Thanks Jerome but the problem is that I can't understand where I need Proxy
autenthication and why!
I mean: I access the app with spring plugin with my browser and it's local, the
app redirects me to CAS (deployed on the same server) and then CAS posts back
with the security ticket on the first
Hi Chitra !
Do you have any luck integrating JCaptcha with CAS 4 ?
If so please inform the steps to accomplish.
Thanks in advance,
Sunil
--
You are currently subscribed to cas-user@lists.jasig.org as:
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see
Daniel,
Please refer this thread for my working copy of deployerConfigContext.xml
Thanks,
Daniel
On Thursday, June 12, 2014 2:17:26 AM UTC+5:30, Daniel Salzedo wrote:
Sunil,
I am trying to do the same thing with CAS 4.0 in a lab environment. Any
chance of you posting your steps and
Daniel,
Please refer this thread for working copy of my deployerConfifContext.xml;:
https://groups.google.com/forum/#!topic/jasig-cas-user/vuQa4ZOuL4U
Thanks,
Sunil
On Thursday, June 12, 2014 2:17:26 AM UTC+5:30, Daniel Salzedo wrote:
Sunil,
I am trying to do the same thing with CAS 4.0
CAS 3.4 not is compatible with 3.5 and therefore 4 branch.
The solution is easier that that link explains and could valid for all
versions. When somebody don't know techologies behind frameworks, appears
solutions as you had applied in your CAS 3.4.
In fact, that AuthenticationViaFormAction
Hi, I am still attempting to get CAS to release attributes and not
having much luck.
My user goes to the the web site, logs in, and gets a 401 http code with
the message This server could not verify that you are authorized to
access the document requested. Either you supplied the wrong
(This is another attempt at posting using the Google Group. My last one
seems to have been bounced by Wisc. Apologies if this gets posted multiple
times somehow.)
I'm interested in using CAS with JBoss AS 7. Could someone recommend which
combination of server/client I should start with?
The exception I got appears to have been caught and handled by
CAS/OAuthAction. There's not much of a trace in the log.
OAuthAction.doExecute:
.
.
.
} catch (final TicketException e) {
return error();
}
cas.log
2014-06-16 18:07:07,023 INFO
You should use the 4.0.0 release of the server and the 3.3.1 release of the
CAS client.
And we should update our documentation :-)
On Mon, Jun 16, 2014 at 6:34 PM, Tom Arnold tar...@gmail.com wrote:
(This is another attempt at posting using the Google Group. My last one
seems to have been
I've updated our www.jasig.org/cas page.
Which wiki link was out of date?
On Mon, Jun 16, 2014 at 10:06 PM, Scott Battaglia scott.battag...@gmail.com
wrote:
You should use the 4.0.0 release of the server and the 3.3.1 release of
the CAS client.
And we should update our documentation :-)
10 matches
Mail list logo
