Bug 36018 - rhn_register/up2date anonymous login fails
Summary: rhn_register/up2date anonymous login fails
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: up2date   
(Show other bugs)
Version: 7.1
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Preston Brown
QA Contact: Jay Turner
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-04-16 11:36 UTC by Joshua West
Modified: 2015-01-07 23:45 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-04-16 11:36:56 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

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

Description Joshua West 2001-04-16 11:36:53 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.4.1-0.1.9smp i686)


I've read that the up2date application allows anonymous logins, but I was
only allowed to anonymously login once.  After that, it told me that RHN
was not accepting anonymous logins anymore. 

Also, what should those of us do who have gone ahead and registered before
reading your documentation on up2date/rhn_register with Wolverine, and
would like to go back to the anonymous method?

Reproducible: Always
Steps to Reproduce:
1. Use up2date for the first time
2. Try to use it again
3.
	

Actual Results:  Anonymous login works the first time, but fails the
second.

Expected Results:  Anonymous login allowed both times...
Comment 1 Jay Turner 2001-04-16 11:45:32 UTC 
Anonymous login to Red Hat Network is not longer allowed.  You can rhn
rhn_register and register your system(s) with RHN and you will be entitled to a
free subscription to Red Hat Network.  Once you have run rhn_register on your
machine to get a valid (i.e. non-anonymous) certification on your system, you
will be able to run up2date again.
Note You need to log in before you can comment on or make changes to this bug.