http://bugzilla.novell.com/show_bug.cgi?id=537202
User jdsn@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=537202#c6
J. Daniel Schmidt
jdsn - when your module is done please ping me and I add two necesarry methods and add it to default work-flow
Ping! (In reply to comment #5)
The request is kind of funny, because the design of the registration is that the client does not know if it is registered or not.
Which makes me wonder if we shouldn't change this design in the future.
We definitely should. The current system is broken by design (from several points of view ... it may have solved the original issue).
Sure we could agree on a flag file that indicates that the registration ran at least once and then unlock the rest of the interface. Is this enough?
It probably is. What are the alternatives ?
An alternative was implemented. It's even a little better guess if the system is registered. It works like this: You do a GET request to the rest-service at /registration/registration and if the system is registered, it will return its GUID (the ID that was assigned to it by $some registration server $somewhen). We can not fully rely on this guess, as (like I already pointed out) the "registration" is handeled on the server. So if there is a GUID and its length is > 0 then you could assume that the system is registered. If there is no GUID the system did not run a registration successful yet. See as well: http://en.opensuse.org/YaST/Web/Development/Registration -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.