XAC: OBEY doesn't work from a XYGATEAC (XAC) TACL

XAC: OBEY doesn't work from a XYGATEAC (XAC) TACL

Reconcile COMMANDESCAPE character defined in the ACCONF file with those used in conjunction with the ALIAS keyword in the individual commands in the ACACL file

1.  Edit the ACCONF file
2.  Look for the line "COMMANDESCAPE".  This should be near the top of the file

      Example:

       COMMANDESCAPE          <<

3. Edit the ACACL file using the XAC_EDIT_ACL macro.  Find the XAC TACL command from where OBEY is not working and make sure that COMMANDESCAPE is defined and that
    the COMMANDESCAPE character matches the one defined in the ACCONF file.

     Example:

     a. RUN $<vol>.XYGATEAC.XAC INSTALL    (Where $<vol> is the disk volume where XYGATEAC is installed)
     b . XAC_EDIT_ACL
     c.  Find the XAC command(s) and review the ALIAS keyword entries for the XAC command(s).  The COMMANDESCAPE character preceding the "OBEY" or "O" should be the
          same as the one defined in the ACCONF file.
             
      Sample ACCONF ENTRY

       COMMANDESCAPE          <<



        Sample ACACL ENTRY

        COMMAND TACL-255   
         !  This command is used to give SUPER.SUPER privileges to
         !  authorized users.
            DESCRIPTION "Privileged TACL"
            USER 255,255                       !Execute as SUPER.SUPER
         .
         .
         .
         ALIAS "O " "<<OBEY "               !Replace all of the following commands
         ALIAS "OBEY " "<<OBEY "            !with references to XYGATE/AC'S
         ALIAS "O$" "<<OBEY $"              !internal >OBEY command which audits
         ALIAS "O\" "<<OBEY \"              !all activity..
         
        In the above example, the COMMANDESCAPE character defined in the ACCONF file  (<<) matches the ones used with the ALIAS keywords in the ACACL command
        TACL-255.



         If you are unable to locate the solution needed or if you need additional assistance, please Click Here to open a case from our Customer Care Portal.

          
         


 

    • Related Articles

    • XAC: OBEY within a TACL macro does not work as expected in XAC TACL

      An obey command executed from the TACL prompt will be captured and controlled if the ACACL entry has ALIAS entries for OBEY. An obey command within a TACL macro will not be captured or controlled. There are constructs in obey files that if obeyed ...

    • XAC: Error 48 when executing an obey file in an XAC TACL session

      Add the following keyword to the underlying TACL session (the XAC TACL session configured in the telnet service): 1. Edit the ACACL file 2. Add the keyword to the TACL command that is configured in the telnet service, e.g TACL-DYNAMIC-IP: ...

    • XAC: How to configure keystroke auditing for TACL SSH sessions

      Use the following steps to configure XAC auditing for SSH. Add the XAC command. The XAC command requires the following keywords to be included. USER_IGNORED START_LOGGED_ON USER_SWITCH SAFEGUARD_PRIVLOGON Note: If XYGATE User Authentication (XUA) is ...

    • XAC: Eight character volume name causes Invalid OBEY file error.

      Verification: TACL> VOLUME TACL> OBEY $LONGVOL.A234567.XX XAC - Invalid OBEY file. Workaround: After using the XAC VOLUME command use the TACL SYSTEM command without an argument to set the system name to a blank value. TACL> SYSTEM TACL> OBEY ...

    • How to make XAC work with NSDEE

      XAC 6.25 or higher is required for XAC and NSDEE. This is because the NSDEEREG file is included with this version and is required for NSDEE support when telnet or SSH is configured to use XAC. To configure NSDEE with XAC is installed, proceed as ...