Skip to main content
json1
Level 2
Oct 27, 2026 1:27 PM UTC
Question

Request approval for secure web links

Is the recent release to request approval on the live web page the same way you request approval on an uploaded file supported for secure sites (i.e., links that require login or SSO authentication)? In initial testing secure links either could not be displayed or only partially rendered in the Frame.io reviewer with the Chrome extension installed.

3 replies

Kurt_Jones
Adobe Champion, Community Advisor, UG Leader
Kurt_JonesAdobe Champion, Community Advisor, UG Leader
Adobe Champion, Community Advisor, UG Leader
Oct 27, 2026 2:54 PM UTC

Not fully sure I understand your question, however, the user would need to have access to the link (secured or otherwise) to be able to see and approve it.

Translate
If my response answered your question, please mark it answered, so others can find the answer
json1Author
Level 2
Oct 27, 2026 5:15 PM UTC

I’m testing approval workflows using the new “Add a web link as a document” feature. Sites that require authentication do not display properly to users who have access.  https://experienceleague.adobe.com/en/docs/workfront/using/product-announcements/product-releases/release-26-q4/26-q4-documents

Translate
Russ_Nelson
Russ_Nelson
Level 2
Oct 28, 2026 5:25 PM UTC

Short answer: some secured sites will work and some won’t. The limit is usually in how the page gets rendered for review, not in the Workfront approval workflow.

The 26-Q4 web link approval depends on the Frame.io integration. The release note says it isn’t available in the Preview sandbox for that reason. Frame.io’s web review loads the live page in a frame, and its HTML Review article lists the conditions:

  • The site has to allow iFrame embedding. Many login-protected apps and intranets send X-Frame-Options or a Content-Security-Policy frame-ancestors header that blocks it. That usually shows up as the blank or half-rendered frame you’re seeing.
  • Private URLs are supported, but “certain authentication flows may not work depending on server configuration.” SSO flows that bounce through an identity provider are the usual culprit.
  • Some private and restricted URLs need the Frame.io browser extension, and it’s Chrome only.
  • Admins can allowlist redirect domains in Frame.io’s Content Security Settings. That helps sites that need a redirect to finish signing in.

What I’d check, in order:

  1. In dev tools on the target site, look at the response headers for X-Frame-Options or frame-ancestors. If those block framing, no extension will fix it. The site owner would have to allow Frame.io, which is often doable on a staging host.
  2. Make sure every reviewer has the extension installed and is already signed in to the site in the same Chrome profile.
  3. If sign-in redirects through Okta, Entra or similar, have your Frame.io admin add those domains to the redirect allowlist.
  4. Test in Production, not Preview, because the feature isn’t available in the Preview sandbox.

If the site can’t be framed, the fallback is a staging copy that allows framing, or a zipped HTML build. Zip HTML is supported for interactive review today.

Translate
Russ Nelson, Founder, Prolifico Digital
    Terms & ConditionsAccessibility statement

    Loading footer...