Closed marcus-oscarsson closed 7 months ago
Coverage Report •
File Stmts Miss Cover Missing mxcubecore/HardwareObjects Beamline.py 307 102 67% 145–159, 271, 293, 337, 348, 370, 426, 438, 449, 460, 482, 493, 506, 517, 528, 539, 550, 561, 572, 583, 594, 606, 621, 632, 645, 656, 671, 682, 693, 709, 725, 742–828, 835–845, 848, 851–862 LdapAuthenticator.py 102 102 0% 7–185 mxcubecore/HardwareObjects/abstract AbstractAuthenticator.py 13 13 0% 22–50 mxcubecore/HardwareObjects/mockup ISPyBClientMockup.py 208 208 0% 5–725 LdapAuthenticatorMockup.py 13 13 0% 1–30 TOTAL 59311 54820 8%
Tests | Skipped | Failures | Errors | Time |
---|---|---|---|---|
1925 | 0 :zzz: | 0 :x: | 0 :fire: | 1m 34s :stopwatch: |
@rhfogh, @MartinSavko: Do you see an issue with this on the Qt client side ?
I am a little confused. I do not see AbstractAuthenticator or the relevant mockup anywhere in either code or config files, in the PR or the pre-existing code. Should they not be there?
@rhfogh :) thanks, I forgot to add those files, done now
Does this pull request imply some changes that a facility should make in their facility-specific code? Or is that intended to be "backwards compatible" so to say?
And this pull request from the web part https://github.com/mxcube/mxcubeweb/pull/1140 is required, is that right? Or are the 2 pull requests independent?
This PR and https://github.com/mxcube/mxcubeweb/pull/1140 are independent. It makes it possible to decouple the authentication bit from the ISPyB client (for instance in your case ISPyBrestClient) from the rest.
EDIT The actual decoupling of ISPyB and authentication is for a future PR
Greetings from the MXCuBE meeting :)
Introduced
AbstractAuthenticator
and made necessary updates toLdapLogin
This also means that we should move the
authenticate
call fromISPyBclient
to the the authenticate/login logic.All
*LdapLogin
classes have been updated so that they care now call*Authenticator