Copy link to clipboard
Copied
Did something change to how Purview works within Adobe recently ? When i opened a Purview locked document with Adobe Acrobat Reader, i still get the login info but when i log in nothing happens, it just stays stating ( We have Opened a new browser Tab for you to sign in ) but nothing happens, after awhile it times out and give me a " Client Application Failed to provide authentication token for HTTP Request " now our department cant only PDFs because it wont accept out logins anymore. I would like to post pictures but i dont have permission.
Copy link to clipboard
Copied
Hi,
Apologies that you are facing this issue.
Can you please help with few question.
1. Is this happening for all users?
2. Has this started happening after any recent update?
3. Has there been any updates on Microsoft client end you are aware of ?
Regards,
Abhinav Sethi
Copy link to clipboard
Copied
Just created an account to try and help you. I had the same issue on my tenant, the fix was to open at least ONCE a purview file from within Adobe.
As in, open Adobe, in the "recent files" or "File > Open", open the purview protected file. It should work. DO NOT click on the file directly on your desktop or in your downloads folder, for some unkown and weird reason it won't work.
No idea why, I'm loading up ProcessMonitor to try and understand what kind of difference in call it makes.
Copy link to clipboard
Copied
Bobby:
Thanks for the information on the potential workaround. Did you find anything else with your troubleshooting?
Absethi:
Has the root cause / fix been identified for this issue?
(Wwe are impacted by this as well)
Copy link to clipboard
Copied
Same issue here : Adobe Acrobat 64bits Purview labelling issue when ... - Adobe Community - 15032760
I have a sure way to recreate the problem 100% of the time (which is incredibly rare), it's been an issue for the past 3 months and still no answer from Adobe. Outside of being an Adobe Engineer, I doubt there's any way to fix this on the long term.
What they should do is start ProcMon64, recreate the issue and debug whatever's happening.
Find more inspiration, events, and resources on the new Adobe Community
Explore Now