Yan,
Fix the error first. It could be eating the parameters. Return to default login
flow and try again.
Are you sure your authentication handler is correct?
Ray
On Wed, 2019-02-06 at 14:28 -0800, Yan Zhou wrote:
I think the log may help better. I do not believe CheckLoginUserAction has
anyth
I think the log may help better. I do not believe CheckLoginUserAction has
anything to do with it, because it only comes into the picture if authN is
successful.
I just enabled debug logging, the stacktrace below is only because I
entered incorrect credential. Notice that my URL had service pa
Yan,
The log in flow that exists when CAS is running is considerably more complex
than the xml file that is in the code base. A number of features will modify
the flow.
It may be possible that your 'checkLoginUser' is not being executed where/when
in the flow you think.
I have a gist,
https:
Hi,
I made some customization on the login flow, see all login related
code/configuration below.
I read this in CAS 5.3.X documentation: If “service” was specified to
*/login*, “service” MUST also be a parameter of the form, containing the
value originally passed to */login*.
Is this say
Yan,
Can you post your code?
Ray
On Wed, 2019-02-06 at 10:00 -0800, Yan Zhou wrote:
Hi there,
I extended CAS 5.3.4. The app. redirects to CAS login page with service
parameter.
When I type incorrect credential, I saw the invalid credential message, but I
lost service parameter, the screen r
Hi there,
I extended CAS 5.3.4. The app. redirects to CAS login page with service
parameter.
When I type incorrect credential, I saw the invalid credential message, but
I lost service parameter, the screen refreshes to have only the CAS url.
What could be missing in my code?
Thx!
--
- Webs
