While testing CAS 7 (RC7), we encountered either a puzzling bug, or some
configuration effect we don't understand.
Normally, if we don't specify an application with for /cas/login, after
authentication we expect to be directed to a "Log In Successful" page for
an unknown target destination that
HI,
Looks like CAS already performed logout (TGC cookie is already removed)
before it redirect to Okta doing Logout, but it does not have a signature
element in Logout request sent to Okta.
Would that be a problem, even if Okta would recognize and log user out, it
will redirect back to CAS,
Just register the bean in Configuration
@Bean("authController")
public AuthController authController(){
return new AuthController();
}
在 2023/9/11 21:12, ztf863 写道:
Thank you very much for your reply. After my attempts, I found a
solution. By adding the controller's package path address
Trevor,
Test classes are not part of packaged jars. If you want test classes, you have
to copy them into your src directory.
Beware, you may have to copy in dependencies of the test classes too; and
remember to update them when you upgrade.
Is it possible to rework your logic to extend the
Thank you very much for your reply. After my attempts, I found a
solution. By adding the controller's package path address in the
configuration file
META-INF/spring/org.springframework.boot.autoconfigure.AutoConfiguration.imports,
the controller can be identified.
在 2023/9/8 23:22, Ray Bon
Hi All,
Just wondering if anyone has any ideas about the build errors?
Thanks
Trev
.
On Sep 8, 2023 at 9:48 PM -0700, Trevor Fong , wrote:
> Hi All,
> I'm trying to customize the AUP template view and some of the logic behind
> its SUBMIT button. The problem is that I'm running into some
