Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Login Display Issues #6290

Closed
explorecti opened this issue Mar 8, 2024 · 0 comments
Closed

Login Display Issues #6290

explorecti opened this issue Mar 8, 2024 · 0 comments
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@explorecti
Copy link

explorecti commented Mar 8, 2024

Description

Login page is not centering (excessive margin-top) when adding
addtional messaging and setting PROVIDERS__LOCAL__STRATEGY=false. This
was not an issue with platform version 5.12.32.

Environment

  1. OS: CENTOS7.9
  2. OpenCTI version: 6.0.5
  3. OpenCTI client: Frontend

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Navigate to settings/accesses/policies
  2. Add platform login message (3 lines of text)
  3. Add platform consent message (9-10 lines of text)
  4. set PROVIDERS__LOCAL__STRATEGY=false

Expected Output

User Login page content should be centered.

Actual Output

Content is shifted to page footer while leaving excessive top margin and not displaying OPENIDCONNECT button do to page run off.

Additional information

None

Screenshots (optional)

Screenshot at 2024-03-08 06-06-40

@explorecti explorecti added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Mar 8, 2024
@SamuelHassine SamuelHassine added this to the Release 6.0.6 milestone Mar 8, 2024
@SamuelHassine SamuelHassine removed the needs triage use to identify issue needing triage from Filigran Product team label Mar 8, 2024
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Mar 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

No branches or pull requests

2 participants