Thanks Ray, I owe you a case of what ever your vice is by now.
In retrospect it makes sense now. The service ticket was being searched for
in the requestScope as the log reflects:
2023-08-08 15:25:26,057 DEBUG
[org.apereo.cas.web.flow.GenerateServiceTicketAction] - https://localhost:8443] and
Pablo,
There are a number of maps associated with the web flow.
You can put to one of the maps, if needed. From your action class you can see
their contents:
// authn attributes contains encrypted credential
// LOGGER.debug("auth attribs Map: " +
It looks like I'm losing the request scope, or at least the service ticket:
2023-08-08 15:25:26,057 DEBUG
[org.apereo.cas.web.flow.GenerateServiceTicketAction] - https://localhost:8443] and added it to the
request scope>
2023-08-08 15:25:26,057 DEBUG [org.apereo.cas.web.flow.MyCustomAction] -
Hi Ray, looks to be a self inflicted issue.
We have a custom login webflow and have injected as view between
generateServiceTicket and Redirect action/view states. When I disable this
custom step all works fine. I haven't been able to trace my issue but it is
my issue.
-psv
On Thursday,
Pablo,
What version of Cas is this?
Check your logs. The audit log records the authentication events, including
ticket creation.
Ray
On Wed, 2023-08-02 at 14:39 -0700, Pablo Vidaurri wrote:
Notice: This message was sent from outside the University of Victoria email
system. Please be cautious
I am seeing a problem where after a successful login a redirect is happing
back to the service URL but does not have a ticket=ST- query parameter.
This of course means that the service has no ticket to go validate. But if
I hit the login page again, i get the ticket on the 2nd try.
1)
