Hi,
I implemented DWA (DIrect Web Access) assignment to send a form to the company external clients without access to our Pega platform 8.5.
The problem that I’m facing is that one client can’t open more than one DWA form in one session of the browser. They have to always use incognito mode which obviously we can’t require from external partners.
After one DWA assignment is submitted all the following ones opened in a browser got the error:
Access denied#### This request for information cannot be processed (another request is currently being processed).
The case is set to allow multiple users but anyway each for is a different case so the DWA assignment.
I found this article:
But it seems nothing has changed since then.
I found this article as well:
But my implementation uses PerformExternal harness.
Thanks for any advice
Paweł
@PawelAdamczuk FDBK-9093 was closed with no action.
Did you already check this support article ‘DWA session locks when user exits using browser close option’?
Can you confirm whether you have configured the anonymous user authentication for assignment submission through Directed Web Access, to allow the user to open the multiple assignment URLs in same session?
Please see: Handling external assignments in Pega | Support Center
@MarijeSchillern thanks for your reply.
I followed the instruction but it didn’t work for me. Still the same behavior.
ActionExternal:
CloseAndLogOff:
LogOff activity is slightly different than in the article. I use Pega 8.5.5
@MarijeSchillern
it worked!! 
I just had to create the authentication service and create links with the approach from the article
https://wiki.pega.com/index.php/Handling_External_Assignments_in_Pega
I missed that when I previously replied to your post.
Thank you very much!!
@PawelAdamczuk
For people who will struggle with the same issue in the future. What in fact worked for me wasn’t the PDN article but tips from wiki page and especially 2 points: creation of authentication service, different way of link generation including authentication service name in URL and external assignment key.
I removed all rules described here and it was still working fine.