Mailinglist Archive: yast-devel (233 mails)

< Previous Next >
Re: [yast-devel] GUI related questions about registration
  • From: Martin Schmidkunz <mschmidkunz@xxxxxxx>
  • Date: Mon, 5 Oct 2009 13:55:45 +0200
  • Message-id: <DB2AAE6D-6798-4E5B-9FBF-B3681621A366@xxxxxxx>
Hi,

I just spoke with jdsn and tgoettlicher and the concerning the registration GUI we propose:
* user enters just some registration credentials and sends them to the registration server
* if the server certificate of the registration server or the certificate issuer is not found on the appliance the user gets an error page stating something like: "Certificate Problems - It is not sure that the server you are trying to contact can be trusted. To protect you from malicious software no update server is registered. Please contact your admin in order to check the certificate configurations." (or if admin is logged in, a link to certificate configuration can be shown).
The fix of the error would be that the sys admin enters the certificate in the certificate management module.
The proposed way avoids that users install insecure stuff on their machine because they just clicked away another annoying pop up.

A proposal of registration module can be found at:
http://w3.suse.de/~mschmidkunz/webyast_7/registration.html

If used during first run workflow the buttons would be of course in wizard style.

The system name should be an editable text entry and should be already filled with current host name.
The system name is the name by which the system is represented in the Novell Customer Center.
I think it is a nice and useful feature.
Nonetheless I have two issues about that:
* Should we make it more obvious to the user, what this credential means? e.g. tooltip?
* Is it planned, that by "default" registering webYaST machines means that the system appears in the Novell Customer Center?

Another issue is that we obviously don`t know exactly which credentials need to be provided to register successfully on a registration server.
Therefore it might happen that after sending the form, the form is returned to the user representing previous entries plus new entry fields.
This seems quite annoying but it seems to be the only solution since it is not known, which data is needed.
Question is: do we want to stick with the solution?
Another idea would be that by creating the appliance the registration details are set somehow (e.g. ISV 1 says, that he wants an email- address, a registration code and country to be in the form and ISV 2 would only choose only registration code).
What do you think about that?

Looking forward to your comments!


Cu,

Martin

---
Martin Schmidkunz
User Experience Specialist
mschmidkunz@xxxxxxxxxx
+49 (0) 911 740 53-346
---
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
---
Novell® Making IT Work As One™

--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx

< Previous Next >