-
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
Client certificate required no matter which option is selected #597
Comments
Can you supply a screenshot / explain more? I was able to configure from scratch with a client secret no problem |
Hi, @fcorluka-burai |
Hi @timja and @fcorluka-burai I'm also having similar issue when trying to verify configuration after required fields are populated. Please see screenshot below or attached as well. Hope details provided will help troubleshoot faster. Here are the all the version details: Azure SDK API Plugin: 174 |
Can you open your browser console when you click Verify Configuration and send the JSON? Replacing values with ****s of any user supplied info From reading the code I don't see how this could happen and I've tested on an existing and from a clean setup again (I also tested this case yesterday) What browser are you using? (I've tested Safari and Chrome) |
@timja Just FYI on side, I've deployed brand new AWS EC2 Rocky Linux with latest Jenkins Version 2.452.2 with MS EntraID plugin along with all dependencies which doesn't seems to have this issue which I find it odd. Possibly issue is related to older versions. Notice in the second screenshot, even though I've selected Client Secret, somehow the credentialType comes as Certificate. |
Ah right. I fixed this in Jenkins 2.443 jenkinsci/jenkins#8832 are you able to upgrade please? |
Jenkins and plugins versions report
Environment
azure-ad:504.vc4785930e17a_
Jenkins: 2.414.3
What Operating System are you using (both controller, and any agents involved in the problem)?
Java: 11.0.20 - Red Hat, Inc. (OpenJDK 64-Bit Server VM)
Reproduction steps
I wanted to create an integration between Microsoft SSO and Jenkins. I was trying yesterday before the latest upgrade and there wasn't even an option for client certificate. Now when I want to use client_id and client_secret, it is still requiring me to enter client_certificate. Since it's a radio button, I would believe that only one of these two option is required and not both.
Expected Results
Be able to add client_secret without adding client_certificate
Actual Results
client_certificate required no matter the option selected
Anything else?
No response
Are you interested in contributing a fix?
No response
The text was updated successfully, but these errors were encountered: