Edgar Herrera

Background

About Edgar Herrera

I am a responsible, methodical, honest person. I like facing new challenges and love to develop my skills. I am a fast learner and easily abide by the rules. I believe that teamwork is critical to success. I have been working with networking and Linux for 2 years now. When I got into the Splunk account I was able to dig deeper in Linux with CentOS and other distros. I had to troubleshoot permissions, errors in config files with vi, check Splunk’s service with systemctl, provide RCA’s, and document different solutions in the form of knowledge articles to help other engineers. Most issues could be found by looking at Server configs on /etc/ or on Splunk-specific config files in /opt/*. Once in Okta, I was selected to work in Okta Access Gateway (OAG) and Advanced Server Access (ASA), both of which are features Okta provides for On-prem applications and connections to On-Prem servers. OAG is based on CentOS, so whenever a customer is having issues, we have to log in the backend to their servers and search for config files or log analysis in /opt/oag/ to find the root cause of the issue. Issues may be found using nginx -t or systemctl status nginx to view problems in configuration for OAG. I have also needed to gather packet captures and scp them to my own machine in order to better analyze the SSO of an application. I find myself having to use vi, less, grep, cat, sudo, ls, ssh, change permissions more often than not. In ASA, it’s mainly having to check sudo entitlements and permissions within servers and projects for users. I have to check in journalctl when a sudo entitlement is not passed to the servers to find the cause of the issue. I’ve had to help install ScaleFT Service on both Windows and Linux servers and client machines.