Unable to authenticate using eda-ui

[RobinR1]

Please confirm the following

• I agree to follow this project's code of conduct.
• I have checked the current issues for duplicates.
• I understand that EDA-Controller is open source software provided for free and that I might not receive a timely response.

Bug Summary

disclaimer: First time installation of eda-server using eda-server-operator and new to eda.

After deployment I got a login screen, but I'm not able to login using the admin user.
Browser receives a 204 response on /api/eda/v1/auth/session/login/ and a new csrftoken but keeps logging 403 errors on subsequent /api/v2/me/ calls.

After much trail and error I decided to try older eda-server images, and found that image sha-b4030df is the last image where authentication actually works. When using

  image: quay.io/ansible/eda-server
  image_version: sha-b4030df

I can actually log in using the UI.

Environment

server:
Rancher k3s on SLES15 SP6
client:
Vivaldi browser 7.8 on openSUSE Leap 16.0

Steps to reproduce

Deploy EDA server using eda-server-operator
Not sure if required, but I have set

 extra_settings:
    - setting: EDA_ALLOW_LOCAL_RESOURCE_MANAGEMENT
      value: true

because I run EDA standalone
Ensure correct Ingress / IngressRoute / Route is set to service eda-ui
After deployment, surf to your set entrypoint to get the UI login screen (do note: broken logo image)
Log in as admin with credentials set in deployment config or from generated eda admin secret

Actual results

Page does not refresh nor displays any error. Nothing seems to happen visually.
Browser developer tools > network tab shows 403 errors on /api/v2/me/ calls, even after successful 204 response from /api/eda/v1/auth/session/login/

Expected results

Page refreshes to EDA Server Overview page as user Admin

Additional information

Login works as expected on sha-b4030df image of eda-server

[ttuffin]

Hi @RobinR1, this should be resolved once #1503 is merged.

[kaiokmo]

Hi @RobinR1! I moved the change from the above PR to this one in the operator: ansible/eda-server-operator#331

We shouldn't need to override this setting in EDA server defaults. It's up to the deployer to decide how EDA will be deployed anyway. Development mode sets the resource server URL to None, and we can live with that. The operator, as a deployment mechanism, can get the workaround.