In my application, the call to authorize (which blocks the entire application) takes 1-3 seconds
When copied as curl and executed in the command line it’s not faster
As you can see it’s all waiting on server response time. How can we debug this further?
Edit: It appears that the login flow actions are running even on silent auth. My understanding is that they aren’t supposed to be running here (they only show up in the logs until login, not silent auth)
tyf
May 23, 2024, 4:14pm
3
Hey there @anselsantosa welcome to the community!
Thanks for following up with this - Login Actions do indeed run for silent auth:
Problem statement
There are some actions in the tenant that call multiple APIs. Is there any way we could run these actions only once per session and not on silent auth calls or refresh token exchanges? Doing so would help to make our actions run faster.
Solution
In addition to running on a user’s login to start a session, Actions will also run on Silent Authentication requests and on Refresh Token exchanges. However, you can configure your actions to bypass these two other scenarios.
For Refr…
Thank you! this is super helpful. We will consolidate our actions and bail out sooner
1 Like
tyf
May 23, 2024, 5:33pm
5
No problem, happy to help!
1 Like
system
Closed
June 6, 2024, 5:34pm
6
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.