Bug 984070 - RHEV-M will never see AD users added by the CLI (net user /add)
Summary: RHEV-M will never see AD users added by the CLI (net user /add)
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-webadmin-portal
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3.3.0
Assignee: Nobody's working on this, feel free to take it
QA Contact: Pavel Stehlik
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-12 16:35 UTC by Bill Sanford
Modified: 2016-02-10 19:01 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-06 09:38:18 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Bill Sanford 2013-07-12 16:35:15 UTC
Description of problem:
If you have ad AD attached to RHEV-M with the "engine-manage-domains" command, there is no way to add users from the Windows 2008 Server R2 (using the CLI to add the Windows users) and have them accessible to RHEV-M.

A "net user /add foobar <password> /fullname:"Foo Bar" /domain" command won't allow the user to show up in RHEV-M. 

I have actually tried:
   net user /add <username> <password> 
   net user /add <username> <password> /fullname:"Foo Barred"
   net user /add <username> <password> /fullname:"Foo Bar" /domain"

When I add user in RHEV-M, by selecting the domain and selecting the go button for the whole user list in AD, I don't see any users added by the CLI. If I add them from the GUI, instead of the CLI, I DO see them. When in RHEV-M, if I use the "search user" dialog to search the user added by the CLI, it NEVER shows the user.

Version-Release number of selected component (if applicable):
RHEV-M 3.3 (is4)

How reproducible:
100%

Steps to Reproduce:
1. See above.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Andrew Cathrow 2013-07-12 22:07:54 UTC
Have you verified that the user has been correctly created in AD within the domain not local?

Can you provide logs?

thanks

Comment 2 Itamar Heim 2013-07-14 07:02:18 UTC
and that the user created in AD has a upn

Comment 3 Barak 2013-08-06 09:38:18 UTC
no reply - moving to CLOSE INSUFFICIENT_DATA


Note You need to log in before you can comment on or make changes to this bug.