Other scenario is if you do not have a datastore at all. Users can authenticate through LDAP for example, but none of their session can be searched.

We upgraded to AM 5.5.1 and we are affected by this issues. Its fixing is important for us.  Which AM version is it planned to be fixed in? Will a patch be released for AM 5.5.1 after the fix?

Ivailo Kolev which use case applies to you? The REST endpoint for querying the sessions should work, my understanding is that only the UI has this limitation in place.

The use case is that external users'(for example users from LDAP) sessions cannot be listed in the XUI.

And those external user stores aren't configured as data stores? Are you using ignored or dynamic profile mode?

Yes, user stores are not configured as data stores. We are using the ignored profile.

In that case as a workaround you should be able to use the REST API directly.

Thanks for the workaround. We know about it and we are using it. But it is a temporary solution that has some inconveniences. We need the sessions listing to be working in the XUI, too. The question is if the bug will be fixed and if so which release the fix is planned for.

Ivailo Kolev  Please raise a support ticket here.

Currently, wildcards are not supported on that endpoint. An interim solution would be to allow the submission of known usernames, even if no match was found in the datastore.

Peter Major [X] does the REST api handle wildcards?

No, the backend only supports exact matches at the moment.

it works now, seems I was doing something wrong <- exact match only.