-
Title
The access request id is currently available for use and cannot be acknowledged at this time -
Description
After upgrading to SPP 7.4.x, the checked out sessions are remaining in the users list after they expire. Additionally, when users try to close the access request out, the following error appears:
The access request id (Request_Id) for (account) is currently available for use and cannot be acknowledged at this time. (90102)
Users were able to clear it by requesting a new session, then the old one becomes available to remove. -
Cause
Issue can happen when:
1- The "Close Expired Sessions" flag is enabled on the Access Request policy in SPP.
Or
2- There has been an error with communicating with SPS such that SPP doesn't realize that a session is terminated. -
Resolution
STATUS:
Change request # 438619 is fixed in SPP version 7.5, please upgrade to address this issue.
WORKAROUND:
1. Remove the "close expired sessions" flag on all Access Request Policies that have this enabled
- You can use the safeguard-ps module to run the following example script to disable the "close expired sessions" flag on all Access Request policies:$arp = Get-SafeguardAccessPolicy ForEach ($i in $arp) { $policy = Get-SafeguardAccessPolicy -PolicyToGet $i $policy.AccessRequestProperties.TerminateExpiredSessions = $false $id = $policy.Id write-host $policy.Rolename write-host $policy.name invoke-safeguardmethod core put "AccessPolicies/$id" -Body $policy }2. Reboot the Primary appliance.
3. You will need to close any Pending Password Reset requests:
- Using the SPP Web UI: Security Policy Management > Access Request Activity > Open Requests > In the search field click on the Search icon > Filter by State: Pending Password Reset and close these requests.
OR
- Using Safeguard-ps module and an example script below:$accessrequest = Get-SafeguardAccessRequest $accessrequest |? {$_.state -eq 'Pending Password Reset'} ForEach ($i in $accessrequest) { $id = $accessrequest.Id Close-SafeguardAccessRequest -RequestId $id }
Important note: The issue will return if you do not remove the "close expired sessions" flag from access request policies or upgrade to the next release version 7.5 when it becomes available.