-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Several operations throw java.lang.IllegalArgumentException: A granted authority textual representation is required #253
Comments
Getting the same error when trying to queue a build:
|
What attributes do your users have @kevinkrol ? |
@timja The user I'm testing with has full administrator permissions. For the group, the SSO provides these permissions:
|
This is likely the Azure AD attributes causing an issue not the Jenkins permissions |
I am also facing the same issue, which seemed to be working with Azure AD Plugin: 191 version but giving this issue with 234 version. https://updates.jenkins-ci.org/download/plugins/azure-ad/ With this plugin version 234, for some users when trying to do REST call with the API token generated in jenkins, it is throwing HTTP response code 500, however if we try to login to jenkins console with that same user, we are being able to. |
I have the same issue.
Jenkins versions jenkins-2.346.2-1.1.noarch and jenkins-2.332.3-1.1.noarch (on Linux), and Azure-AD versions 241.vb_e5cd7c35b_2e and 234.vb_ece34ecd5ff. I suspect the change from If you're just looking for a quick way to roll back, here it is
|
It won't be that change as that change is a no-op for object id, line 124 adds the group as an authority and the
|
I'm going to close this as there's no steps to reproduce provided. Please provide a method of reproducing from scratch including in AAD. I have tried reproducing this and have not been able to. |
This is no longer an issue with |
Jenkins and plugins versions report
What Operating System are you using (both controller, and any agents involved in the problem)?
Windows Server 2012
Reproduction steps
I have seen this issue when accessing /asynchPeople and when accessing /computer/agent_id/api/json (Both with full admin perms)
Expected Results
The API response.
Actual Results
For /asynchPeople a few users are loaded but then it gets stuck.
Anything else?
No response
The text was updated successfully, but these errors were encountered: