Welcome to the community!
There are a couple things going on here.
admin can be a global administrator and still not have analyze permissions on a project. So there’s that. But even if it does have permissions, those aren’t the credentials you’re using for analysis. You’re overriding those scanner-level values on the command line with
-Dsonar.login=d9485adba92198844074498dd8082c40808e0bab, which is the auth token of… some user who may or may not have analysis rights on the project.
Of course, you’ve already deleted that token, right? RIGHT?
So once you clean that token out of your command line config and out of the user profile SonarQube-side, you’ll set up a new token that you’ll keep private for a user that you know has analysis rights & configure that on the command line instead.
Alternately, you can clean
admin out of your Gradle properties (well, do this either way) and configure in the token value for a limited-permissions technical user that has Browse and Analyze on all (most?) projects and no other permissions. Then there’s no need to configure credentials on the command line.