Closed adombeck closed 1 month ago
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 84.74%. Comparing base (
924b003
) to head (c69735d
). Report is 8 commits behind head on main.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
We're having some real flakiness issues in github.com/ubuntu/authd/pam/integration-tests
. Took four attempts to get them to pass here.
What I want to avoid is that a user can log in as another user on the same Entra instance because strings.EqualFold considers different Entra user names equal.
I'll create a PR against the brokers repo to use strings.ToLower
instead of strings.EqualFold
.
forgot to push some commits or is my browser broken? :)
forgot to push some commits or is my browser broken? :)
Right, my pre-push hook failed because of those weird "directive is unused for linter" errors from golangci-lint
which only I get locally :/
Pushed with --no-verify
now.
I am unsure if you noticed that the tests are failing (please always check CI after pushing).
If they would not anyway, I would have asked for a test illustrating that we don’t check the user name matching anyway, but we already have them to cover that functionality of the code! :)
I am unsure if you noticed that the tests are failing (please always check CI after pushing).
I did notice that, but at the bottom of the logs of the CI job I only saw the pam integration tests failing, which are known to be flaky, so I just retried the tests a couple of times. After taking a closer look now, I see that the broker tests are also failing. I will address that.
Microsoft Entra user names are case insensitive, so we should ignore the case when comparing the user name.
Closes #496
UDENG-4334