Hi Everyone,
We have setup an application to reply on a passed in proxy ticket to
authenticate through CAS. An INVALID_TICKET XML response is received by
the phpcas because the ticket is not recognized. However, when we look in
the CAS logs in debug mode, we can see clearly that the
DefaultT
So many thanks.
Now it's working.
Am Freitag, 3. Februar 2017 13:39:46 UTC+1 schrieb Menno en Erla Avegaart:
>
> That error explains it. cas-management needs to contact the CAS server to
> validate the ticket, but it doesn't trust the SSL certificate on
> https://cas.
>
> Configure server.ssl.t
I'm looking for a way to invalidate a current user session.
Use case is the Admin that want to kill a user session.
(Looking for a way CAS invoke the Single Logout BACK CHANNEL URL on all
registered ST)
Thanx.
--
- CAS gitter chatroom: https://gitter.im/apereo/cas
- CAS mailing list guidelines
Setting aside the question of whether this is a good idea and answering the
literal question of why it doesn’t work, the CAS login is coded in Spring
Webflow. There is an initialization step and then a sequence of test (like is
the user already logged in with a CASTGC cookie, and only after that
Quick update: testing this a bit more I did find a few anomalies. I’ll put
aside some time to review and apply fixes and if you want to track progress,
do please open up that issue.
Thanks.
--Misagh
From: Misagh Moayyed [mailto:mmoay...@unicon.net]
Sent: Friday, February 3, 2017 2:34 PM
Hey dkopy..., thank you for replying. I am using the Maven overlay, and
yes, I have included the dependency in pom.xml, as stated from the site (
https://apereo.github.io/cas/5.0.x/installation/Database-Authentication.html).
I have also added the JDBC driver dependency, and checked if the jar f
Hey dkopy..., thank you for replying. I am using the Maven overlay, and
yes, I have included the dependency in pom.xml, as stated from the site (
https://apereo.github.io/cas/5.0.x/installation/Database-Authentication.html).
I have also added the JDBC driver dependency, and checked if the jar fil
Hey dkopy..., thank you for replying. I am using the Maven overlay, and
yes, I have included the dependency in pom.xml, as stated from the site
(https://apereo.github.io/cas/5.0.x/installation/Database-Authentication.html).
I have also added the JDBC driver dependency, and checked if the jar fil
If you put parameters like that in the URL, it'd be a HUGE security
risk...username and password would be stored in cleartext in browser history,
server logs, possibly firewall/load balancer logs, etc.
There is this workaround that you can do though; this hasn't been tested with
CAS 5, but does
1. I configured security.basic.path=/cas/status/** and it triggers for
Spring Boot endpoints (e.g. /cas/status/health), but it doesn't for
/cas/status/dashboard. Am I missing a config option somewhere?
Possible. Difficult to say without seeing what the config looks like.
2. Are Spring Boo
That error explains it. cas-management needs to contact the CAS server to
validate the ticket, but it doesn't trust the SSL certificate on
https://cas.
Configure server.ssl.trustStore (or put the certificate in the key store
you already configured).
Op vrijdag 3 februari 2017 13:12:09 UTC+1 s
Hi,
1. I configured security.basic.path=/cas/status/** and it triggers for
Spring Boot endpoints (e.g. /cas/status/health), but it doesn't for
/cas/status/dashboard. Am I missing a config option somewhere?
2. Are Spring Boot endpoints like /cas/status/health supposed to work?
3. Yes, but if you
Oh yes sorry.
I get the following error:
No i have no registered the service.
Can you tell me, how i register it?
Thanks
Am Freitag, 3. Februar 2017 12:56:10 UTC+1 schrieb Menno en Erla Avegaart:
>
> And, any errors in the CAS log?
>
> Did you register the management URL in the CAS service
Have you included CAS' JDBC authentication module dependency in your overlay's
build config (Maven or Gradle)?
Best,
D.
On Feb 3, 2017, 03:04 -0500, Jihad Talic , wrote:
> Hello,
>
> I am experiencing issues regarding my Database authentication configuration
> in my CAS 5.0.1 server. The databa
1. Only the Spring Boot security endpoints trigger authentication, but
the classic CAS status pages (e.g. /cas/status/dashboard) do not. This means
there is no way to access them, unless you disable Spring Security and use
cas.adminPagesSecurity again.
You’ll need to map the endpoints in th
And, any errors in the CAS log?
Did you register the management URL in the CAS service registry?
Op vrijdag 3 februari 2017 12:09:45 UTC+1 schreef Sebastian Wilde:
>
> Yes i mean "too many redirects".
>
> Sorry
>
> Am Donnerstag, 2. Februar 2017 16:03:49 UTC+1 schrieb Menno en Erla
> Avegaart:
You don't *need *to use the cas-management UI to set it up.
You do need to set an attributeReleasePolicy in the services .json file.
(You also need to specify the attributes to be returned somewhere per
previous responses).
It's the Spring side that I found most confusing. Below is an excerpt from
Yes i mean "too many redirects".
Sorry
Am Donnerstag, 2. Februar 2017 16:03:49 UTC+1 schrieb Menno en Erla
Avegaart:
>
> What do you mean with a "redirect error"? Did you mean "Too many
> redirects"?
>
> Do you see any errors in the CAS log?
>
>
>
>
--
- CAS gitter chatroom: https://gitter.im
You could maybe get it from an environment variable and set that per
environment eg
http://stackoverflow.com/questions/23711541/get-spring-application-environment-in-thymeleaf
If that doesn't work another way to get it would be to write a custom bean
under org.apereo.cas.web.flow that got the envi
I'm testing the new Spring security integration in CAS 5.1.0-RC2-SNAPSHOT
and fail to get it working.
Before I post this as a bug report I would like some feedback, because it
fails so completely that I think I'm missing something...
My issues so far:
1. Only the Spring Boot security en
In Tomcat's conf/server.xml you'll have a tag. You can specify
the keys and ca-cert Tomcat will use there eg :
SSLEnabled="true" scheme="https" secure="true"
>sslProtocol="TLSv1.2"
> keystoreFile="C:\some_path\certs\keystore.p12"
keystoreType="PKCS12" keystorePass="your password"
>
https://github.com/apereo/cas/issues/2347 Friday, 03 February 2017, 11:14AM
+01:00 from kaphaelm kapha...@gmail.com :
>Hi,
>
>My bad, I didn't provide Authorization header...
>OIDC works fine now with Shiro authentication.
>
>But when I use trusted authentication with OIDC protocol I get an err
Hi,
My bad, I didn't provide Authorization header...
OIDC works fine now with Shiro authentication.
But when I use trusted authentication with OIDC protocol I get an error for
the /authorize endpoint.
The error occurs after the authentication (I have an
"AUTHENTICATION_SUCCESS" in the logs)
He
Thanks for the diagnosis. Could you open up an issue, attach your metadata,
your pub cert and describe the change you made? That way we can begin to
duplicate the issue. I am almost sure it's a bug in the code. Thursday, 02
February 2017, 10:38PM +01:00 from Todd Pratt pratt.t...@gmail.com :
Hello,
I am experiencing issues regarding my Database authentication configuration
in my CAS 5.0.1 server. The database I'm connecting with my CAS server uses
PostgreSQL, and deploying the overlay build in Tomcat 8.5. First of all, I
have enabled Database Authentication in the application.prope
25 matches
Mail list logo
