Jfrog CLI does not detect group permissions when using SSO

[ArieLevs]

Describe the bug

when Artifactory is configured with SSO, and using the UI all works 100%, users are detected, and SSO groups are associated to artifactory group and being granted with relevant permissions

but when using CLI, it seems that Artifactory does not "understands" an API key is linked to a group (sine its not an internal user?)
only after manually going to the group and adding an SSO user there, CLI starts working fine

Current behavior

CLI does not detect permissions, all kind of

404
401
No results found

returnes

Reproduction steps

configure SSO, make sure your SSO user is part of a group with admin privileges (to test)
go to a repo to list/download artifacts via the UI all is OK,
do the same using CLI commands (for helm search helm-test for example) and nothing works (in helm's case a No results found returned)

Expected behavior

user permissions for CLI access should be identical to UI access

JFrog CLI version

2.46.2

Operating system type and version

jfrog-cli-v2 container

JFrog Artifactory version

7.63.11

JFrog Xray version

No response

[shuvadipc]

Jfrog CLI actually uses a REST API provided by JFrog Access to perform the login. That API returns an access token that jfrog-cli stores locally. Any additional logic is performed server side by JFrog Access. So not a jfrog cli bug.