Is manual deletion of service ticket possible? Is there an api to do the
same?
Regards
Ajay
On Mon, Oct 20, 2014 at 8:52 PM, Ajay Madhavan wrote:
> Hi Carlos,
>
> I am trying to prototype a complete rest-based system.I do not expose the
> TGT rather expose only the Service ticket and increased
It might, yes, since the SLO callbacks are synchronous the job will block
until something comes out of the operation. Future versions of CAS do
support sending async requests out, and perhaps with a little bit of
modification you could make your deployment do so...or upgrade to a
version that does
Thanks for the advice on tuning the timeout parameters. We expected
the HTTP requests to fail for the unresolvable hosts, but our concern
is whether this would also block servicing subsequent requests from
other "normal" resolvable hosts until the requests for the unresolvable
hosts timed out.
Al
I came across this same issue when testing clearPass in our environment.
Is there a solution that I can implement to fix this issue so that I can
use clearPass in a clustered environment?
Root cause: javax.crypto.BadPaddingException: Given final block not
> properly padded
>
Thank you,
Adam
On
Hi,
For security reasons, service tickets cannot be reused and expire shortly
(10s by default). So that must be a *quick* manual testing or you must
change your service ticket lifetime configuration.
Best regards,
Jérôme LELEU
Founder of CAS in the cloud: www.casinthecloud.com | Twitter: @leleuj
I left only the AuthenticationFilter and manually testing doesn't work.
The log after authentication
15:39:00,925 INFO [org.jasig.cas.CentralAuthenticationServiceImpl]
(http--127.0.0.1-8443-1) Granted service ticket [
ST-10-bB15nrEOEfxcZcjzVLPC-cas01.example.org] for service [
https://localhost:8
Hi,
You can use the SAML endpoint, but the new /p3 endpoint is meant to avoid
the use of SAML and return the user atributes.
Sure it works by testing manually:
http://host/yourcas/p3/serviceValidate?ticket=ST-xxx&service=yyy?
Best regards,
Jérôme LELEU
Founder of CAS in the cloud: www.casinth
Hi Jérôme,
I haven't defined/modified anything on the CAS Server. The validation
filter on the webapp is defined so
CAS Validation Filter
org.jasig.cas.client.validation.Cas20ProxyReceivingTicketValidationFilter
casServerUrlPrefix
https://localhost:8443/
Hi,
What's the url of the defined endpoint for the service ticket validator?
Did you use the /p3 url?
Thanks.
Best regards,
Jérôme LELEU
Founder of CAS in the cloud: www.casinthecloud.com | Twitter: @leleuj
Chairman of CAS: www.jasig.org/cas | Creator of pac4j: www.pac4j.org
2014-11-05 11:42 G
On Wed, 05 Nov 2014 11:12:05 +0100
Federico Paparoni wrote:
> Map attributes = principal.getAttributes();
>
> Iterator attributeNames = attributes.keySet().iterator();
> for (; attributeNames.hasNext();) {
> String attributeName = (String) attributeNames.next();
> Object attributeValue = att
Hi all,
I have some problems with CAS 4 and attributes. I started a simple cas
server using maven overlay, but I didn't modify anything in the
configuration. Then I created a simple Java webapp and configured the
following filters
org.jasig.cas.client.authentication.AuthenticationFilter
org.jasig
11 matches
Mail list logo