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; } } }

FV 3.0 Disable Secure Service Login

SimonRoss_User

I've already posted this to an existing post (http://forums.arcgis.com/threads/54640-FV-3.0-and-Login) but thought I'd open separately so there's no confusion.

Just started working with FV 3.0 and having some issues with the new login popup for secured services.

Our existing applications (FV 2.5) are secured via an ASP form control. Credentials for the secure services are built into the proxy page. Currently with the new secure services login this causes a separate challenge for authentication. Ideally I'd just like to disable the new secure services challenge but can't seem to make this happen in the flexviewer source code. I've tried removing the IdentityManager.instance.enabled = true but this makes no difference. I still get the popup appear. Any ideas on how to customize the viewer to remove this?
Thanks

Encontre mais publicações marcadas com

Accepted answers

HeatherGonzago

Hi Simon,
Could you try one thing for me please? It looks like there may be a slight typo in the source that may be causing the issue with proxies not being honored for layers.

Go to line 495 of MapManager.mxml and change

From:
layerObject.proxyURL = m_configData.proxyUrl;

To:
layerObject.proxyUrl = m_configData.proxyUrl;

Could you please try this out and let me know if this takes care of the problem? If not, then there may be something more that we are missing.

Thanks again,
Heather

All comments

DasaPaddock

Can you post your Viewer's config.xml?

SimonRoss_User

If the proxy is adding a token and no security error is returned to the client, then the IdentityManager should not be showing the sign in dialog.

Since creating an instance of the Portal also enables the IdentityManager, try adding this after line 45 of PortalBasemapAppender:

IdentityManager.instance.enabled = false;

Dasa - thanks for the response. I added this as directed and also set the instance of IdentityManager.instance.enabled to false in the ViewerContainer.mxml. Unfortunately this now causes a fault code 499 Unauthorized Access when the application launches and the layer cannot be accessed. For reference our proxy configuration has user name and password credentials embedded to generate a token at runtime - could this be causing the issue?

proxy.ashx, proxy.config

    <serverUrl url="https://MYDOMAIN/ArcGIS/rest/services"
               matchAll="true"
        dynamicToken="true"
        userName="USER"
        password="PASSWORD"
               host="SERVER_ID"
               ></serverUrl>
</serverUrls>

DasaPaddock

If the proxy is adding a token and no security error is returned to the client, then the IdentityManager should not be showing the sign in dialog.

Since creating an instance of the Portal also enables the IdentityManager, try adding this after line 45 of PortalBasemapAppender:

IdentityManager.instance.enabled = false;

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.