Embedded app - private using API

I have a working POC written in .NET which successfully retrieves an access token and embed token for my Domo App. I am then following model of creating an iframe and setting the source to:
const source = "<html>\n" +
" <body>\n" +
" <form id=\"form\" action=\"" + embedUrl + "\" method=\"post\">\n" +
" <input type=\"hidden\" name=\"embedToken\" value=\"" + embedToken + "\">\n" +
" </form>\n" +
" <script>\n" +
" document.getElementById(\"form\").submit();\n" +
" <\/script>\n" +
" </body>\n" +
"</html>\n";
This was working last week. My Domo domain was changed, and now I get a
Sorry. This content is no longer available.
error. I created a new client, still no luck. The allowed domains are still set and still accurate. What else should I check for?
Answers
-
Tokens are domain specific. If your domain changed, you need to make sure you regenerate access and embed tokens for the new domain. And allowed domains are set.
You say you created a new client and allowed domains are still set. Are you referring to the embed and settings for Domo Everywhere?** Was this post helpful? Click Agree or Like below. **
** Did this solve your problem? Accept it as a solution! **0
Categories
- All Categories
- Product Ideas
- 2.1K Ideas Exchange
- Connect
- 1.3K Connectors
- 309 Workbench
- 7 Cloud Amplifier
- 10 Federated
- Transform
- 664 Datasets
- 120 SQL DataFlows
- 2.3K Magic ETL
- 824 Beast Mode
- Visualize
- 2.6K Charting
- 88 App Studio
- 46 Variables
- Automate
- 195 Apps
- 486 APIs & Domo Developer
- 93 Workflows
- 24 Code Engine
- AI and Machine Learning
- 23 AI Chat
- 4 AI Projects and Models
- 18 Jupyter Workspaces
- Distribute
- 119 Domo Everywhere
- 283 Scheduled Reports
- 11 Software Integrations
- Manage
- 143 Governance & Security
- 11 Domo Community Gallery
- 49 Product Releases
- 13 Domo University
- Community Forums
- 41 Getting Started
- 31 Community Member Introductions
- 116 Community Announcements
- 5K Archive