Bug 33528 - Use credentials of the current user
Summary: Use credentials of the current user
Status: RESOLVED WONTFIX
Alias: None
Product: UCS
Classification: Unclassified
Component: UMC - Domain join
Version: UCS 3.2
Hardware: Other Linux
: P5 enhancement
Target Milestone: UCS 3.2-x
Assignee: UMC maintainers
QA Contact:
URL:
Keywords:
: 35067 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-11-21 20:22 CET by Stefan Gohmann
Modified: 2017-08-08 07:10 CEST (History)
1 user (show)

See Also:
What kind of report is it?: ---
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):
Customer ID:
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Gohmann univentionstaff 2013-11-21 20:22:00 CET 
By default the credentials of the logged in user should be used. At least if the current user is member of Domain Admins. Maybe we could add a button "Run as different user".
Comment 1 Florian Best univentionstaff 2015-01-12 14:45:51 CET 
*** Bug 35067 has been marked as a duplicate of this bug. ***
Comment 2 Stefan Gohmann univentionstaff 2017-06-16 20:37:23 CEST 
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
Comment 3 Stefan Gohmann univentionstaff 2017-08-08 07:10:31 CEST 
This issue has been filed against UCS 3.2.

UCS 3.2 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.