Bug 251909 – Populate orgid for user service

Bug 251909 - Populate orgid for user service

Summary:	Populate orgid for user service

Status:	CLOSED WONTFIX

Aliases:	None

Product:	Red Hat Network
Classification:	Red Hat
Component:	RHN/Backend (Show other bugs)
Sub Component:
Version:	RHN Stable
Hardware:	All Linux

Priority	low Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Bryan Kearney
QA Contact:	Red Hat Satellite QA List
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:	433492
Blocks:	244391 345571
	Show dependency tree / graph

Reported:	2007-08-13 09:13 EDT by James Bowes
Modified:	2013-01-10 04:55 EST (History)
CC List:	3 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2008-04-08 10:05:44 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:

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

Groups: None (edit)

Description James Bowes 2007-08-13 09:13:45 EDT

User registration via the backend does not consistently populate the org id
field. Fix this.

Comment 1 James Bowes 2007-10-08 17:25:34 EDT

Chris, I think what's going on here is the org_id field will not be filled in
when we are creating a new user that isn't to be added to an exisiting org; it
should get its own new org. Does this make sense? What should happen in that case?

Comment 2 James Bowes 2007-11-06 13:16:09 EST

From what Chris tells me, this will require a change in the userservice code. So
it may or may not require a change on our part. Moving to 505-triage.

Comment 3 James Bowes 2008-03-11 09:01:11 EDT

Since we're disabling new user creation in rhn_register, this won't be a problem
any longer.

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