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

Change in identity manager between 2.5 and 2.6

JeffPace1

My identity manager works at 2.5. I don't have any custom code in it at the moment, it just hits the first secure service and prompts for login (AWESOME THANK YOU)

when I change my application to 2.6, firebug throws and error saying

tokenserviceurl not defined

and hangs login.

What changed?

Find more posts tagged with

Accepted answers

JeffPace1

Let's try this:

var serverInfo = new esri.ServerInfo(); serverInfo.server = 'https://www.mymanatee.org'; serverInfo.tokenServiceUrl = 'https://www.mymanatee.org/arcgis/tokens/generateToken';           esri.id.registerServers([serverInfo]);

Can you let us know if that works?

esri.ServerInfo is not a constructor
[Break On This Error] var serverInfo = new esri.ServerInfo();

All comments

JeffPace1

Ok i think i got it but it is a bit kludgy. It seems as though it works as long as there is a secure service loaded somewhere. If not, it fails

Since i load my layers based on config parameters (in the url) there isnt always a secure service. I just had to trap to make sure that dojo.ready function is only called if the site is being accessed securely, seems to work ok.

derekswingley1

Not sure how much I can help with that...maybe use an additional query string parameter indicating if there are secure services and check that before defining the serverInfo?

Just as an FYI, dojo.ready and dojo.addOnLoad are the same thing: http://bugs.dojotoolkit.org/browser/dojo/tags/release-1.6.1/dojo/_base/_loader/loader.js#L202

JeffPace1

Yes if we use secure services, the entire app is accessed over https. So for now I am just checking the protocol for https. If it it is i load the serverinfos. Seems to work.

Would still be nice to have an "onSuccessfulIdentity" type event to listen for. I am running into more and more circumstances where I need to fire code if a login is successful, and different code if login fails.

Thanks for the help getting this up and running.

JeffPace1

Did this change again with 2.7 or 2.8? I had to roll back to 2.6 .

derekswingley1

Hi Jeff,

Can you recap where you're at with this issue?

JeffPace1

Let me 'splain.
[pause]
No, there is too much. Let me sum up.

Ok so we are using a highly modified version of the JSViewer sample from many moons ago, accessing Local GIS Server services from multiple servers, one that is secured using tokens (arcgis server 10sp4 for JAVA).

We access these services twice. Once for the mapLayer, Once directly to the legend for a TOC icon.

The application is deployed as a war file on tomcat, all services, application, and locally hosted API accessed via a WebApp Firewall (modproxy) to avoid cross-domain issues.

On upgrading from 2.5 to 2.6, i had to add to my index.jsp

         function initSecurity() {
                    // Comment out these lines, and the onresize on body
                    // if you don't want full-screen
                    var serverInfo = new esri.ServerInfo();
                        serverInfo.server = 'https://www.mymanatee.org';
                        serverInfo.tokenServiceUrl = 'https://www.mymanatee.org/arcgis/tokens/generateToken';
                        esri.id.registerServers([serverInfo]);

                };
 if(document.location.protocol==="https:"){
                    dojo.addOnLoad(initSecurity);
                }

for the services, and then for the TOC add

var params = {
                 url:urls+"/legend",
                        layerName:layerNames,
                        content:{f:"json"},
                 handleAs: "json",
                 sync: true,
                 load: dojo.hitch(this, "onLegendLoad"),
                 error: dojo.hitch(this, "onLegendError")
             };
                     if(document.location.protocol==="https:"){
   if(esri.id.credentials.length>0){
                            params.content["token"]=esri.id.credentials[0].token;
   }
                    }

which allows me to add the token to the url call for the legend json.

This worked upgrading from 2.5 to 2.6 (it was not necessary at 2.5 as the token server was guessed)

however it seems to be broken at 2.7/2.8 resulting in an uninitialized variable for me. Simply changing back to 2.6 gets rid of the error

The onLegendLoad function

     onLegendLoad: function(response, ioArgs) {
                var minScale=591657527.591555;
                var maxScale=0;
                if(!this.tocScales[ioArgs.args.layerName]){
                      this.tocScales[ioArgs.args.layerName]={response:response, ioArgs:ioArgs};
                }
                dojo.forEach(response.layers, dojo.hitch(this,function(layer){
                    dojo.forEach(layer.legend, dojo.hitch(this, function(legend){
                        var legendUrl=    legend.url;
                        if(legendUrl.length<10){
                        legend.url =  ioArgs.url.replace("legend?f=json&token=",layer.layerId+"/images/"+legendUrl+".png?token=");
                        legend.url =  ioArgs.url.replace("legend?f=json",layer.layerId+"/images/"+legendUrl+".png");
                        }
                        minScale=layer.minScale;
                        maxScale=layer.maxScale;
                        if(minScale==0){
                            minScale=591657527.591555;
                        }
                        if((minScale==0&&maxScale<=1)||(this.currentScale>maxScale&&this.currentScale<minScale)){
                            layer.scaleVisible=true;
                        }else{
                           layer.scaleVisible=false;
                        }
                    }))                    
                }))
         this.layersInfoLegend.push(response.layers);              
     },

Does two things, it loops through every service and every sublayer, and grabs the legend icon. This is where the token needed to be appended for the secure services
It also checks the scale dependency of the service to color code the TOC entry to show scale dependent visibility.

