Looking within the element inspector of firefox, I believe this has to do
with the difference between a button "hold" on desktop and mobile
platforms. When holding the button on desktop, the input type for the
password field is changed from password to text until you let go of the
button. On
Hello,
I am running CAS 6.2.1 with SpringBoot 2.2.8 on tomcat 8.5.56 and java
openjdk 11.0.7 . I noticed when viewing the https://XX/cas/login page
on a mobile device, the "show password" button highlights slightly when I
press it, but it does not show the password. I was using an Iphone
You were right on the first guess,
Google was logging the user out, however, since CAS never properly saw the
logout, it could not destroy / invalidate the ticket. It turns out
something was entered incorrectly on Google's side. Once I changed the
logout URL to the /cas/logout endpoint, without
I haven't chased down logout operation. You're going to need to look, but I'm
guessing that they are getting logged out on the Google side, but an SSO
session is still active in the IdP? Or is it after logout it isn't doing a
logout on Google side?
On Mon, 2020-08-17 at 08:29 -0700, Jeremiah
Richard,
I've got one more question for you.
First, I'd like to say that all of the sign-in procedure worked perfectly,
so thank you for that.
The only problem I have now is with the logout URL on Google. Before we
could set up the SSO, we had to enter a logout URL for Google to use. At
Hi,
Yes, I use PostgreSQL to store services and tickets.
I actually try to use LDAP to auth my users in CAS Management, but actually
it doesn't work :
WARN [org.apereo.cas.mgmt.authz.CasRoleBasedAuthorizer] - Unable to
authorize access, since the authenticated profile [#CasProfile# | id:
Hi Mr Julien Sabatier,
I have read your cas-management configuration and I guessed your
cas-management authen user from LDAP and store service registry to
PostgreSQL.
Is that right?
You resolved your problem.
Can you show me your cas-managment, cas-overlay and service registry in
detail?
Thank you
I solved the problem. It was that I didn't added
"cas-server-support-discovery-profile" to my CAS dependencies at
compilation, so the discovery service wasn't available.
Thanks for your help.
Now my problem is that I want to use ldap for CAS Management auth, and for
this I need to include
You probably aren't waiting long enough?
2020-08-17 09:06:54,686 DEBUG [org.apache.http.impl.execchain.MainClientExec] -
Executing request GET /actuator/discoveryProfile HTTP/1.1
It's trying to make a connection to your CAS system. Looks like from your logs
it hasn't time out, and thus hasn't
Dirk,
Does attribute release still work for you after including impersonation? It
breaks for us after including surrogate-webflow for cas 5.3.5. If it works,
could you tell me what changes are needed?
Thanks
Aditi
On Wednesday, January 9, 2019 at 9:29:37 PM UTC-5, Dirk Tepe wrote:
>
> We are
I try to setup a CAS Management to manages services of my CAS instance.
But when I launch the webapp, it's like it freeze on startup, and I can't
access it in my browser.
CAS Version : 6.2.1
CAS Management Version : 6.2.1
Here is my /etc/cas/config/management.properties :
11 matches
Mail list logo
