Skip Navigation

Update the database server

Values in the database server that are used in smart card authentication are stored in the GLB_CONFIG_TAB in the ngaddata database. These values include the following items:
  • The name of the HTTP header that contains the information.
  • The regular expression that is used to extract the information.
A Require Smart Card option is available that appears when you select Smart Card Login.
The SMART_CARD_ENFORCED value is present in the PRV_SECURITY_POLICY_TAB
The following smart card settings are present in GLB_CONFIG_TAB:
  • ALT_HTTP_CAC_REGEX
  • ALT_HTTP_CAC_VARIABLE
  • CAC_CHECK_PRESENT
  • CAC_CHECK_VALID
  • CAC_REGEX
  • CAC_SAN_REGEX
  • HTTP_CAC_REGEX
  • HTTP_CAC_VARIABLE
Definitions of smart card settings
KEY_NAME
Notes
ALT_HTTP_CAC_REGEX
(Operator log on) Alternate regular expression for extracting the mapping ID from the CAC certificate.
ALT_HTTP_CAC_VARIABLE
(Operator log on) Alternate HTTP header variable that contains the mapping ID from the CAC certificate.
CAC_CHECK_PRESENT
(Operator log on) Specifies if the system should check that the CAC certificate is present.
CAC_CHECK_VALID
(Operator log on) Specifies if the system should check that the CAC certificate is valid.
CAC_REGEX
Primary regular expression for extracting the mapping ID from the certificate data passed by the
BlackBerry AtHoc
desktop app during sign on.
CAC_SAN_REGEX
(Operator log on) Alternate regular expression to extract the email address from the Subject Alternative Name in the certificate.
HTTP_CAC_REGEX
Primary regular expression for extracting the mapping ID from the certificate during operator log on.
HTTP_CAC_VARIABLE
Primary HTTP header variable to search for mapping ID during Operator log on.
Correlation of smart card settings between the database and user interface
KEY_NAME
Visible in management system
ALT_HTTP_CAC_REGEX
No
ALT_HTTP_CAC_VARIABLE
No
CAC_CHECK_PRESENT
No
CAC_CHECK_VALID
No
CAC_REGEX
No
CAC_SAN_REGEX
No
HTTP_CAC_REGEX
No
HTTP_CAC_VARIABLE
No