For the installation I followed the instructions in the documentation:
https://opaldoc.obiba.org/en/latest/admin/installation.html
The software requirements are met:
openjdk version “1.8.0_312”
mysql Ver 15.1 Distrib 10.3.32-MariaDB
MongoDB shell version v3.6.8
R version 3.6.3
As the VM is a Ubuntu-20.04 distribution I simply installed the debian packages for agate, mica2, rock and opal:
apt-get install opal
apt-get install opal-python-client
apt-get install rock
apt-get install mica2
apt-get install mica-python-client
In R I installed the opalr package:
install.packages("opalr")
The configuration file I left unchanged, because this VM is currently only accessible internally via IP, not a public domain:
https://opaldoc.obiba.org/en/latest/admin/configuration.html
All services, agate, mica2, rock, mariadb, mongod and opal are running; at least according to their statis with:
systemctl status
From within R I can connect to the Rock-server and execute the example on Using R — Opal documentation, successfully.
There is one major problem: I can’t connect to OPAL via the web interface, though. The login page, http://192.168.100.94:8080/ui/index.html, always denies the authentication.
/var/log/opal/rest.log showed only “unknown” for user. Otherwise there is little insight from the logs:
{“@timestamp”:“2022-01-11T19:47:09.791+01:00”,“@version”:“1”,“message”:“/auth/sessions”,“logger_name”:“org.obiba.opal.web.security.AuditInterceptor”,“thread_name”:“qtp1522875398-31”,“level”:“WARN”,“level_value”:30000,“method”:“POST”,“ip”:“10.0.8.4”,“username”:“Unknown”,“status”:“403”}
I thought the default credentials are “administrator/password”. I tried to update the password with
dkpg-reconfigure opal
But any password entered there didn’t change the SHA256 entry in /etc/opal/shiro.ini. I then used
shiro-hasher -p password
to create the hash for “password” which pasted into /etc/opal/shiro.ini:
administrator=$shiro1$SHA-256$500000$TIBDu25yk3IYyUKgRJf2hQ==$Sd/ChI2QCqf4diT5iSVTbSZTt2V6XbNy6/xEiv8NC2k=,admin
I then restarted agate, mica2 and opal. As far as I understand authentication is down by agate, and shiro.ini is part of its configuration.
I still only got. when trying to log in. Capital “A” or not, i.e. “a” (“administrator”) didn’t make any difference either:
[image]
As far as I know, the data, and also user data is held in the mongodb database, right? /var/log/mongodb/mongodb.log didn’t show any connection attempts, though.
I connected on to the mongo shell on the console:
mongo --port 27017
There are no users or roles in the “agate” database defined:
use agate switched to db agate db.getRoles()
During what part of the installation are the user credentials in agate created? Doing dpkg-reconfigure agate allows to set a password for “administrator”. But there are still now users or roles in the agate database:
use agate; switched to db agate db.getUsers()
db.getRoles()
And login in the web interface also still fails.