Updating authenticators from latest in Tiled - #81
Conversation
|
Wow, thanks @davidpcls! |
|
Thank you. I am going to try to fix the unit tests first, I may push a few commits. |
|
If either of you intend to commit more work to this PR, put it in Draft mode. Change the mode back when you are ready for final review. |
579d82a to
f54ef36
Compare
|
I fixed the unit tests. I also rebased the branch to main, so I had to force push the changes. |
|
Thanks for working on that @dmgav! I just got things setup so I can test with this against MS Entra, so I'll go about verifying there are no other changes required for this to work properly. Took a little longer than expected to get the Entra stuff worked out. |
This is working okay, although it doens't really work smoothly for the API based login and the http command based login isn't great, as it requires the user to copy and past token around. Compared to ldap which just logs the user in. So still some work to do here to smooth out the user experience.
This solves the problem that what was implemented was actually authenticating the application and not the user like expected. It worked but it required that the user input a code. This solves that problem so that when you click the login link, if you are already logged in with you SSO provider you'll just automatically log in to the HTTP Server. Likewise if you use the bluesky queueserver api, when you call RM.Login you'll automatically be logged in, no user interaction required.
These should correct some of the problems in the last CI workflow. I moved the LDAP and docker image into the continuous_integration folder so it matches tiled.
This addresses documentation problems, the levels were incorrect as I did not understand what the next level should have been in the docs. I've also updated the usage documentation a little to be more useful.
These allow for running the unit tests in a containerized system just like how they are done in the ci pipeline, but locally and in a way that can maximize processor usage and minimize runtime.
Testing with ms entra
|
I've added in these changes, I'm going to work on cleaning up failing unit tests now and then I will update the pull request description to match your style and provide information on testing. After that I will remove the WIP status. |
|
Please also see the related PR for the API: bluesky/bluesky-queueserver-api#62 |
This is a set of test changes intended to improve the reliability of unit testing, as the current unit tests are randomly failing due to test design. Primarily this appears to be centered around LDAP. So this work was to: * Fix for ldap errors * Hardening unit tests so they fail less frequency * Try to handle console output more reliably
|
Sorry, got excited about the unit tests passing. I need to do one last integration test first, which is why I converted it back into a WIP |
davidpcls
left a comment
There was a problem hiding this comment.
Comments to assist others reviewing the code
|
After these changes, still seems to be working for me. Neato. |
|
While testing the changes I noticed that the function |
|
@dmgav , interesting that it's doing that. Tiled is using the exact same code for getattr. I'm curious why it doesn't have this same problem, or if it does. Just looking into that now. |
|
It looks like tiled starts the apps differently. Do we even need getattr ? We can start it just fine with: Rather than having getattr. I think getattr just solves us importing server.start_server |
|
I don't remember why we implemented |
Co-authored-by: Dmitri Gavrilov <46980826+dmgav@users.noreply.github.com>
Sounds good, I've committed the changes just now |
|
@davidpcls Do you mind if I push some minor changes to this branch? |
Description
These changes bring in the authenticators from Tiled 0.2.12 into bluesky-httpserver along with the required changes to the app and supporting files to support them. This allows us to use the same authentication setup as from Tiled deployments (at least at the current moment). The main other change is to remove the "mode" flag and instead use the class type to determine if it is an internal or external authenticator.
Part of this work is also the updating of the bluesky-queueserver-api, for which I have created a PR. Both are required in order for the OIDC workflows to work.
Like Tiled, the authentication flow forces a login prompt on each attempt to login. I have tried to minimize any differences between similar functions/files in Tiled and bluesky-httpserver.
Motivation and Context
This solves the problem of having different authentication schemes to maintain between Tiled and HTTP server, which came from the same code around 3 years ago. Tiled has been updated but HTTP server was not. This addresses that.
Summary of Changes for Release Notes
Updated authenticators based off Tiled v0.2.12.
Made minimal changes to app.py and authentication.py to support the changes. Some new endpoints needed to be created to do this, but fairly minimal. The majority of the work was getting the unit test runners stable.
Added local parallel unit test runners to aid development.
Updated the github runners to be more stable and reliable by making the port used dynamic.
Fixed
Added
Changed
Removed
How Has This Been Tested?
Testing was done against MS Entra. I tested that these workflows work for both internal (localhost) and external servers. Using this the login workflow changes to just simply being:
While this was tested with MS Entra, the design is based on Tiled's OIDC and testing used the OIDC flow with MS Entra, so it should theoretically work with all other authenticators using OIDC.
TODO: