AUTHLIB Procedure
- Syntax
- Overview
- Concepts
- Using
- Results
- Examples Binding a Physical Library That Contains Unprotected Data SetsBinding a Physical Library That Contains Password-Protected Data SetsBinding a Library When Existing Data Sets Are Protected with the Same PasswordsBinding a Library When Existing Data Sets Are Protected with Different PasswordsChanging Passwords on Data SetsChanging Metadata-Bound Library PasswordsUsing the REMOVE StatementUsing the REPORT StatementUsing the TABLES StatementBinding a Library When Existing Data Sets Are SAS Proprietary EncryptedBinding a Library When Existing Data Sets Are AES-EncryptedBinding a Library with an Optional Recorded Encryption Key When Existing AES-Encrypted Data Sets Have Different Encryption Keys Binding a Library with Required AES Encryption When Existing Data Sets Are Encrypted with the Same Encryption KeyChanging the Encryption Key on a Metadata-Bound Library That Requires AES EncryptionBinding a Library with Existing Data Sets That Are AES-Encrypted with Different Encryption KeysChanging a Metadata-Bound Library to Require AES Encryption When Existing Data Sets Are Encrypted with Different Encryption KeysUsing the REMOVE Statement on a Metadata-Bound Library with Required AES EncryptionResetting Credentials on Imported SecuredLibrary Objects
REPORT Statement
For a specified metadata-bound library, compares physical library contents with corresponding metadata objects (in order to identify any inconsistencies).
| Requirement: | The AUTHLIB REPORT statement requires a connection to the target metadata server. For more requirements, see Requirements for Using the REPORT Statement. |
| Tip: | Each password and encryption key option must be coded on a separate line to ensure that they are properly blotted in the log. |
| Example: | Using the REPORT Statement |
Syntax
REPORT
Optional Arguments
LIBRARY=libref
name of the physical library on which to report binding information.
If the LIBRARY= option is not specified, then the physical library from the PROC AUTHLIB
statement is used.
| Alias | LIB=, DDNAME=, DD= |
| Restriction | The physical library specified cannot be a concatenated library, temporary library, or accessed through a SAS/SHARE server and must be processed by an engine that supports metadata-bound libraries. |
ENCRYPTKEY=key-value
specifies a key value for an AES encryption.
| Tip | The ENCRYPTKEY= value is a passphrase that can be up to 64 characters long from which the actual AES encryption key is later derived, but it is referred to as the encryption key in most SAS documentation. |
| See | ENCRYPTKEY= Data Set Option in SAS Data Set Options: Reference |
Details
Requirements for Using the REPORT Statement
An administrator uses the REPORT statement to identify any inconsistencies between
a physical metadata-bound library and its corresponding metadata objects.
In order to use the REPORT statement, you must meet the following criteria:
-
The SAS session runs under an account that has host-layer Read access to the target physical library. This is necessary in order to assign the libref.
-
The SAS session connects to the metadata server as an identity that has the ReadMetadata permission for the target secured library object and secured table objects.
-
If the library has secured library object location information and the secured library object cannot be obtained, then you will need to use the AUTHADMIN=YES option in the LIBNAME= statement in order to assign the library.
Reporting Inconsistencies
The REPORT statement is used to report any inconsistencies between the physical library
contents and the
corresponding metadata objects.
Inconsistencies between the metadata security information in the physical directory,
data sets, the secured library, and secured table objects might occur if the metadata
or the operating system files are manipulated using nonstandard SAS processing. For
example, an operating system data set copied from one directory into a metadata-bound library directory using an operating
system copy utility will not have the appropriate security
information for that metadata-bound library. Another example is that an administrator
might mistakenly delete a secured library or secured table object using SAS Management Console.
The REPORT statement reports the secured table and metadata-bound library security
information for each data set in the operating system directory of the library. This
data set information is grouped
by the metadata-bound library attributes that all the data sets share. If any data
sets in the physical library are correctly registered to the secured library object
for the library and have the required passwords, then those data sets and attributes
will be listed as the first grouping in the report. Subsequent groupings are for data
sets with either passwords that differ from the metadata-bound library passwords or
whose metadata-bound library security information does not match the metadata-bound
library location registered for the operating system directory.
Copyright © SAS Institute Inc. All rights reserved.