Conformance Statement

Product Standard: RBAC

This form contains a series of questions that need to be answered. As you go about answering the questions, please keep the following things in mind:

Please edit with a html editor, and try to preserve all formatting.

While it is not required that each question be answered at this time, all questions must have answers before the response is submitted to The Open Group for review and publication.

Questions on this system should be addressed to the Conformance Statement manager at The Open Group.

Enter the name of the Organization that produced the implementation and the name of the author of the Conformance Statement.

Organization
Author

1. RBAC

Product Information

Enter the product name, version/release number, and product supplier for each product required to meet the conformance requirements.

Product Identification	Version/Release Number	Product Supplier

Environment Specification

Product registration applies to software products operating in a specific hardware or hardware/software environment.

A product may be registered in all members of a binary-compatible family of products on the basis of a single test report.

Answer the questions for each binary-compatible family. Alternately, provide the answers in the Appendix at the end of this document.

Testing Environment	Binary-compatible Family	Portability Environment	Indicator of Compliance	Compliance Details
		None.	None.	Test Suite: Test Report:
		None.	None.	Test Suite: Test Report:
		None.	None.	Test Suite: Test Report:
		None.	None.	Test Suite: Test Report:
		None.	None.	Test Suite: Test Report:

Temporary Waivers

Enter the waiver number and expiry date for each temporary waiver granted by The Open Group.

	Waiver Number	Expiry Date

1.1 Optional Features

1.1.1 Roles

Question 1: Does the implementation support each of the roles below as described in the O-ARMOR specification?

Response

Audit Administrator	(auditadm)	Yes/No
File System Administrator	(fsadm)	Yes/No
Software Package Administrator	(pkgadm)	Yes/No
Security Administrator	(secadm)	Yes/No
Service Administrator	(svcadm)	Yes/No
System Operator	(sysop)	Yes/No
User Administrator	(useradm)	Yes/No

Rationale

The O-ARMOR Standard states that these roles are optional.

Reference

Brand Program Documentation, January 2013, RBAC Product Standard (X1301).

1.1.2 Additional Roles

Question 2: What additional roles does the implementation support?

Response

Enter your response in the area below, using as many lines as necessary. Please use the same format as in 1.1.1

Rationale

The O-ARMOR Standard states that additional roles may be supported.

Reference

Brand Program Documentation, January 2013, RBAC Product Standard (X1301).

1.1.3 Role Names

Question 3: Does the rbac_chkauth() function accept role names (as well as user names) passed as the username argument?

Response

Yes/No

Rationale

The O-ARMOR Standard states that rbac_chkauth() function may accept role names (as well as user names) passed as the username argument.

Reference

Brand Program Documentation, January 2013, RBAC Product Standard (X1301).

2. Appendix

This appendix contains additional, explanatory material that was provided by the vendor.

3. Change History

Date	Name	Comment
New

The Open Group, UNIX, and the Open Brand X logo are registered trademarks of The Open Group.

[ Home ] [ Testing Home ] [ Conformance Statement Library Home ] [ Search Conformance Statements ] [ Send Feedback ]