+1I want to stream web site to Chromebox.
When I access from Windows 11, web site is displayed and I can sign-in.
From Appspace, I can access the web site but fails to sign-in.
The web site supporting browser is Edge, Chrome, and Safari.
What is Appspace web browser engine?
I would be grateful if someone can teach me how I can set the web site to Appspace streaming content
Best answer by Najil
Hi Kenichiro,
I Gemini'd your question and got some tips for you here below. Let me know if it works.
In the past I had some issues as well with but nowaways am only using a seperate SSO login card as the primary card in the channel. After that it loads a seperate card with the URL that shows the content.
------
On a Chromebox (ChromeOS), the underlying engine running the Appspace app is Chromium (Blink)—the exact same core browser engine used by Google Chrome and Microsoft Edge.
Even though the browser engine is identical to desktop Chrome, sign-in fails because Appspace renders external web pages inside an embedded Web View container or iframe, rather than a full browser tab.
Most modern web applications block sign-ins inside embedded web views for security reasons:
Anti-Framing Security Headers: Servers use X-Frame-Options: DENY or Content Security Policies (frame-ancestors) to block login pages inside web views.
SSO / Modern Auth (OAuth, SAML, Azure AD, Okta): Sign-in flows that rely on pop-up windows, multi-factor authentication (MFA), or cross-site cookies are blocked inside digital signage app containers.
Unattended Kiosk Limitations: Appspace playback is designed to run unattended; standard interactive form logins won't persist across player reboots without explicit token handling.
To get your web content streaming on your Chromebox, follow these configuration steps:
Log into your Appspace Console.
Go to Library > + Create > Cards and select the Web View card.
Enter your website URL.
Under Embed Options, test the following settings:
Native Webview (Default): Displays the site directly via the Chromebox browser.
XHR Proxy: Switches to an XMLHttpRequest proxy, which can bypass certain X-Frame-Options and cross-origin security blocks.
If the site uses HTTP Basic Authentication: Enable Basic Authentication (or Basic Auth via XHR) in the card settings and type in your username and password.
If your website uses Single Sign-On (SSO), form-based logins, or MFA, standard credentials won't work in a Web View Card. Use one of these industry standard solutions instead:
Option A: Use a Tokenized or Embedded URL (Recommended)
Ask your web developers or system admin to provide a public read-only URL, an embed token, or a URL with an API authentication key (e.g., [https://example.com/dashboard?token=xyz](https://example.com/dashboard?token=xyz)).
Option B: IP Whitelisting / Bypassing Auth for Signage
Configure the website server to bypass the login screen if the request originates from the specific public IP address or local network subnet of your Chromebox display.
Option C: Pre-built Appspace Integrations
If the website is a common business dashboard (such as Power BI, Salesforce, Google Slides, or Tableau), do not use the raw URL. Instead, use Appspace’s dedicated integration cards (e.g., Salesforce Card, Power BI Card) which securely handle OAuth authentication tokens in the background.
Kind regards,
+2Hi Kenichiro,
I Gemini'd your question and got some tips for you here below. Let me know if it works.
In the past I had some issues as well with but nowaways am only using a seperate SSO login card as the primary card in the channel. After that it loads a seperate card with the URL that shows the content.
------
On a Chromebox (ChromeOS), the underlying engine running the Appspace app is Chromium (Blink)—the exact same core browser engine used by Google Chrome and Microsoft Edge.
Even though the browser engine is identical to desktop Chrome, sign-in fails because Appspace renders external web pages inside an embedded Web View container or iframe, rather than a full browser tab.
Most modern web applications block sign-ins inside embedded web views for security reasons:
Anti-Framing Security Headers: Servers use X-Frame-Options: DENY or Content Security Policies (frame-ancestors) to block login pages inside web views.
SSO / Modern Auth (OAuth, SAML, Azure AD, Okta): Sign-in flows that rely on pop-up windows, multi-factor authentication (MFA), or cross-site cookies are blocked inside digital signage app containers.
Unattended Kiosk Limitations: Appspace playback is designed to run unattended; standard interactive form logins won't persist across player reboots without explicit token handling.
To get your web content streaming on your Chromebox, follow these configuration steps:
Log into your Appspace Console.
Go to Library > + Create > Cards and select the Web View card.
Enter your website URL.
Under Embed Options, test the following settings:
Native Webview (Default): Displays the site directly via the Chromebox browser.
XHR Proxy: Switches to an XMLHttpRequest proxy, which can bypass certain X-Frame-Options and cross-origin security blocks.
If the site uses HTTP Basic Authentication: Enable Basic Authentication (or Basic Auth via XHR) in the card settings and type in your username and password.
If your website uses Single Sign-On (SSO), form-based logins, or MFA, standard credentials won't work in a Web View Card. Use one of these industry standard solutions instead:
Option A: Use a Tokenized or Embedded URL (Recommended)
Ask your web developers or system admin to provide a public read-only URL, an embed token, or a URL with an API authentication key (e.g., [https://example.com/dashboard?token=xyz](https://example.com/dashboard?token=xyz)).
Option B: IP Whitelisting / Bypassing Auth for Signage
Configure the website server to bypass the login screen if the request originates from the specific public IP address or local network subnet of your Chromebox display.
Option C: Pre-built Appspace Integrations
If the website is a common business dashboard (such as Power BI, Salesforce, Google Slides, or Tableau), do not use the raw URL. Instead, use Appspace’s dedicated integration cards (e.g., Salesforce Card, Power BI Card) which securely handle OAuth authentication tokens in the background.
Kind regards,
+1Good morning!
This is a common point of confusion with Chromebox signage.
Browser engine on Chromebox
Why sign‑in may fail
Even though the page loads, the sign‑in step can fail if the site requires:
Chromebox signage often runs in a restricted or kiosk-style environment, which can block some login mechanisms.
How to set the website in Appspace
Things to check
+1Many thanks for reply.
The web site is not SSO enabled.
So, I think we cannot achieve “streaming web site requires ID/password credential”.
Many thanks for providing actual steps to try.
Regards,
ken
Already have an account? Login
Partners: If you do not have an Appspace login, please contact community@appspace.com for assistance.
Appspace Employees Customers and PartnersNo account yet? Create an account
Partners: If you do not have an Appspace login, please contact community@appspace.com for assistance.
Appspace Employees Customers and PartnersEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.
