USE SECURELY STORED API AUTHORIZATION STRING

It took much longer to write this follow-up to the API AUTHORIZATION STRING STORAGE post than I had anticipated. I was tasked with something specific to Avaya IP Office however, in classic Avaya fashion, the tools offered fall way short of the task. Alas, I have decided to use use the “IP Office 11.0 Management API” to demonstrate how to use the stored secure authorization string generated in the previous

API Authorization String Storage

I’ve been interfacing PowerShell scripts with APIs lately and have identified a need for securing my credentials at rest for those applications that require sending authenticated headers. My solution performs the base64 encoding transform, commonly required by web-based APIs, on string input provided at run time and stores it as an encrypted standard string for later use. This process is not straightforward which is odd, considering the obvious need for

Install RaNCID With Gitweb On Ubuntu 20.04 LTS

Wow! CENTOS 8 didn’t last long. As you may have heard by now CENTOS will be front-running RHEL  from now on and is no longer considered stable or Enterprise-ready by my company so we are re-standardizing on Ubuntu 20 LTS. This post is a rehash of the previous “INSTALL RANCID WITH GITWEB ON CENTOS 8” article, configuring the same features for Ubuntu (Rancid w/ GIT; scheduling CRON; setting up email

Install RaNCID With Gitweb on CentOS 8

A contemporary overview of the RaNCID installation and configuration