I can confirm that the official docs are missing couple points, which caused me some headaches when setting up the local Manage first time.
As for the user sync process between MAS Core and other MAS apps (Manage included): it does not transmit passwords for a reason. MAS uses the microservices concept (to some extend at least) and the authentication part is done in a dedicated service (this is CoreIDP pod to be precise).
Another dirty way to set the password for local Manage is to use E-signature password. Procedure is as follows:
Original Message:
Sent: Wed November 08, 2023 04:35 PM
From: Dirk Huppertz
Subject: Authentication in the local Maximo Manage dev environment
Hi Arif,
sorry, but I cannot confirm.
Here a snippet from the dockerfile.rtf
And a snipped from the manual at https://www.ibm.com/docs/en/mas-cd/maximo-manage/continuous-delivery?topic=environment-building-deploying-development-images
As you can see, only the crypto key is set, not the cryptox key.
The password field in the maxuser object is an cryptox field, so you need to set the key.
Kind regards
Dirk
------------------------------
Dirk Huppertz
Senior Project Manager
S&T Deutschland GmbH
Aachen
Original Message:
Sent: Wed November 08, 2023 04:19 PM
From: Arif Ali
Subject: Authentication in the local Maximo Manage dev environment
> you have to set the cryptox key properly (this is missing in the manual!!)
This is mentioned in the Dockerfile/Containerfile which is available to download. The file comes out as a rtf file but it is a standard image file. When Manage is installed, it is installed with randomly generated crypto/cryptox keys (one can also manually define the same at the time of the installation). So, I have to assume that we are all pulling the images from OpenShift after the Manage is installed.
------------------------------
Arif Ali
Original Message:
Sent: Wed November 08, 2023 03:52 PM
From: Dirk Huppertz
Subject: Authentication in the local Maximo Manage dev environment
Here are a few new findings:
- The synchronization process from MAS Core to Manage does not transmit passwords
- To use the preset passwords (form a migrated 7.6 db or from demo data) in the local container you have to set the cryptox key properly (this is missing in the manual!!)
- new password (in the Manage database) cannot be set via UI, so you have to set it via Interface (MXLoader as described by Witold or automation script or ...)
Wondering what IBMs idea was, how to manage the passwords in manage for the dev container?
------------------------------
Dirk Huppertz
Senior Project Manager
S&T Deutschland GmbH
Aachen
Original Message:
Sent: Mon November 06, 2023 03:26 AM
From: Dirk Huppertz
Subject: Authentication in the local Maximo Manage dev environment
Hi Diego,
I had the same issue.
My guess is that the issue is related to the CrypoX key.
Unfortunately, I haven't had time to analyze the root cause further.
But, I found a way to work arround it:
- Create an automation script to set the password of maxadmin
- Create an API-key for a user (i.e. maxadmin)
- Start the local container
- Call the automation script using the API key for authentication via REST API
- Now, maxadmin has the new password in the manage database and you can login π
Regards
Dirk
------------------------------
Dirk Huppertz
Senior Project Manager
S&T Deutschland GmbH
Aachen
Original Message:
Sent: Sat November 04, 2023 11:50 AM
From: Diego Visentin
Subject: Authentication in the local Maximo Manage dev environment
I have successfully created a local Maximo Manage development environment by extracting images from a MAS 8.11.
With a few tricks I am able to connect but I suspect there is some problem with the passwords initially stored on the database by the synch process from the MongoDB of the MAS.
Can anyone who uses it tell me if they have experienced any problems using the MAS user credentials in the derived "dev" environment?
------------------------------
Diego Visentin
EAM BU Director
Tempestive S.p.A.
------------------------------