We are trying to show a warning message for users who have passwords
expiring *soon*, displaying a link to change their password but also
allowing them to continue to the original service if they don't want to
change their password just yet. It seems the flow is running into an
infinite loop
I patched the CompressionUtils file and replaced the inflate function with
the one from 5.1.x and now GoogleApps is working again.
Was there a reason the function was re-written in the first place other
than trying to make it more efficient? I'm thinking of submitting a pull
request to revert
yes
###Token/JWT Tickets ENCRIPTION
cas.authn.token.crypto.enabled=true
cas.authn.token.crypto.signing-enabled=true
cas.authn.token.crypto.signing.key=
Dkkpi7iUKqidOXXmeAbr4RyHirYmgQgqqUrIo6q_JPNks2iqX2l95jVVoZQDWLNiFnhQF43agCtdMxRnIXOO9g
cas.authn.token.crypto.encryption-enabled=false
Has anyone managed to configure their Pulse Secure VPN as a SAML2 SP to use
CAS as a SAML2 IdP?
I've got (according to the documentation) all the configuration bits on the
Pulse Secure box set up, and I've put an entry into the CAS service
registry for a SAML2 service with the correct
Hi Dave,
Yes, we are using this combination: Pulse Secure VPN + CAS as SAML2 IdP and
it works well.
If this highlighted string from log is exactly the same as in your service
registry id then perhaps the problem is in question mark, it has to be
escaped:
As-Is: "serviceId" : "^
Thanks, Andres! That was exactly the problem.
--Dave
--
DAVID A. CURRY, CISSP
*DIRECTOR OF INFORMATION SECURITY*
THE NEW SCHOOL • INFORMATION TECHNOLOGY
71 FIFTH AVE., 9TH FL., NEW YORK, NY 10003
+1 212 229-5300 x4728 • david.cu...@newschool.edu
On Thu, Dec 13, 2018 at 10:43 AM Andres Rattur
Fortunately, Miami University is in a position to facilitate addressing
this issue. Thanks to the efforts of Unicon (https://www.unicon.net/) the
latest snapshot build of 5.3.7 appears to address this issue. If anyone
else is following this and can help test the Google Apps integration,
please do
I just reproduced the broken behavior using CAS 5.3.5 and 5.3.7-SNAPSHOT.
We are preparing to upgrade our CAS server but have not tested Google Apps
since our initial work with 5.2.x, when it did work correctly IIRC.
We are going to pursue pretty aggressively because it has major
consequences for
Posting to an old thread, but I too struggled to get attributes visible in
php
After making the following changes mine came through
If you have specified the CAS version in /etc/httpd/conf.d/cas.conf,
comment it out.
# CASVersion 2
CASValidateUrlhttps:///cas/samlValidate
You are welcome, David!
I would like to thank you for CAS Deployment step-by-step guide, it has
been a great help for me.
Kontakt David Curry () kirjutas kuupäeval N, 13.
detsember 2018 kell 18:12:
> Thanks, Andres! That was exactly the problem.
>
> --Dave
>
> --
>
> DAVID A. CURRY, CISSP
>
Hi,
The option `CASAuthNHeader On` must be configured in an .htaccess or a
directory/location directive. That will add headers that look like:
CAS_uid => mac
CAS_mail => mar...@mtu.edu
- Mac
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List
Jon,
The stanza, inquireInterruptAction, on 'no' goes to createTicketGrantingTicket.
But you have already created the ticket. It should go to
sendTicketGrantingTicket.
Same with finalizeInterruptFlowAction.
Ray
On Thu, 2018-12-13 at 06:42 -0800, Jon Li wrote:
We are trying to show a warning
12 matches
Mail list logo
