Also look at the prototype_com of SUNWlighttpd14r. In that file we
include auth_attr and prof_attr but with a class of rbac (which as
Srirama says also needs to be added to the CLASSES field of
pkginfo.tmpl). The rbac class merges any additions from the files in
your package into the files in the OS.
Amanda
Raymond Xiong wrote:
> I got it, thanks a lot!
>
> Raymond
>
> On 04/02/09, Srirama Sharma wrote:
>
>> Hi Raymond,
>>
>>
>> Raymond Xiong said the following on Thursday 02 April 2009 12:07 PM:
>>
>>> I am porting ejabberd, which is an XMPP server, and need to
>>> add two new authorizations ("solaris.smf.manage.ejabberd" and
>>> "solaris.smf.value.ejabberd"). I checked existing packages
>>> on sfwnv gate and found some packages (lighttpd14, stunnel,
>>> etc) introduced new authorizations too, but I didn't see
>>> they had any code to do that.
>>>
>>>
>> If you intend to add new RBAC authorizations for the product your are
>> integrating, you could add those entries in the RBAC files
>> (auth_attr/exec_attr/prof_attr/user_attr) present in the sfwnv gate in
>> "usr/src/common/rbac" dir.
>>
>>
>>> Does that mean I just need to request those new authorizations
>>> (for example, by filling a form) during integration time
>>>
>> AFAIK, there is no form which needs to be filled up. I guess you just
>> need to mention about these authorizations in your ARC case materials.
>>
>> During integration, you just need to have the changes you have made to
>> RBAC files (auth_attr/exec_attr/prof_attr/user_attr) listed in the
>> webrev so that someone could review it.
>> Also make sure that the pkginfo of the package which is installing the
>> SMF service manifest and method files have 'rbac' listed under CLASSES
>> field. Some thing like this :
>> CLASSES="none manifest rbac"
>>
>> HTH.
>>
>> Thanks,
>> Srirama
>>
> _______________________________________________
> sfwnv-discuss mailing list
> sfwnv-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/sfwnv-discuss
>
