Following up from this, I was able to get SPNEGO+Duo-MFA working by
making sure that the SPNEGO webflow is ordered before DuoSecurity webflow.
Specifically, I modified the WEBFLOW_CONFIGURER_ORDER from 0 to 50 in
DuoSecurityAuthenticationEventExecutionPlanConfiguration
private static final in
Running into two issues I could use some help with:
First - in 6.1.2 if I build w/ Hazelcast and Hazelcast AWS Discovey via
the gradle overlay and have discovery enabled,
enabled(cas.ticket.registry.hazelcast.cluster.discovery.enabled=true) I
get the following stack trace:
2019-12-16 12:46:5
nks in advance for any help!
Matt Elson
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message because you are subscribed to the Google Groups "CA
Oops, forgot to mention the CAS version I'm running: 6.1.5.
(Haven't gotten around to seeing if the behavior persists in the 6.2.0
release candidates, planning to sometime this week.)
Matt
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidel
Maybe that's a defect if the default XML is invalid when including all
attributes?
BTW - I am still looking for advice or best practices for validating
using email and/or username when using LDAP.
Not sure if best practice or not, but I have a similar requirement and
fulfill it by adjustin
right when combined w/ trustedDevice.
I'm sort of new to Java webflow (and not really a programmer), so not
quite sure if I'm understanding the interactions correctly - I don't
mind digging into code to try and learn more, but not quite sure where
to begin since it's all qu
> In any case, any help would be appreciated!
Just noting for future people potentially stumbling on this that this
got fixed up in 5.1.3 (commit 29d4fd6388969820e4631b2a2693cb8116a36f98
would be my guess).
The flow is going to the right place and the in memory storage is
working fine.
However,
On 08/15/2017 04:47 PM, Matt Elson wrote:
> Both look like the SQL statements are getting incorrectly formed or
> truncated in some format; going to be firing up more debugging on
> mariadb/mysql side of things and will try other DBs later.
>
> Just figured I'd throw it o
