1.0  Project Description

    The iSCSI Target stores persistent data in standard
    configuration files.  It should use the SMF repository
    to store the persistent data.

    1.1  Definition

	See the case directory for more details. The scf_design
	file describes and addresses the high level design, and address the
	RBAC authorization scheme.  The scf_schema file
	describes the iSCSI Target SCF properties and property
	groups.

    1.2  Motivation, Goals, and Requirements

	Storing persistent data using SMF repository will make
	the iSCSI Target conform to the SMF policy.  The benefit of
	this project is to provide a common repository to store
	configuration data.  The consumer of the iSCSI Target will reduce
	the overhead of learning a new system of service management
	and configuration.

    1.3  Changes From the Previous Release

	This is a change from PSARC 2005/441.  This will be a micro/
	patch release.  The changes are moving persistent data stored
	in files to the SMF repository.  The persistent data are project
	private and managed by the iSCSI Target daemon.

	After moving the persistent data to the SMF repository, the
	access of the persistent data needed the RBAC authorization from the
	svccfg(1M) and the iSCSI Target daemon.

	The following changes are proposed for this case:

	iscsitgt.xml:
		Add RBAC authorization for action_authorization and
		value_authorization.

	auth_attr:
		Add authorization attributes:
		   solaris.smf.value.iscsitgt
		   solaris.smf.read.iscsitgt

	prof_attr:
		Add iSCSI Target Management rights profile.

	iSCSI Target Daemon:
		Add SCF functionality and RBAC authorization.

    1.4  Program Plan Overview

	1.4.1  Development

	   Make the above changes to the iSCSI Target Daemon.

	1.4.2  Quality Assurance/Testing

	   Standard iSCSI PIT test, this tests the iscsitadm(1M) and
	   verification of the persistent data.

	   Add negative and positive testing of security.

	1.4.3  Documentation

	   iscsitadm (1M) will be  modified to document that RBAC 
	   authorization is required to create/modify/delete iSCSI 
	   persistent data.

	1.4.4  Release Cycle

	   The schedule release is for Nevada and possible Solaris
	   update.

    1.5  Related Projects

	1.5.1  Dependencies on Other Sun Projects

	   PSARC 2007/177 smf(5) enhancements for storage of
	   sensitive properties

2.0  Technical Description

    2.1  Architecture

	The basic archicture of iSCSI is unchange except
	for the changes described in section 1.3.

    2.2  Interfaces

	   The interface is Project Private and Evolving.  This
	   interface is iscsitadm and iscsi target daemon.

    2.4  Compatibility and Interoperability

	2.4.7  Compatibility with Earlier and Future Releases

	   There is no changes to the interface (iscsitadm(1M)).

	   The persistent data will be converted from XML to
	   SCF upon this upgrade.  After the upgrade, the persistent
	   data cannot revert back to the XML format.

    2.6  Failure and Recovery

	   This project is dependent on the failure and recovery
	   mechanism of SCF.

    2.7  Security

	   Issue:
	      This project stores CHAP secrets in the SMF repository, this
	      can be a potential security issue because the CHAP secrets
	      are stored in clear text.

           Solution:
              The CHAP secret will be obscured using a  base 64 encoding 
              technique.

	   Issue:
	      The current SMF framework allows any user to view the SMF
              repository.

	   Solution:
	      PSARC 2007/177 prevents the reading of protected data by
	      unauthorized user.  Iscsi Target will add a 
	      'read_authorization' property to all the pgroups
	      that needed the protected data authorization.

           Issue:
              RBAC authorization

           Solution:
	      We propose the following RBAC authorizations for managing
	      iSCSI Target properties (auth_attr(4)):

		solaris.smf.value.iscsitgt:  Authorization to change
			iSCSI Target SCF properties.
		
		solaris.smf.read.iscsitgt:  Authorization to read
			iSCSI Target SCF protected properties.  The
			protected properties implementation is dependent
			on PSARC/2007/177.

              We will add an iSCSI Target Management rights profile to
	      the iSCSI Target service (prof_attr(4)):

                  ISCSI Target Management:::ISCSI Target Management:\
                  auths=solaris.smf.value.iscsitgt,\
                        solaris.smf.read.iscsitgt,\
                        solaris.smf.action.iscsitgt;\
			help=RtIscsitgtMngmnt.html

              The iSCSI Target pgroups will be created with the
              property 'value_authorization' and 
              value 'solaris.smf.value.iscsitgt'.

              The iSCSI Target pgroups needed the protected data
              requirement will be created with the
              property 'read_authorization' and
              value 'solaris.smf.read.iscsitgt'.


3.0  Release Information

   3.2  Installation

	Other than changes documented in 2.4.7 there is no
	changes to the current installation procedure.

   3.2.5  Upgrade

	This changes will upgrade per section 2.4.7.