-
Notifications
You must be signed in to change notification settings - Fork 7
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
feat: OIDC Broker and EntraID specific group management #13
Conversation
23578b2
to
0e930ab
Compare
f75e105
to
2363708
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is amazing work, I had some comments, all minor though :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I haven’t done a full review yet, but I think we have an excellent start here!
I think there is more still to review and achieve, but let’s fix those first, and see what the consequences on the code are.
Excellent work!
f3d3527
to
3f692ce
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
while doing pairing :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
go.sum conflict fix + need some feedbacks on the investigation on file touching (and a test)
There were some missing dbus methods in brokerservice (and the NewSession method definition was also missing the input argument for the session mode)
073a91e
to
def051d
Compare
I was expecting to see some tests around expiration changing, do we miss any? I think a test with offline login and below offline cache expiration date, we can login and another one where we are after that date, and can’t login. We had similar tests in aad-auth. |
Like these? |
Right, but why weren’t they modified with the latest commit? They should have been impacted or it means, we have a missing test somewhere :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to check the configuration file in order to gather required values for the broker creation. This is best done when creating the brokerservice.
Instead of having the providers handled by the internal/broker package, they now have their own separate package to manage them and their respective functionalities. This helps a lot when mocking them for the tests and also make the code scale better.
Common test utilities such as LoadAndUpdateFromGolden
51e0111
to
f4f1771
Compare
I'm opening this as a single draft PR for now so we can have this code listed somewhere. We can decide later whether we should merge this as a single pull request or break it into multiple ones.
UDENG-2039
UDENG-2040
UDENG-2041
UDENG-2042
UDENG-2043