Timeline for Access user calling a web tool
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 8 at 14:08 | vote | accept | Bernd Loigge | ||
| Aug 29, 2022 at 16:00 | comment | added | KHibma | No. You'd need to explicitly build that into the tool/workflow (getting a token as a parameter and have the calling application pass it in --even then, not sure you can 'share' a token like that). The GP Service framework does not log the user/identity (at least not in the way that those credentials are available internally to the code inside). I understand why you'd make that assumption, and it would be pretty cool if it did, but simply, this is not how it works. | |
| Aug 29, 2022 at 13:59 | comment | added | Bernd Loigge | But when I make the request I can see the token is submitted with the request to the backend / IIS. So I guess the GP Tool must be able to identify the user which triggered the GP Tool, right? | |
| Aug 29, 2022 at 13:18 | comment | added | KHibma | There is no connection between the WebMap / WebApp being logged in and the WebTool that is running on a Server somewhere. Two independent processes. | |
| Aug 29, 2022 at 12:55 | comment | added | Bernd Loigge | I already tried the SignInToPortal method, but there I would need to store some admin user credentials within the code which looks not ideal. | |
| Aug 29, 2022 at 12:53 | comment | added | Bernd Loigge | When I execute the WebTool from within the portal (used in a WebMap) the user is logged into the portal. For me it looks like it is not possible to access the executing user in the GP Tool when executed as a WebTool. | |
| Aug 29, 2022 at 12:12 | history | answered | KHibma | CC BY-SA 4.0 |