Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • V VISPA web
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 84
    • Issues 84
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • 3pia3pia
  • VISPAVISPA
  • VISPA web
  • Issues
  • #582
Closed
Open
Issue created Mar 01, 2015 by Benjamin Fischer@benjamin.fischerOwner

Logging in

When trying to log in (on the test-server) with Mozilla Firefox, although the user parameters are correct, the login fails.
An appropriate message is not given, instead the two fields (username, password) are reset.

This bug does not occur when using Chromium web browser.

In the console, it is complained about some certificate for login (see screenshot). Yet, if the user is not familiar with the usage of the console he has no chance to see what is preventing the login.

(from redmine: issue id 2154, created on 2015-03-01 by root, closed on 2015-03-02)

  • Changesets:
    • Revision 2149 by Fabian Heidemann on 2015-04-27T16:25:43Z:
Clean-up inflationary use of event.stopPropagation(), fix #2154
  • Revision 2149 by Fabian Heidemann on 2015-04-27T16:25:43Z:
Clean-up inflationary use of event.stopPropagation(), fix #2154
  • Uploads:
    • CertificateComplaint
Assignee
Assign to
Time tracking