Review `f-user-realm`

Do we still need the stale f-user-realm branch?

• Investigated whether it is still relevant and desired
• Depending on outcome, either ...
  • ... deleted branch ...
  • ... or created proper EnhancementProposed issue and MR

added Statusnext label

changed iteration to Sprint Jul 25, 2022 - Aug 7, 2022

assigned to @salexan

changed iteration to Sprint Sep 5, 2022 - Sep 18, 2022

added Task label

removed iteration Sprint Sep 5, 2022 - Sep 18, 2022

changed the description

added (A label

changed iteration to Sprint Jun 24, 2024 - Jul 7, 2024

added P3 label

set weight to 1

added Statustodo label and removed Statusnext label

added P2 label and removed P3 label

In administration.py:

def _update_user(name: str,
                 realm: Optional[str] = None,
                 password: Optional[str] = None,
                 status: Optional[str] = None,
                 email: Optional[str] = None,
                 entity: Optional[Entity] = None, **kwargs):
  (...)
        return con.put_form_data(entity_uri_segment="User/" + (realm + "/" + name if realm is not None else name), params=params, **kwargs).read()
  (...)

does the update of a user.

We can see that the function behaves differently when a realm is provided - currently this is not possible using the command line tool.

@timm Do you see a use case where this is necessary. Is providing the realm explicitly in the URL required for doing the update when multiple realms are used? Can you point us to documentation of the realm URL endpoint if it exists?

Currently I would assume, that the feature is necessary.

assigned to @timm

marked the checklist item Investigated whether it is still relevant and desired as completed

added Statusdoing label and removed Statustodo label

removed iteration Sprint Jun 24, 2024 - Jul 7, 2024

changed iteration to Sprint Jul 8, 2024 - Jul 21, 2024

removed iteration Sprint Jul 8, 2024 - Jul 21, 2024