Sunday, 19 October 2014

Interesting glitch with IBM Tivoli Access Manager 6.1.1 when creating Policy

This is what I was running: -

/opt/PolicyDirector/sbin/mgrsslcfg -config -f no

and this is what I was seeing: -

Aborted (core dumped)

which, I think you will agree, is less than helpful.

This is what I had installed: -

rpm -qa | grep -i 6.1.1

PDWebADK-PD-6.1.1-8.i386
PDAuthADK-PD-6.1.1-8.i386
PDAcld-PD-6.1.1-8.i386
PDlic-PD-6.1.1-0.i386
TivSecUtl-TivSec-6.1.1-2.i386
PDWPM-PD-6.1.1-8.i386
PDMgr-PD-6.1.1-8.i386
PDWebRTE-PD-6.1.1-8.i386
PDMgrPrxy-PD-6.1.1-8.i386
PDWeb-PD-6.1.1-8.i386
PDRTE-PD-6.1.1-0.i386
PDJrte-PD-6.1.1-8.i386


Note that the PDRTE component was back-level.

I thought I'd patched things up.

Once I applied the fix: -

rpm -Uvh /tmp/fixes/PDRTE-PD-6.1.1-8.i386.rpm

things started working better: -

/opt/PolicyDirector/sbin/mgrsslcfg -config -f no

Creating the SSL certificate.  This might take several minutes.
The SSL configuration of the Tivoli Access Manager policy server
has completed successfully.

The policy server's signed SSL certificate is base-64 encoded and
saved in text file "/var/PolicyDirector/keytab/pdcacert.b64."

This file is required by the configuration program on each machine
in your secure domain.

which is nice.

No comments:

Note to self - use kubectl to query images in a pod or deployment

In both cases, we use JSON ... For a deployment, we can do this: - kubectl get deployment foobar --namespace snafu --output jsonpath="{...