This requirement depends on the client application. If necessary, use this resource to authorize users for requests: [prefix.]USER.AUTH. prefix is the optional resource name prefix as specified by the HWISAFPF parameter. This resource enables you to define a user so that, when accessing the service, the service acts as if the user is APF authorized.
The examples use the FACILITY resource class (HWISAFCL=FACILITY) and the HI$RV resource name prefix (HWISAFPF=HI$RV).
Example: Grant User Authorities Using CA ACF2 for z/OS
To define the security resources and authorize a user (usern), issue CA ACF2 for z/OS commands in TSO, for example:
[ACF] SET RESOURCE(FAC) COMPILE * $KEY(HI$RV) TYPE(FAC) USER.AUTH UID(usern) SERVICE(READ) ALLOW STORE [END]
Example: Grant User Authorities Using CA Top Secret for z/OS
To define the security resources and authorize a user (usern), issue CA Top Secret for z/OS commands in TSO, for example:
TSS ADDTO(acid) IBMFAC(HI$RV) TSS PERMIT(usern) IBMFAC(HI$RV.USER.AUTH) ACCESS(READ)
Example: Grant User Authorities Using RACF
To define the security resources and authorize a user (usern), issue RACF commands in TSO, for example:
RDEFINE FACILITY HI$RV.USER.AUTH UACC(NONE) SETROPTS RACLIST(FACILITY) REFRESH PERMIT HI$RV.USER.AUTH CLASS(FACILITY) ID(usern) ACCESS(READ)
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|