Bug 26226 - UCS Test S4&AD: 172sync_ad_change_username prüft userPrincipalName falsch
UCS Test S4&AD: 172sync_ad_change_username prüft userPrincipalName falsch
Status: CLOSED WORKSFORME
Product: UCS Test
Classification: Unclassified
Component: S4 Connector
unspecified
Other Linux
: P5 normal (vote)
: ---
Assigned To: Julius Hinrichs
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-02-23 12:10 CET by Felix Botner
Modified: 2023-03-25 06:48 CET (History)
3 users (show)

See Also:
What kind of report is it?: Development Internal
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Felix Botner univentionstaff 2012-02-23 12:10:22 CET
info 2012-02-22 19:19:49         Yes
info 2012-02-22 19:19:49         CN=hxacostl,CN=Users,DC=AS,DC=DF: "userPrincipalName" == "tykhmkmeother" ??
info 2012-02-22 19:19:50         Value of "userPrincipalName" is "tykhmkmeother@AS.DF".
info 2012-02-22 19:19:50         Expected: "tykhmkmeother"
error 2012-02-22 19:19:50        Expected operation to succeed, but it failed
error 2012-02-22 19:19:50        **************** Test failed above this line (110) ****************

userPrincipalName ist immer in der Form "USERNAME@DOMÄNE", der Test 72sync_ad_change_username will aber das nur der Benutzername in userPrincipalName steht, das sieht nicht richtig aus.
Comment 1 Arvid Requate univentionstaff 2016-09-28 11:56:08 CEST
I guess that's both tests:

52_s4connector/172sync_ad_change_username
55_adconnector/172sync_ad_change_username
Comment 2 Stefan Gohmann univentionstaff 2016-10-12 07:49:00 CEST
For this bug is no separate QA needed.