Idea ID: 2879095

Enable the feature of limiting runtime logging of parameters from LRE or for Specific user

Status: Waiting for Votes

We have scenario where the users fetch production account secrets from CyberArk and we do not want our users to see/access the secrets from project they from LRE. We need to have an option where we can limit/restrict runtime settings especially for parameter substitution in the logging on a project level or for a specific user.

  • Hi ,

    In our perf.lab. we maintain login template(s) for development teams. (include, modules or libraries). In those we can control the logging behavior with functions like:
    lr_get_debug_level() / lr_set_debug_level().

    You can distribute an include for the teams and/or 'sample code' that they have to add to their script to obtain the credentials. I assume it is in side a company enough to state this as the procedure and state no code modification allowed on those pieces of code.

    You can always in the code overrule the RTS, so enforce some RTS settings  is not good enough.

    How to ask questions

    Reward contributions via likes or 'verified answers'