3.16 - "Institutional" group missing in "groups" table

[yvesgoupil]

There is an anomaly that disturbs the authentication process, a default group is missing in the "groups" table. In my case, the group "Institutional" was missing. As the Default group was fortunately present, the login with the admin user created by populateLDAP.sh could be done.
But for Marc, it was the group "Default" that was missing and he had to create this group in the table so that the login could be done.
Here is my "groups" table after the installation from scratch done on February 23rd:

OpenWIS=> select * from groups;
id | name | description | email | referrer | reserved | isglobal
----+---------+-------------+-------+----------+----------+----------
1 | DEFAULT | | | | n | n
(1 row)

Here are the ERRORS in the log openwis_security_service.log
...
2023-02-23 15:00:46,094 ERROR [org.openwis.usermanagement.GroupManagementServiceImpl] - LDAP Exception : The global group ou=GLOBAL,ou=groups,dc=opensso,dc=java,dc=net doesn't exist
LDAPException: No Such Object (32) No Such Object
LDAPException: Server Message: The search base entry 'ou=GLOBAL,ou=groups,dc=opensso,dc=java,dc=net' does not exist
LDAPException: Matched DN: ou=groups,dc=opensso,dc=java,dc=net
...
2023-02-23 15:19:33,084 ERROR [org.openwis.usermanagement.UtilEntry] - LDAP Exception : The object uid=openwis,ou=people,dc=opensso,dc=java,dc=netdoesn't exist
2023-02-23 15:20:07,744 INFO [org.openwis.usermanagement.UserManagementServiceImpl] - Initializing Centre DcpcDev, default admin openwis
2023-02-23 15:20:07,747 ERROR [org.openwis.usermanagement.UtilEntry] - LDAP Exception : The object ou=GLOBAL,ou=groups,dc=opensso,dc=java,dc=netdoesn't exist
2023-02-23 15:20:07,747 INFO [org.openwis.usermanagement.GroupManagementServiceImpl] - Creating Global Group node
2023-02-23 15:20:07,754 ERROR [org.openwis.usermanagement.UtilEntry] - LDAP Exception : The object cn=Institutional,ou=GLOBAL,ou=groups,dc=opensso,dc=java,dc=netdoesn't exist
2023-02-23 15:20:07,754 INFO [org.openwis.usermanagement.GroupManagementServiceImpl] - Creating Global Group Institutional
..

But at the end, the group "Institutional" is not created.

• March, 16th 2023

I've created the missing group with this postgresql request:
OpenWIS=> insert into public.groups(id,name,description,email,referrer,reserved,isglobal) VALUES (3,'Institutional','','',NULL,'n','y');

OpenWIS=> select * from groups;
id | name | description | email | referrer | reserved | isglobal
----+---------------+-------------+-------+----------+----------+----------
1 | DEFAULT | | | | n | n
2 | test | | | | n | n
3 | Institutional | | | | n | y
(3 rows)

Yves.

[abrmh]

Installing from scratch Opendj and OpenAM also doing all the necessary installations and configurations
listed below
• Check OpenAM/OpenDJ connectivity
• Add openWis Use attributes
• Openwis security configuration
• IdpDiscovery
• IDP Setup
• Openwis security services,
• LDAP initialization
after LDAP initialization, DEFAULT and institutional are created in the LDAP.
• creation of a new PostgresSql database
• Generation of Fedlets
After launching the admin portal, the rest of the tables are created in a Postgressql database.

In the groups table, both DEFAULT and institutional groups are created.

The connection to the admin-portal was successful.

[yvesgoupil]

Same test on MF side.
DB OpenWIS deleted and re-created.
Installation from scratch and configuration of OpenDJ/OpenAM and Openwis security-service
LDAP initialization (populateLDAP)
Launch of admin portal -> the missing tables are created including the 'groups' table.
The Service Provider admin portal is added in OpenAM
The groups Default and Institutional are present in 'groups' table
Logging tests OK on both admin and user portal..

I propose to consider this ticket closed since the error could not be reproduced on Akka and MF side.