#10414: Remove the list of associated groups of logged in user from the User Details modal window

[mahmoudadel54]

Description

In this PR, handling hiding the group info in the user details modal by adding a cfg in Login plugin 'hideGroupUserInfo' is implemented. If 'hideGroupUserInfo' is configured into Login plugin cfg,
{ "name": "Login", "cfg": { "toolsCfg": [{"hideGroupUserInfo": true}] } }
the group info into user details modal will not be shown.

Please check if the PR fulfills these requirements

• The commit message follows our guidelines: https://github.com/geosolutions-it/MapStore2/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (check one with "x", remove the others)

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Other... Please describe:

Issue

#10414

What is the current behavior?
#10414

What is the new behavior?
If 'hideGroupUserInfo' is configured into Login plugin cfg, the group info into user details modal will not be shown.

Breaking change

Does this PR introduce a breaking change? (check one with "x", remove the other)

• Yes, and I documented them in migration notes
• No

Other useful information

For Login plugin (cfg.toolsCfg[0].hideGroupUserInfo) ---> the first index into toolsCfg is for userDetails tool based on this order as I think:

• MapStore2/web/client/plugins/Login.jsx

  Line 104 in bc4aefc

  tools: [UserDetails, PasswordReset, Login],

• MapStore2/web/client/plugins/Login.jsx

  Line 86 in bc4aefc

  tools: [UserDetails, PasswordReset, Login],

• To enable this, it should be added to all Login plugin
• For the old contexts, it may not work as expected because of the previous cfg into Login plugin

[MV88]

your solutions works only because the user details is the first in the list of tools, but if a project has a custom login plugin this might not work, so I think you have to specify this information as well. Probably it should be mentioned in the migration guidelines because it could be a breaking change in a sense that this configuration may not work there if there are refactors to the login plugin. the index part is import to highlight.

• please add this entry in the migration guidelnes
• improve tests

[MV88]

make sure to run locally documentation to check possible syntax errror

[tdipisa]

@ElenaGallo please test in DEV and let us know if we can backport.

[ElenaGallo]

@tdipisa even the admin can't see the GroupUserInfo section, is this correct?

[tdipisa]

@tdipisa even the admin can't see the GroupUserInfo section, is this correct?

I've commented here:
#10414 (comment)

Something that has not been reported in the ACs. @mahmoudadel54 can you please take a look? Can we do that simply by config or dev is necessary for it?

[mahmoudadel54]

@tdipisa even the admin can't see the GroupUserInfo section, is this correct?

I've commented here: #10414 (comment)

Something that has not been reported in the ACs. @mahmoudadel54 can you please take a look?

Ok I will take a look for it
Dev is necessary for it even we put a config for theis requirement

Is it required to make it optional based on config to show or hide group for admin ? Or group should be shown by default for admin without using config? @tdipisa

[tdipisa]

@mahmoudadel54 thank you for this check. Let's leave this as it is now since it is not so fundamental and the config you have provided is not the default one. @ElenaGallo if there is nothing else we can we can ask @mahmoudadel54 to backport.

[ElenaGallo]

Test passed, @mahmoudadel54 please backport to 2024.01.xx

[mahmoudadel54]

Test passed, @mahmoudadel54 please backport to 2024.01.xx

backport is done ---> #10447