Mailinglist Archive: yast-devel (163 mails)

< Previous Next >
[yast-devel] Re: [Bug 537200] [task] [fate 307141] Admin password and e-mail rest service
  • From: Jiří Suchomel <jsuchome@xxxxxxx>
  • Date: Tue, 8 Sep 2009 14:37:35 +0200
  • Message-id: <200909081437.35634.jsuchome@xxxxxxx>
On Tuesday 08 of September 2009 13:44:03 Bugzilla_NoReply Bugzilla_NoReply

User kkaempf@xxxxxxxxxx added comment

--- Comment #3 from Klaus Kämpf <kkaempf@xxxxxxxxxx> 2009-09-08 05:44:01
MDT --- (In reply to comment #2)

Lets discuss such things on yast-devel !

Move the final documentation into git, link it from the wiki, and put the
wiki url here.

Admin password module proposal (fate #307141)

- change administrator (root's) password
- configure notification e-mail addresses
(mail aliases for root)

- possibly more in the future


singleton class Administrator

string password
list aliases

Why would aliases be a list ? I understand the request as "single email
address" to send mails to. And, is 'alias' the right name for this ?

I'm thinking about the implementation as an entry in /etc/aliases (we have
MailAliases.ycp for that). And here it is possible to assign multiple aliases
for one e-mail.

(access the system, probably using YaPI::USERS)


You don't need set/get prefixes in Ruby.

Ah, well, get_aliases is actually part of find method.

set_password and set_aliases are meant as a methods that actually access the
system (call YaPI or whatever), not that they just fill the variables.

Or there can be one save method, handling both, but I thought more granularity
can help testing.



URL: /administrator

REST service pseudo-code:

# GET method
def show

read and return current mail aliases

# PUT method
def update (params)

if password changed

save the new password

if aliases changed

save new list of aliases

Jiri Suchomel

SUSE LINUX, s.r.o. e-mail: jsuchome@xxxxxxx
Lihovarská 1060/12 tel: +420 284 028 960
190 00 Praha 9, Czech Republic
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups