Hello, I have just hit this and wondered if anyone has seen similar before since the login page was added to the Admin UI?
I'm using Solr 6.6.6 currently, but I'm in the process of moving to 8.1.x. That means I've been accessing the UI from 6 and had it cached. I switched off 6 and run the 8.1.x (built off of https://github.com/apache/lucene-solr/commit/c9bc8273c1e714ff06b2c443838f5aa690690298 ) Upon opening the Admin UI I got some nasty behaviour, which appears to be a result of some the Solr 6 Admin UI pages being cached. In Chrome, I got a Basic Auth prompt in the browser, rather than the login page. Then when trying to run a query (from http://localhost:8983/solr/#/gettingstarted/query), the results pane showed a 401 for the entire results frame. Reloading the page without cache fixed it. i.e the login page appeared and I then logged in through it, and things worked correctly. In Firefox, I got the login page, but it was malformed (see https://i.ibb.co/SvVws3j/login.jpg). In the dev console the error was Error: [$injector:unpr] Unknown provider: AuthenticationServiceProvider <- AuthenticationService <- LoginControllerhttp://errors.angularjs.org/1.3.8/$injector/unpr?p0=AuthenticationServiceProvider%20%3C-%20AuthenticationService%20%3C-%20LoginController minErr/<@http://localhost:8983/solr/libs/angular.js:86:12 createInjector/providerCache.$injector<@http://localhost:8983/solr/libs/angular.js:4017:19 getService@http://localhost:8983/solr/libs/angular.js:4164:39 createInjector/instanceCache.$injector<@http://localhost:8983/solr/libs/angular.js:4022:28 getService@http://localhost:8983/solr/libs/angular.js:4164:39 invoke@http://localhost:8983/solr/libs/angular.js:4196:13 instantiate@http://localhost:8983/solr/libs/angular.js:4213:27 $ControllerProvider/this.$get</<@http://localhost:8983/solr/libs/angular.js:8472:18 link@http://localhost:8983/solr/libs/angular-route.min.js:30:268 invokeLinkFn@http://localhost:8983/solr/libs/angular.js:8236:9 nodeLinkFn@http://localhost:8983/solr/libs/angular.js:7745:11 compositeLinkFn@http://localhost:8983/solr/libs/angular.js:7098:13 publicLinkFn@http://localhost:8983/solr/libs/angular.js:6977:30 boundTranscludeFn@http://localhost:8983/solr/libs/angular.js:7116:16 controllersBoundTransclude@http://localhost:8983/solr/libs/angular.js:7772:18 x@http://localhost:8983/solr/libs/angular-route.min.js:29:364 $broadcast@http://localhost:8983/solr/libs/angular.js:14725:15 m/<@http://localhost:8983/solr/libs/angular-route.min.js:34:426 processQueue@http://localhost:8983/solr/libs/angular.js:13193:27 scheduleProcessQueue/<@http://localhost:8983/solr/libs/angular.js:13209:27 $eval@http://localhost:8983/solr/libs/angular.js:14406:16 $digest@http://localhost:8983/solr/libs/angular.js:14222:15 $apply@http://localhost:8983/solr/libs/angular.js:14511:13 done@http://localhost:8983/solr/libs/angular.js:9669:36 completeRequest@http://localhost:8983/solr/libs/angular.js:9859:7 requestLoaded@http://localhost:8983/solr/libs/angular.js:9800:9 <div ng-view="" id="content" class="ng-scope"> angular.js:11617:18 Again, reloading the page without caching fixed the problem. So, this isn't a major issue, but it's not a nice experience when you hit it. Any thoughts? I can raise a JIRA issue just to track it, even if it's not worth fixing. Cheers Colvin
