Symantec Identity Suite - Identity Portal / Governance jboss cli commands no longer work
search cancel

Symantec Identity Suite - Identity Portal / Governance jboss cli commands no longer work

book

Article ID: 282336

calendar_today

Updated On:

Products

CA Identity Suite

Issue/Introduction

After performing an upgrade of VAPP 14.4 to VAPP 14.5 the jboss-cli.sh command no longer properly authenticates to IP or IG.

When doing this it connects to the Identity Manager application server and not IP or IG.

Environment

Release : 14.5

Component : IdentitySuite(Identity Suite)

Cause

/opt/CA/wildfly-ig/bin/jboss-cli.xml

Reads:

<default-controller>
    <protocol>remote+http</protocol>
    <host>localhost</host>
    <port>9990</port>
</default-controller>

<!-- Example controller alias named 'Test'
<controllers>
    <controller name="Test">
        <protocol>remote+http</protocol>
        <host>localhost</host>
        <port>9990</port>
    </controller>
</controllers>
-->

Should be:

<default-controller>
    <protocol>remote+http</protocol>
    <host>localhost</host>
    <port>9992</port>
</default-controller>

<!-- Example controller alias named 'Test'
<controllers>
    <controller name="Test">
        <protocol>remote+http</protocol>
        <host>localhost</host>
        <port>9992</port>
    </controller>
</controllers>
-->

/opt/CA/wildfly-portal/bin/jboss-cli.xml

Reads:

<default-controller>
    <protocol>remote+http</protocol>
    <host>localhost</host>
    <port>9990</port>
</default-controller>

<!-- Example controller alias named 'Test'
<controllers>
    <controller name="Test">
        <protocol>remote+http</protocol>
        <host>localhost</host>
        <port>9990</port>
    </controller>
</controllers>
-->

Should be:

<default-controller>
    <protocol>remote+http</protocol>
    <host>localhost</host>
    <port>9991</port>
</default-controller>

<!-- Example controller alias named 'Test'
<controllers>
    <controller name="Test">
        <protocol>remote+http</protocol>
        <host>localhost</host>
        <port>9991</port>
    </controller>
</controllers>
-->

Resolution

This issue will be fixed in 14.5CP1 or if this issue is experienced before the release of 14.5CP1 then open a ticket and request HF_VA-14.5.0-20240327093514-DE594526.tgz.gpg

The workaround is to specify the desired port when using the command.

IP:
./jboss-cli.sh --connect controller=127.0.0.1:9991

IG:
./jboss-cli.sh --connect controller=127.0.0.1:9992