Dear James,
> I am trying to find a way to completely customize CAS login view
Do you mean customize the *layout *(i.e. HTML, css, javascript), or do you
mean customize the *login logic* (i.e. login using Database / LDAP / other
mechamism...)?
If you want to customize layout:
- try
this:
Thanks, Misagh. The first line did the trick!
-Dustin
On Wednesday, May 15, 2019 at 11:33:15 AM UTC-7, Misagh Moayyed wrote:
>
>
> https://apereo.github.io/cas/5.3.x/installation/Configuration-Properties.html#protocol-attributes
>
> cas.authn.releaseProtocolAttributes=false
>
https://apereo.github.io/cas/5.3.x/installation/Configuration-Properties.html#protocol-attributes
cas.authn.releaseProtocolAttributes=false
cas.authn.authenticationAttributeRelease.neverRelease=A,B,C,D
--Misagh
> From: "Dustin Luck"
> To: "CAS Community"
> Sent: Wednesday, May 15, 2019
I have set up an SP in my service registry in CAS 5.3.2. All of the
attributes I have included via the attributeReleasePolicy are being
included in the response, however, many attributes that I didn't specify
are being included as well. This is causing an error with the SP because
the
James,
If you want to change the look of the login page there is
https://apereo.github.io/cas/6.0.x/ux/User-Interface-Customization.html#
If you want to add a new authentication mechanism then you will have to modify
web flow,
Alain,
There are two connection errors in the log:
Error connecting to LDAP URL: ldap://ForestDnsZones.test.univ-bfc.fr:389
Error connecting to LDAP URL: ldap://DomainDnsZones.test.univ-bfc.fr:389
Where do they come from?
Your config is pointing to 192.168.0.54! And this shows up in earlier log
Hello everyone,
I am trying to find a way to completely customize CAS login view. We have
some complex view customization work to do, for example, let users to login
via scanning QR code, etc.
After searching, I found this:
Thanks - per Duo Status everything seems up: https://status.duo.com/
but it seems to be an error on their end since we haven't changed anything
on our side. Even with Debug logging on though I'm not seeing much of
anything that would indicate an error with Duo other than the original log
I
It's working fine for us (CAS 5.2.x).
That error looks familiar though... I won't swear it's the same one, but
there was an outage a couple of months ago too, and that was a problem on
the Duo side.
--Dave
--
DAVID A. CURRY, CISSP
*DIRECTOR OF INFORMATION SECURITY*
THE NEW SCHOOL • INFORMATION
Forgot to mention CAS version is 5.3.6.
On Wednesday, May 15, 2019 at 9:50:03 AM UTC-5, J Truts wrote:
>
> Without having made any changes to our CAS application servers or services
> today Duo MFA challenge is no longer being presented after logging into CAS.
>
> We opened a call with Duo as
Without having made any changes to our CAS application servers or services
today Duo MFA challenge is no longer being presented after logging into CAS.
We opened a call with Duo as well but haven't heard anything.
I did notice this error in the logs:
2019-05-15 07:45:04,820 WARN
Va,
I would like to mention that your complaint is about a product that you get
to use *for free*. I support some paid software with worse documentation. I
do understand the frustration, as the learning curve is steep, but that's
where this community comes in. Everyone here tries to be very
As I see after almost 2 years documentation still don't getted better ...
... there are no some 1-2-3-Specs to finish even HelloWorld with CAS. But
the release number grows extremely. 3.6, 4.0-1-2-3, 5.0-1-2-3, 6.0.
So - looks like the developers stacked in the similar way as users :)
I
Thank you Martin.
I have repeated tests, you are right, the autocommit=true is the definitive
solution to the problem.
Il giorno sabato 11 maggio 2019 15:09:08 UTC+2, Martin Böhmer ha scritto:
>
> I experienced the exact same behaviour and solved it by setting autocommit
> = true. Don't
14 matches
Mail list logo
