Project

General

Profile

Bug #27059

Login page asking for browser authentication

Added by William Grzybowski almost 4 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Important
Assignee:
Peter Southwell
Category:
GUI (new)
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

While at login page I was asked for authentication from the browser builtin dialog. (attached screenshot)

I believe that is a bug and should never happen.

It seems to happen after you logout.

The URL it is trying to access is /api/v1.0/system/alert

n9xwn25.png (38.1 KB) n9xwn25.png William Grzybowski, 12/06/2017 10:34 AM
13312

History

#1 Updated by Bonnie Follweiler almost 4 years ago

  • Status changed from Untriaged to Unscreened
  • Assignee changed from Release Council to Anonymous

#2 Updated by Dru Lavigne almost 4 years ago

  • Target version set to 11.2-BETA1

#3 Updated by Anonymous almost 4 years ago

  • Assignee changed from Anonymous to Peter Southwell

#4 Updated by Peter Southwell over 3 years ago

  • Priority changed from No priority to Important

#5 Updated by Anonymous over 3 years ago

Pete, has this one been fixed? I seem to recall it being fixed

#6 Updated by Peter Southwell over 3 years ago

Still happens... Looking into.

#7 Updated by Peter Southwell over 3 years ago

  • Status changed from Unscreened to Ready For Release
  • % Done changed from 0 to 100

Solved simply enough...

as per advice.. https://stackoverflow.com/questions/43985752/how-to-reload-page-with-angular-2

Which I agree.. In that case.. I call all the logout code..
but then do a

ws.service.ts

.....

logout() {
this.clearCredentials();
this.socket.close();
this._router.navigate(['/sessions/signin']);
window.location.reload();
}

SWeems to work nicely.

#8 Updated by Peter Southwell over 3 years ago

  • Status changed from Ready For Release to 19

#10 Updated by Peter Southwell over 3 years ago

  • Status changed from 19 to Ready For Release

https://github.com/freenas/webui/pull/308

Jenkins was in a tiffy.. This ONE line of code compiled just fine in a new branch. Think literally jenkins got to bogged down Bet we're overloading it with too many peeople pushing prs at a timd.

#11 Updated by Dru Lavigne over 3 years ago

  • Status changed from Ready For Release to Resolved
  • Target version changed from 11.2-BETA1 to Master - FreeNAS Nightlies

Also available in: Atom PDF