Univention Bugzilla – Bug 34369
Test case for changing the password on login via UMC
Last modified: 2023-03-25 06:42:57 CET
Created attachment 5834 [details] sample code This has been partly resolved, some sample test code has been attached. However, the specified TODO parts are yet to be adjusted, currently 411 is returned when trying to change the password.
Created attachment 5835 [details] sample code
The script fails currently with > cookie: None > connection response: '{"status": "411 Length Required", "message": "Current Kerberos password: "}'
IMHO we should implement the following test cases: UMC-Authentication with: * correct Password * incorrect Password * expired password * change of password * change of password fails → multiple reasons * password containing unicode characters * modules (UDM) usable after password change * deactivated user account * removed user account
r52522: * 60_umc-system/31_umc-service-user-authentication: test the UMC user authentication and password change (Bug #34369) Notes: - test limited to DC-Master as modifying UCR on master node from other nodes is not that convenient; - regarding the status code 411 opened Bug #35571 - Bug #25279 was reproduced + "Account expiry date" there shows wrong date format in appearing hint message (day.month.year instead of MM/DD/YYYY); - also opened Bug #35575.
r52779: * 60_umc-system/TestUMCSystemModule.py: added method to wait for samba replication; 60_umc-system/samba_repl.sh: a small wrapper for ../lib/samba.sh; 60_umc-system/31_umc-service-user-authentication: wait for samba syncronisation whenever possible (Bug #34369). Updated as in S4 environment an authentication with a removed (etc.) user may be successful since sync takes some time. (http://jenkins.knut.univention.de:8080/job/UCS%203.2-2%20Autotest%20MultiEnv/SambaVersion=s4,Systemrolle=master/114/testReport/junit/60_umc-system/31_umc-service-user-authentication/test/) After Bug #35634 is resolved -> should be updated at line 273.
(In reply to Dmitry Galkin from comment #5) > * 60_umc-system/TestUMCSystemModule.py: added method to wait > for samba replication; > 60_umc-system/samba_repl.sh: a small wrapper for ../lib/samba.sh; Came across waiting methods already implemented in Python just by chance: ucs-test/univention/testing/ucs_samba.py
OK: TestUMCSystem.wait_for_samba_replication() OK: samba_repl.sh OK: 31_umc-service-user-authentication OK: ./31_umc-service-user-authentication -vvvf (In reply to Florian Best from comment #3) > IMHO we should implement the following test cases: > > UMC-Authentication with: > * correct Password OK > * incorrect Password OK > * expired password OK > * change of password OK > * change of password fails → multiple reasons > * password containing unicode characters OK > * modules (UDM) usable after password change OK > * deactivated user account OK > * removed user account OK FAIL: > Setting an expiry date in the past for the test user 'umc_test_user_cvevad' account and trying to authenticate: ... > Waiting for replication: > OK: replication complete (nid=288 lid=288) > Done: replication complete. > ### FAIL ### > > Waiting for Samba replication failed, in stderr: > 'Kein Paket gefunden, das auf univention-samba4 passt. > ' @ samba_repl.sh:6 -if checkpkg "univention-samba4"; then +if checkpkg "univention-samba4" 2>/dev/null; then
(In reply to Philipp Hahn from comment #7) > @ samba_repl.sh:6 > -if checkpkg "univention-samba4"; then > +if checkpkg "univention-samba4" 2>/dev/null; then r53010: * 60_umc-system/samba_repl.sh: checkpkg output > /dev/null 60_umc-system/31_umc-service-user-authentication: wait bit more after user is being deleted (Bug #34369)
OK: r53010 OK: /usr/share/ucs-test/60_umc-system/31_umc-service-user-authentication -vvvf