Description of problem: TO remove the user creation from registration process against hosted, we need hosted to return appropriate message letting user know what to do. The registration client makes an xmlrpc call to hosted when login/password is entered. Which in turn calls backend/server/rhnUser.py's reserve_user method. In Satellite Case this method returns a rhnFault that user creation is not allowed in RHN Satellite context by checking 'disallow_user_creation' config variable and if user exists. The same thing need to happen for hosted case as well. - Flip the 'disallow_user_creation' flag in /etc/rhn/defaults/rhn_server.conf - Fix the error message to suggest user to go to hosted url to create new user. - raise rhnFault which the client would catch and show the user to do the appropriate thing.
Note: Make sure to let Pradeep/Satellite know when this is in the QA env
aghhhh TUI-- chops off part of the message There was an error communicating with the # │ ┐ │ │ registration server: ▒ │ │ │ │ ▒ │ │ │ │ Error Class Code: 2001 ▒ │ │ │ │ Error Class Info: ▒ │ │ │ │ We're sorry! Due to changes in the way we ▒ │ │ │ │ capture information, user ▒ │ │ │ │ creation has been disabled through this ▒ │ │ │ │ process. To continue, please visit ▒ │ │ │ │ -- ▒ │ │ │ │ https://www.redhat.com/wapps/ugc/register.html ▒ │ │ │ │ -- (you may copy and ▒ │ │ │ │ │ │ │ │ ┌────┐ │ │ │ │ │ OK │ │ │ │ │ └────┘
from rhnreg_ks new message: Error Class Code: 2001 Error Class Info: We're sorry! Due to changes in the way we capture information, user creation has been disabled through this process. To continue, please visit -- https://www.redhat.com/wapps/ugc/register.html -- (you may copy and paste) and create a Red Hat login. To complete the process, run rhn_register on the command line and enter your new username and password when prompted. Our sincerest apologies for having you enter your new account information twice.
all set on dev
I recommend against directing people to UGC. That's like telling them: "This road's closed. Here, go this way" and redirecting them to a bridge that's out. :) See, if they are creating brand new blank accounts using UGC, they will never be able to successfully register because a brand new account will have 0 entitlements. Better to point people to: https://rhn.redhat.com/rhn/sales/LoginInfo.do It was specifically designed for this purpose. ==== On the GUI screen with three buttons: [o] I have an existing Red Hat Login [ ] I dont have a login. I need to create one [ ] Tell me why I need to register and provide a Red Hat Login It should be changed to look like this: [o] I have an existing Red Hat Login [ ] Tell me why I need to register and provide a Red Hat Login (i) Tip: Don't have a Red Hat Login? Please visit: https://rhn.redhat.com/rhn/sales/LoginInfo.do ========= Why Register? Screen also needs the language regarding creating a new login completely taken out.
I've updated the link to point at LoginInfo.do instead. The client side changes to get rid of the create login checkbox will be in rhel 5.2 and 4.7, iirc
Here is the new message: Error Class Code: 2001 ▒ │ │ │ │ Error Class Info: ▒ │ │ │ │ We're sorry! Due to changes in the way we ▒ │ │ │ │ capture information, user ▒ │ │ │ │ creation has been disabled through this ▒ │ │ │ │ process. To continue, please visit ▒ │ │ │ │ -- ▒ │ │ │ │ https://rhn.redhat.com/rhn/sales/LoginInfo.do ▒ │ │ │ │ -- (you may copy and paste) and create a Red Hat login. ▒ │ │ │ │ ▒ │ │ │ │ To complete the process, run rhn_register ▒ │ │ │ │ on the command line and enter ▒ │ │ │ │ your new username and password when ▒ │ │ │ │ prompted. Our sincerest apologies for ▒ │ │ │ │ having you enter your new account ▒ │ │ │ │ information twice.
(In reply to comment #7) > I've updated the link to point at LoginInfo.do instead. The client side changes > to get rid of the create login checkbox will be in rhel 5.2 and 4.7, iirc yep, rhel- 4.7 and 5.3
Passes QA, 17-MAR