Authentication Redirect is Suddenly Incorrect

134
1
Jump to solution
03-23-2021 07:08 AM
JustinWilson
New Contributor II

I am working through a strange situation.  I had an application that has been working for years and then suddenly, the ArcServer stopped redirecting properly.  Here are the details:

URL of App:  https://app.domain.com/AppName

URL of Portal: https://geo.domain.com/portal

Code (Simple Oauth for Portal)

require([
          "esri/arcgis/Portal", "esri/arcgis/OAuthInfo", "esri/IdentityManager",
          "dojo/dom-style", "dojo/dom-attr", "dojo/dom", "dojo/on", "dojo/_base/array",
          "dojo/domReady!"
        ], function(arcgisPortal, OAuthInfo, esriId,
          domStyle, domAttr, dom, on, arrayUtils) {
          var info = new OAuthInfo({
              appId: "<>",
            portalUrl: "https://geo.domain.com/portal",
            authNamespace: "portal_oauth_inline",
            popup: false
          });

 

When I click "Sign In," I am taken to the portal for authentication.  I "allow" the app to use my credentials.  At this point, it was redirecting back to the application and it was working just fine.  Now it redirects incorrectly to: https://geo.domain.com/AppName.  I validated the callback urls in the network traffic and they should be sending the callback to https://app.domain.com/AppName

I opened the application that is registered with the portal to validate the names in Application > Redirect URIs section.  Bottom line is that the application worked and now it seems to have stopped redirecting properly.  Are there settings in Portal that can mess this up?

 

 

0 Kudos
1 Solution

Accepted Solutions
JustinWilson
New Contributor II

This issue seems to be dependent on several compounding factors not related to the development.  Client location and network inconsistencies seem to be the culprit though that is very odd.  Thank you for anyone who looked at the issue.

View solution in original post

0 Kudos
1 Reply
JustinWilson
New Contributor II

This issue seems to be dependent on several compounding factors not related to the development.  Client location and network inconsistencies seem to be the culprit though that is very odd.  Thank you for anyone who looked at the issue.

View solution in original post

0 Kudos