Mailinglist Archive: yast-devel (163 mails)

< Previous Next >
Re: [yast-devel] Registration Rest Api
  • From: "J. Daniel Schmidt" <jdsn@xxxxxxx>
  • Date: Mon, 21 Sep 2009 17:12:58 +0200
  • Message-id: <200909211712.59687.jdsn@xxxxxxx>
On Friday 18 September 2009 01:50:57 josef reidinger wrote:

Registration Configuration:
---------------------------------
* /registration/config
GET
get registration server

returns:

<registrationconfig>
<server>
<url>https://myregistration.server.com/center/regsvc</url>
</server>
</registrationconfig>

Hi, just few notes.
Why get doesn't get certificate? Maybe someone find usefull to check
server certificate

The idea is, to do all the certificate checking (and downloading the cert from
a url) in the web-client and then the web-client PUTs the certificate itself
to the target system.
PUTting the certificate to the server only imports it to the certificates in
/etc/ssl/certs. Ok, I could check for a fixed file name and dump it again -
sure.


<!-- in case of missing arguments -->

I think that missing argument should be reported as error, also another
controller handle it as error (I plan add specific exception for
arguments missing/invalid). Do you have any reason to respond it as
success response? Also status error is not good I think...thats reason
why status code exist, just report problem in status code and explain
problem in response. Don't mix success registration and problematic.

The design of the registration process is different to any other module that
does configuration stuff.

1. A system does not know if it is registered or not
You need to do a registration to find out. But after you registered you can
not be sure, tthat the system is still registered - only the registration
server knows, and by design you can not query for that status.

2. A system does not know what arguments (values) to ask from the user; it
does not know if there might be something missing in the first place; you need
to do a registration to find out, what arguments are needed for a
registration. Thus the status "missing info" is a valid status within the
workflow and not an error.



Ciao,
Daniel

--
J. Daniel Schmidt <jdsn@xxxxxxx> SUSE Linux Products GmbH
Research & Development Maxfeldstr. 5
GF: Markus Rex, HRB 16746 (AG Nürnberg) D-90409 Nürnberg
--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx

< Previous Next >