Select to view content in your preferred language

3.3 api not prompting for login (identitymanager) firefox only.  Chrome and IE work

1270
9
03-13-2013 05:46 AM
JeffPace
MVP Alum
Ok so changing my app from 3.2 to 3.3 makes the identity manager stop prompting for a login in FIREFOX (v20 and v19) only.  Chrome and IE7 both work

https://www.mymanatee.org/gisapps/mapviewer-ssl/index.jsp?type=utilitiesinfrastructure  <---- 3.3 api
https://www.mymanatee.org/gisapps/mapviewer/index.jsp?type=utilitiesinfrastructure     <----- 3.2 api

the api is the only change.

any ideas? firefox is our recommended browser

There is no error in the Firebug console other than forbiddens on the urls (expected, since we never logged in)
0 Kudos
9 Replies
JeffPace
MVP Alum
anyone have similar problems?
0 Kudos
TimSeiple
New Contributor
I am experiencing the same in Firefox and Chrome.  However, If i first visit the service directory (e.g. http://host/instance/rest/services), I am prompted and can login successfully.

If I then refresh the webpage i was interested in, the data will appear because the login is valid for the entire browser session.

Obviously not something I want my users to have to do.  Still searching for an elegant solution

Tim
0 Kudos
JeffPace
MVP Alum
same here, obviously not a solution.

Have not tested 3.4 yet
0 Kudos
JeffPace
MVP Alum
can't test 3.4 because its not available for download yet.

Anyone else seeing this?
0 Kudos
MattLane
Frequent Contributor
Your 3.3 api link is giving me a 404 Page not found error
0 Kudos
JeffPace
MVP Alum
sorry, redeployed
0 Kudos
JeffPace
MVP Alum
Same Error with 3.4

Chrome prompts for login, firefox does not

https://www.mymanatee.org/gisapps/mapviewer34/index.jsp?type=utilitiesinfrastructure
0 Kudos
JeffJacobson
Frequent Contributor
Same Error with 3.4

Chrome prompts for login, firefox does not

https://www.mymanatee.org/gisapps/mapviewer34/index.jsp?type=utilitiesinfrastructure


I just tried your link in Firefox (v 20) and was prompted for a login.
0 Kudos
JeffPace
MVP Alum
Believe it or not, I just found and fixed it.

My Draw widget had

dojo.require("dijit.form.CheckBox");

Which was no longer used.  For some reason, it was causing the error.  All I did was comment it our and the login popped up.

Very odd.
0 Kudos