Authentication with user/pass, OAuth2 and Keycloak

[rsnyman]

• AuthService for authentication
• HttpClient for all http calls
• Login page
• Login controller

[john-dupuy]

I've only tried out Gitlab auth so far but I noticed the following:

• Clicking the "Sign up" button on the login page reloads the page but doesn't take you to a sign-up form. Just the same page is displayed. Same thing with the "Forgot username or password" button
• When we deploy outside of VPN, we should disable these buttons and default to some pre-configured auth mode through Github or SSO
• After logging in via Gitlab, all the requests from the frontend to the backend failed with:

Access to fetch at 'http://localhost:8080/api/run?estimate=true&pageSize=20&page=1' from origin 'http://localhost:3000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

[rsnyman]

I've only tried out Gitlab auth so far but I noticed the following:

• Clicking the "Sign up" button on the login page reloads the page but doesn't take you to a sign-up form. Just the same page is displayed. Same thing with the "Forgot username or password" button
• When we deploy outside of VPN, we should disable these buttons and default to some pre-configured auth mode through Github or SSO
• After logging in via Gitlab, all the requests from the frontend to the backend failed with:

Access to fetch at 'http://localhost:8080/api/run?estimate=true&pageSize=20&page=1' from origin 'http://localhost:3000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

I've fixed up some DB queries that were wrong, maybe they were causing this issue? Everything works for me right now.

[john-dupuy]

@rsnyman Finally got a chance to check this out again today. Gitlab login is working fine but now I see when trying to access the runs page:

  File "/home/jdupuy/iqe/iqe-repos/ibutsu/ibutsu-server/backend/ibutsu_server/util/projects.py", line 40, in add_user_filter
    query = query.filter(or_(project in user.projects, project.owner == user))
  File "/home/jdupuy/iqe/iqe-repos/ibutsu/ibutsu-server/backend/.ibutsu-env/lib/python3.9/site-packages/sqlalchemy/orm/attributes.py", line 238, in __getattr__
    util.raise_(
  File "/home/jdupuy/iqe/iqe-repos/ibutsu/ibutsu-server/backend/.ibutsu-env/lib/python3.9/site-packages/sqlalchemy/util/compat.py", line 182, in raise_
    raise exception
AttributeError: Neither 'InstrumentedAttribute' object nor 'Comparator' object associated with Run.project has an attribute 'owner'

For the results page:

  File "/home/jdupuy/iqe/iqe-repos/ibutsu/ibutsu-server/backend/.ibutsu-env/lib/python3.9/site-packages/sqlalchemy/orm/attributes.py", line 238, in __getattr__
    util.raise_(
  File "/home/jdupuy/iqe/iqe-repos/ibutsu/ibutsu-server/backend/.ibutsu-env/lib/python3.9/site-packages/sqlalchemy/util/compat.py", line 182, in raise_
    raise exception
AttributeError: Neither 'InstrumentedAttribute' object nor 'Comparator' object associated with Run.project has an attribute 'owner'

Also, I'm wondering about the swagger UI, how can we authenticate there to mess with API queries?

[rsnyman]

Superseded by #227