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

Flex Viewer 3.2 GP Widget upload using 10.1.1 returns 'token required'

ZacharyHart

Flex Viewer 3.2
installed on ArcGIS Server 10.1.1
Secured services; map services access fine, adding and configuring the GP service to the widget goes fine
When attempting to navigate to a local file for upload, after file is selected, the error 'token required' is returned.

GP service & map services secured with the same authentication credentials; no proxy used in the application; all other secured services are accessible as expected.

Vind meer berichten getagd met

Accepted answers

All comments

gisgeeknorth

Hi,

I am having a related problem with version 3.6 of the Flex Viewer. I have token secured GP services. Server is 10.1.1. When I try to access them form the GP Widget, I am first prompted to login. When I cancel that, t he widget then appears, but when I click "Submit" I get an error message that says "Could not determine geoprocessing execution type:".

From what I've read this was supposed to be fixed in 3.3. The widget and same GP service works as-is in version 3.1 of the flex viewer.

I checked the source coud in v3.6 against all the suggested fixes, and they're there for 3.6

I'm stumped.

BjornSvensson

I've installed Flash Builder on my local system ... and it works. So there's some joy there. However, as a ongoing workflow, will I have to do this each time and then configure my application? Or, can i just replace something in the builder templates?

This was all part of version 3.3 that was released this week. You no longer have to do this yourself.

ZacharyHart

Thank you for reporting this - we've now been enabled to reproduce it. I think the problem is only for "file upload". All other parameter types work fine. (So it's not related to "that other 3.2 GP issue")

See https://github.com/Esri/arcgis-viewer-flex/issues/120.

Bjorn,

I've installed Flash Builder on my local system away from my server. I moved the re-compiled project over to the server, added the GP service and it works. So there's some joy there. However, as a ongoing workflow, will I have to do this each time and then configure my application? Or, can i just replace something in the builder templates?

ZacharyHart

Well i just took a detour into Flash Builder. Luckily I have a 60 day trial. Getting the code fix from github was quite easy. However, I've installed Flash Builder on my local system away from my server. I moved the re-compiled project over to the server, added the GP service and it works. So there's some joy there. However, as a ongoing workflow, will I have to do this each time and then configure my application? Or, can i just replace something in the builder templates?

ZacharyHart

Thank you for reporting this - we've now been enabled to reproduce it. I think the problem is only for "file upload". All other parameter types work fine. (So it's not related to "that other 3.2 GP issue")

See https://github.com/Esri/arcgis-viewer-flex/issues/120.

Yes, all of my initial tests were using a service which was leveraging 'file upload'.

However, I have another GP service which is a modified 'extract data task'. This works just fine in 3.1. The relevant map services and GP services are all secured with the same roles on the GIS server. The user logs in once to the application and is then free to use the secured GP services. However, if the application is upgraded to 3.2, the user logs in, but is then prompted to use the data extract GP service; the service prompts for credentials once again, but simply prompts over and over again despite the correct credentials being provided. Again, same exact application, working fine at 3.1, upgraded to 3.2 has the issue and this is not using a GP service with file upload. I think this is a broader issue with 3.2 GP Services in general?

To reiterate the applications specs:
ArcGIS Server 10.1.1. using (token) authentication at the GIS tier, HTTPS/SSL required, self-signed certificate for GIS Server, CA signed certificate for web server.

BjornSvensson

Thank you for reporting this - we've now been enabled to reproduce it. I think the problem is only for "file upload". All other parameter types work fine. (So it's not related to "that other 3.2 GP issue")

See https://github.com/Esri/arcgis-viewer-flex/issues/120.

ZacharyHart

So working with ESRI they are able to replicate the behavior, and are encountering similar behavior when trying to use a proxy instead as I tried.

I have 2 other 3.1 applications which I have not upgraded (good thing) and they contain GP services secured in the same location and with identical permissions as the one I'm trying to use in 3.2, and they work perfectly.

This is starting to look like a 3.2 issue.

I also tried to add the other 'working' GP service which is used in the 3.1 app to the 3.2 app and I'm prompted for credentials; every time I submit the credentials the sign-in just keeps popping up again. When both GP services are exposed in the viewer app, one prompts for credentials, the other says 'Could not determine geoprocessing execution type' (as it did before when I tried to use the proxy).

So back to Bjorn's observation, I do believe that the other issue and this are indeed related. While for some reason the 2 GP services behave differently when executed, it appears that credentials are not being passed correctly.

LaurynasGedminas

I am having the same problem with secure GP services

ZacharyHart

I have been, and they are able to produce this. My test shows that the same service works in a secured service in desktop, but not in flex. If I publish to an unsecured location, the flex app uploads and runs just fine. Waiting on ESRI to see about proxy.my guess is that viewer is not passing credentials to GP services.

BjornSvensson

Zachary, I've heard one other case having problems using a secured GP task, but haven't been able to reproduce when I test against a secure GP task. Any chance you could work with Esri support to have them reproduce this?

ZacharyHart

Out of desperation, I tried to configure a proxy and specify that the GP use the proxy and the error returned this time is 'Could not determine geoprocessing execution type:'.

ZacharyHart

If moved to an unsecured location; the upload will work.

It appears that the user credentials are now not being passed to the GP service?

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

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