Forum Discussion
APM session status remains pending after policy completion
Environment: 12.1.1 HF2
I have an APM policy that is working fine to authenticate my users against my local ActiveDirectory store. Yesterday I modified the policy ending for the successful path to use the "Redirect" ending to drop my users to a specific page, instead of the previous "Allow" ending. I've noticed that now when I check the list of active sessions, they all remain in Pending status after policy completion instead of Established.
The only difference I can see in the APM log with regards to the different behavior is that the Access policy result is set to "Redirect_Allow" instead of "LTM+APM_Mode" like it used to be. Is this expected behavior for the status of the session in APM with a redirect ending? Are there risks to letting the sessions remain in Pending status?
Thanks, Jen
1 Reply
- dubdub
Nimbostratus
I reverted to using the "Allow" ending on my policy and added this handling in my iRule:
when ACCESS_POLICY_COMPLETED { if { [ACCESS::policy result] eq "allow" } { ACCESS::respond 302 Location /a/b/c } }That keeps my sessions in the expected "Established" mode and achieves the same end result.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com