While that looks like it would address the issue, i believe I will wait as
my copy+paste'd solution works now. I really dislike the arbitrary nature
of CAS now, while the xml wasn't easy/fun, i definitely think we've gone
backwards now.
On Monday, September 24, 2018 at 11:51:48 PM UTC-4,
Hi,
I had to do something similar for the Password Management and did not want
to recreate everything. So the solution I came up with was to remove the
passwordManagementWebflowConfigurer from the execution plan and set the
order to one before my configurer and readd the
Hi Curtis,
Ah I missed to mention something,
when you tries to override a Bean inside a Configuration file, whether or
not is actually override success depends on the load sequence. Which one
load last will be the actual bean to be used.
See:
That is what i tried initially, but the transition from success to create
tgt was still happening. It wasn't until i removed it the , that i could
stop that transition, and instead send it to aup.
I believe the reason I couldn't just provide my own x509WebflowConfigurer
bean in loo of the
