Figure 34.1 Dialog Box for ENCRYPTKEY=
See Also
“AUTHLIB” in Base SAS Procedures Guide
AES Encryption and Referential Integrity Constraints
Data files with referential integrity constraints can use AES encryption. All primary key
and foreign key data files must use the same encryption key that opens all referencing
foreign key and primary key data files.
Passwords and Encryption with Generation Data Sets, Audit Trails,
Indexes, and Copies
SAS extends password protection, SAS Proprietary encryption, and AES encryption to
other files associated with the original protected file. This includes generation data sets,
indexes, audit trails, and copies. You can access protected or encrypted generation data
sets, indexes, audit trails, and copies of the original file. The same rules, syntax, and
behavior for invoking the original password protected or encrypted files apply. SAS
views cannot have generation data sets, indexes, or audit trails. For more information
about encryption, see “SAS Proprietary Encryption” on page 732 and “AES Encryption”
on page 733.
Blotting Passwords and Encryption Key Values
Check the SAS Log
You need to check the SAS log to ensure that any password value or encryption key
value is blotted out. This applies to the READ=, WRITE=, ALTER=, PW=, and
ENCRYPTKEY= options.
In most cases, placing the password=value pair on a separate line blots the value:
data &ds(
read=secret
encrypt=aes
encryptkey=evenmoreso
);
x=1;
run;
Blotting Passwords and Encryption Key Values 735