jburns80 Super Contributor.
Super Contributor.
306 views

Updating DB connections post install

So we had UA 4.6.2 running just fine, upgraded to 4.7 and no issue. However after upgrading to 4.7.2 per MF request we are now having a logon issue for our Oracle 12c DB. I'm assuming the install corrupted the credentials somewhere as Everything was working fine until the 4.7.2 install. Does anyone know the way to update these credentials? MF support keeps giving me generic answers and pointing me to documentation that doesn't have anything to do with this. I've tried also searching the web and haven't found anything, I know in the old way you could actually edit an xml file. Any help is greatly appreciated.
Labels (1)
0 Likes
2 Replies
Knowledge Partner
Knowledge Partner

Re: Updating DB connections post install

jburns80 <jburns80@no-mx.forums.microfocus.com> wrote:
>

So we had UA 4.6.2 running just fine, upgraded to 4.7 and no issue.
However after upgrading to 4.7.2 per MF request we are now having a
logon issue for our Oracle 12c DB. I'm assuming the install corrupted
the credentials somewhere as Everything was working fine until the 4.7.2
install. Does anyone know the way to update these credentials? MF
support keeps giving me generic answers and pointing me to documentation
that doesn't have anything to do with this. I've tried also searching
the web and haven't found anything, I know in the old way you could
actually edit an xml file. Any help is greatly appreciated.


Yes. Have done this recently on 4.7.1. (Not oracle though but same
principle)
It is sorta documented.
https://www.netiq.com/documentation/identity-manager-47/identity_apps_admin_472/data/netiq-update-password-for-database-user-tomcat.html

There is a jar that will convert your password into the hashed version that
is expected.

Note each time you run this, it will give you a different hash even with
same input password. This is normal.

Alex McHugh - Knowledge Partner - Stavanger, Norway
Who are the Knowledge Partners
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
Knowledge Partner
Knowledge Partner

Re: Updating DB connections post install

On 1/17/2019 2:57 PM, Alex McHugh wrote:
> jburns80 <jburns80@no-mx.forums.microfocus.com> wrote:
>>

> So we had UA 4.6.2 running just fine, upgraded to 4.7 and no issue.
> However after upgrading to 4.7.2 per MF request we are now having a
> logon issue for our Oracle 12c DB. I'm assuming the install corrupted
> the credentials somewhere as Everything was working fine until the 4.7.2
> install. Does anyone know the way to update these credentials? MF
> support keeps giving me generic answers and pointing me to documentation
> that doesn't have anything to do with this. I've tried also searching
> the web and haven't found anything, I know in the old way you could
> actually edit an xml file. Any help is greatly appreciated.
>
>
> Yes. Have done this recently on 4.7.1. (Not oracle though but same
> principle)
> It is sorta documented.
> https://www.netiq.com/documentation/identity-manager-47/identity_apps_admin_472/data/netiq-update-password-for-database-user-tomcat.html
>
> There is a jar that will convert your password into the hashed version that
> is expected.
>
> Note each time you run this, it will give you a different hash even with
> same input password. This is normal.


The passwords in the ism-configuration.properties hashed passwords can
be generated with the bin/encrypt-password.sh in Identity Governance,
and I think is there in Identity Apps as well.

The DB password should be in Tomcat server.xml and use the same format.

The OSP adminusers.txt file uses a different encrypt format and there is
a JAR for it noted in the docs.


The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.