Of course there are alot of other functions involved, but these are the only two that address security. The version of my site (by config file) that does not access any secure layers (http only) throws no errors and works perfectly at 2.8

JeffPace1

I got this fixed, i think i got bitten by the asynchronous nature of javascript.

For some reason at 2.6 it worked fine, changing to 2.7 or 2.8 cause a variable i was using to be called before it was set, but only when i used the identitymanager. Trapping for undefined/null allows me to proceed without the error.

sorry for the false alarm, i am still baffled as to what changed.

derekswingley1

So you're all good now?

JeffPace1

Yes I am good, for now, mostly.

OF course I am nervous that at 2.9 (and changing to dojo 1.7+) alot of these workarounds will need tweaking, and my biggest concern is the lack of documentation on them.

For example, in the work around, we do

esri.id.registerServers([serverInfo]);

but where is esri.id documented? I am guessing based on the registerServers command that it is related to esri.IdentityManagerBase, but i never created an "id" object, so how am i setting it?

derekswingley1

The Identity Manager API ref documents esri.id: http://help.arcgis.com/en/webapi/javascript/arcgis/help/jsapi/identitymanager.htm

IdentityManager is a singleton class and is automatically instantiated into esri.id when the module containing this class is imported into the application. Because IdentityManager extends esri.IdentityManagerBase it inherits all of the IdentityManagerBase class properties and methods.

JeffPace1

The Identity Manager API ref documents esri.id: http://help.arcgis.com/en/webapi/javascript/arcgis/help/jsapi/identitymanager.htm

awesome thank you, thats what i get for only looking in identitymanagerbase and not realizing that identitymanager extends it.

Thanks again

BenSayers

Hi there,
I am hoping Jeff or Derek will be able to help me.
I have a secure site running in AGS 10.04 using the JS API 2.8.
I am having trouble getting the legend widget to display the icons for the layers in IE. All works fine in Chrome, FF and Safari but in IE I get the red cross error.
All worked fine before I switched to https. I've read several posts which suggest its something to do with the token service not authenticating the legend, but I am stuck as to how to correct this.
The code quoted below seems like it should be what I need but I'm unsure how to hook this in.
Is there something I can force in my proxy.jsp page? Or hardcode in my .js page?
Any help or suggestions would be most welcome.
Many thanks,
Ben Sayers

The onLegendLoad function

     onLegendLoad: function(response, ioArgs) {
                var minScale=591657527.591555;
                var maxScale=0;
                if(!this.tocScales[ioArgs.args.layerName]){
                      this.tocScales[ioArgs.args.layerName]={response:response, ioArgs:ioArgs};
                }
                dojo.forEach(response.layers, dojo.hitch(this,function(layer){
                    dojo.forEach(layer.legend, dojo.hitch(this, function(legend){
                        var legendUrl=    legend.url;
                        if(legendUrl.length<10){
                        legend.url =  ioArgs.url.replace("legend?f=json&token=",layer.layerId+"/images/"+legendUrl+".png?token=");
                        legend.url =  ioArgs.url.replace("legend?f=json",layer.layerId+"/images/"+legendUrl+".png");
                        }
                        minScale=layer.minScale;
                        maxScale=layer.maxScale;
                        if(minScale==0){
                            minScale=591657527.591555;
                        }
                        if((minScale==0&&maxScale<=1)||(this.currentScale>maxScale&&this.currentScale<minScale)){
                            layer.scaleVisible=true;
                        }else{
                           layer.scaleVisible=false;
                        }
                    }))                    
                }))
         this.layersInfoLegend.push(response.layers);              
     },

JeffPace1

Are you manually building a legend?

if so then you can add the token to the params prior to making the legend request

if(document.location.protocol==="https:"){
   if(esri.id.credentials.length>0){
                            params.content["token"]=esri.id.credentials[0].token;
   }
                    }

Hi there,
I am hoping Jeff or Derek will be able to help me.
I have a secure site running in AGS 10.04 using the JS API 2.8.
I am having trouble getting the legend widget to display the icons for the layers in IE. All works fine in Chrome, FF and Safari but in IE I get the red cross error.
All worked fine before I switched to https. I've read several posts which suggest its something to do with the token service not authenticating the legend, but I am stuck as to how to correct this.
The code quoted below seems like it should be what I need but I'm unsure how to hook this in.
Is there something I can force in my proxy.jsp page? Or hardcode in my .js page?
Any help or suggestions would be most welcome.
Many thanks,
Ben Sayers

BenSayers

Are you manually building a legend?

if so then you can add the token to the params prior to making the legend request
if(document.location.protocol==="https:"){
   if(esri.id.credentials.length>0){
                            params.content["token"]=esri.id.credentials[0].token;
   }
                    }

I am using the legend widget. So I am using:

var legend = new esri.dijit.Legend({
                        map: map,
                        layerInfos: legendLayers
                    }, "legendDiv");
    

                    legend.startup();

                });

Any ideas?

JeffPace1

you are not going crazy. I just opened my secure site in IE (something i try to never do) and the default legend widget is broken for us also. Non secure services work fine, but secure ones do not. (red x)

Looks like ESRI did not implement the fix they suggested to me in their own widget.

Could you please start a new thread saying the default legend widget doesnt work over https in IE? this one is already marked as answered and might not get as much attention.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

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