nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Search/Query widgets triggering generatetoken after upgrade to 11.4

TrevorH_OPE

We have recently upgraded from 11.1 to 11.4.

The search & query widgets for experience builder stopped working correctly and I noticed its trying to generate a token based on a token. This creates a 400 error.

Sometimes I'll see a result after a while but mostly it just sits there spinning.

Anybody seen this before?

Encontre mais publicações marcadas com

Accepted answers

TrevorH_OPE

We eventually figured this out ourselves. The problem was that the portal URL had been added to the Trusted Server setting in Portal for some reason (ie it referenced itself).

This had been done in our dev and test environments. Once we removed this, the issue/error went away.

All comments

JeffreyThompson2

I have not seen this one. But I suspect it may be related to a known issue. Please answer the following questions:

Are you using the version installed in Enterprise or connecting on Developer Edition?
Does your organization use SSO?
Do you have an Add Data Widget in your project? If so, check if it is connecting to Enterprise data?

TrevorH_OPE

Thanks for the reply. Its an interesting issue.

It is the version included with Enterprise 11.4, no it doesnt include the add data widget.

A new EXB app with a new Web Map has the same behaviour.

The site uses SAML but it happens with built in users too.

TrevorH_OPE

Actually its not specific to the widgets, even just opening the app results in the same behaviour.

We've logged a ticket with Esri.

AndreLoerch

I'm encountering this same issue using Experience Builder Developer version 1.16, with Enterprise data (map services) and access via SAML (SSO with Okta) in Portal. This issue so far seems to only impact me (the developer of the app) and not the other users of the app. We've deployed it in IIS.

I'm seeing hundreds/thousands of generateToken messages with the same response shared by the OP.

If this is or may be a known issue, I'd be grateful for more details on it. Thanks!

TrevorH_OPE

We’ve logged a ticket with Esri. So far no resolution.

TrevorH_OPE

We eventually figured this out ourselves. The problem was that the portal URL had been added to the Trusted Server setting in Portal for some reason (ie it referenced itself).

This had been done in our dev and test environments. Once we removed this, the issue/error went away.

Participe da Conversa

Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.

Links Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.