ArcGIS Portal (OAuth2) Authentication from Workflow 5

Jerry Stafurik

19 Januari 2021 04:28

I have a Geocortex Essentials server and Workflow integrated with ArcGIS Portal, which contains a Site that requires authentication. When loading the site the user gets redirected to Portal to login, which works well.

 

However, the site has a workflow that needs to call a 3rd party API (REST .Net Core App), that also authenticates using OAuth2 against Portal. Currently when sending requests from the workflow, the API tries to redirect the user to the Portal login (which fails, as it's just a web request call from the workflow).

 

• Has anyone done something similar, where they have to pass through some sort of authentication details to a 3rd party application/API, so that the request can be verified with Portal -- making sure the user has permissions to perform the operation?
• Is there a way to integrate 3rd party APIs with Geocortex Essemtials in terms of authentication, or pass some sort of token to a 3rd party API to perform verification?
• Can the identity server be used to integrate an application for SSO? Is there are documentation for the identity server?

 

I can't use windows authentication, as some users are outside the organization -- therefore Portal is used to authenticate against. I need to be able to determine who the user is, and verify this against Portal when a request comes through to the REST API.

0

• 

  Permanently deleted user

  11 Januari 2022 14:36

  Jerry,

   

  Did you ever found an answer for this case. I would like to use Oauth2 with API's and can't find a way do it this.

   

  Erik

   

  0
• 

  Jerry Stafurik

  17 Januari 2022 00:35

  Hi Erik,

   

  I couldn't figure out how to integrate the workflow as a "Single Sign-on" with Portal.

   

  I ended up creating a custom activity, that on launch of a workflow redirects the user (by opening a new browser tab) to log in (through the custom API), which authenticates all other future requests against the API -- so, the users only authenticate twice once (one for GCX and one for the custom API), and then the authentication persists for a while. Once the authentication is successful, the tab closes and the workflow continues launching.

   

  Hope this helps.

   

  Jerry

  0
• 

  Jerry Stafurik

  17 Januari 2022 00:37

  Forgot to add, that the custom activity checks whether the user is already authenticated, so it doesn't direct the user to log in if the user is authenticated, and the workflow just launches normally.

  0

Du måste logga in om du vill lämna en kommentar.