-
Bug
-
Resolution: Cannot Reproduce
-
Minor
-
None
-
Jenkins 2.249.1 (on Windows)
active-directory 2.17
> still collection information <
as long as I use "Security Realm" -> "Jenkins own user database CLI works fine:
java -jar jenkins-cli.jar -s http://xxx:8081/ -auth user:pass who-am-i
Authenticated as: user
Authorities:
authenticated
... but if I change to AD
... it has worked fine with jenkins version: 2.235.3
java -jar jenkins-cli.jar -s http://xxx:8081/ -auth aduser@domain:pass who-am-i Authenticated as: aduser@domain Authorities: ... java -jar jenkins-cli.jar -s http://xxx:8081/ -auth aduser@domain:pass version 2.235.3
[JENKINS-63752] jenkins cli auth doesn't work any longer if AD authentication is activate
Attachment | New: screenshot-1.png [ 52644 ] |
Description |
Original:
as long as I use "Security Realm" -> "Jenkins own user database CLI works fine: {code:java} java -jar jenkins-cli.jar -s http://xxx:8081/ -auth user:pass who-am-i Authenticated as: user Authorities: authenticated {code} |
New:
as long as I use "Security Realm" -> "Jenkins own user database CLI works fine: {code:java} java -jar jenkins-cli.jar -s http://xxx:8081/ -auth user:pass who-am-i Authenticated as: user Authorities: authenticated {code} !screenshot-1.png|thumbnail! |
Description |
Original:
as long as I use "Security Realm" -> "Jenkins own user database CLI works fine: {code:java} java -jar jenkins-cli.jar -s http://xxx:8081/ -auth user:pass who-am-i Authenticated as: user Authorities: authenticated {code} !screenshot-1.png|thumbnail! |
New:
as long as I use "Security Realm" -> "Jenkins own user database CLI works fine: {code:java} java -jar jenkins-cli.jar -s http://xxx:8081/ -auth user:pass who-am-i Authenticated as: user Authorities: authenticated {code} !screenshot-1.png|thumbnail! ... but if I change to AD ... it has worked fine with jenkins version: 2.235.3 java -jar jenkins-cli.jar -s http://xxx:8081/ -auth aduser@domain:pass version 2.235.3 |
Description |
Original:
as long as I use "Security Realm" -> "Jenkins own user database CLI works fine: {code:java} java -jar jenkins-cli.jar -s http://xxx:8081/ -auth user:pass who-am-i Authenticated as: user Authorities: authenticated {code} !screenshot-1.png|thumbnail! ... but if I change to AD ... it has worked fine with jenkins version: 2.235.3 java -jar jenkins-cli.jar -s http://xxx:8081/ -auth aduser@domain:pass version 2.235.3 |
New:
as long as I use "Security Realm" -> "Jenkins own user database CLI works fine: {code:java} java -jar jenkins-cli.jar -s http://xxx:8081/ -auth user:pass who-am-i Authenticated as: user Authorities: authenticated {code} !screenshot-1.png|thumbnail! ... but if I change to AD ... it has worked fine with jenkins version: 2.235.3 {code:java} java -jar jenkins-cli.jar -s http://xxx:8081/ -auth aduser@domain:pass who-am-i Authenticated as: aduser@domain Authorities: ... java -jar jenkins-cli.jar -s http://xxx:8081/ -auth aduser@domain:pass version 2.235.3 {code} |
Description |
Original:
as long as I use "Security Realm" -> "Jenkins own user database CLI works fine: {code:java} java -jar jenkins-cli.jar -s http://xxx:8081/ -auth user:pass who-am-i Authenticated as: user Authorities: authenticated {code} !screenshot-1.png|thumbnail! ... but if I change to AD ... it has worked fine with jenkins version: 2.235.3 {code:java} java -jar jenkins-cli.jar -s http://xxx:8081/ -auth aduser@domain:pass who-am-i Authenticated as: aduser@domain Authorities: ... java -jar jenkins-cli.jar -s http://xxx:8081/ -auth aduser@domain:pass version 2.235.3 {code} |
New:
---> still collection information <--- as long as I use "Security Realm" -> "Jenkins own user database CLI works fine: {code:java} java -jar jenkins-cli.jar -s http://xxx:8081/ -auth user:pass who-am-i Authenticated as: user Authorities: authenticated {code} !screenshot-1.png|thumbnail! ... but if I change to AD ... it has worked fine with jenkins version: 2.235.3 {code:java} java -jar jenkins-cli.jar -s http://xxx:8081/ -auth aduser@domain:pass who-am-i Authenticated as: aduser@domain Authorities: ... java -jar jenkins-cli.jar -s http://xxx:8081/ -auth aduser@domain:pass version 2.235.3 {code} |
Description |
Original:
---> still collection information <--- as long as I use "Security Realm" -> "Jenkins own user database CLI works fine: {code:java} java -jar jenkins-cli.jar -s http://xxx:8081/ -auth user:pass who-am-i Authenticated as: user Authorities: authenticated {code} !screenshot-1.png|thumbnail! ... but if I change to AD ... it has worked fine with jenkins version: 2.235.3 {code:java} java -jar jenkins-cli.jar -s http://xxx:8081/ -auth aduser@domain:pass who-am-i Authenticated as: aduser@domain Authorities: ... java -jar jenkins-cli.jar -s http://xxx:8081/ -auth aduser@domain:pass version 2.235.3 {code} |
New:
> still collection information < as long as I use "Security Realm" -> "Jenkins own user database CLI works fine: {code:java} java -jar jenkins-cli.jar -s http://xxx:8081/ -auth user:pass who-am-i Authenticated as: user Authorities: authenticated {code} !screenshot-1.png|thumbnail! ... but if I change to AD ... it has worked fine with jenkins version: 2.235.3 {code:java} java -jar jenkins-cli.jar -s http://xxx:8081/ -auth aduser@domain:pass who-am-i Authenticated as: aduser@domain Authorities: ... java -jar jenkins-cli.jar -s http://xxx:8081/ -auth aduser@domain:pass version 2.235.3 {code} |
Attachment | New: screenshot-2.png [ 52645 ] |
Resolution | New: Cannot Reproduce [ 5 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
found my own mistake and solution
configuration for AD was not completed:
need cache, recursive group queries and remove irrelevant groups