[JIRA] (JENKINS-60728) Two active directory domains and same usernames
Title: Message Title Alexander Ukhanov created an issue Jenkins / JENKINS-60728 Two active directory domains and same usernames Issue Type: Bug Assignee: Félix Belzunce Arcos Components: active-directory-plugin Created: 2020-01-10 10:45 Environment: Jenkins 2.176.4, active-directory-plugin 2.16, two AD domains Priority: Major Reporter: Alexander Ukhanov In two AD-domains configuration (adom.organization.com, ddom.organization.com, binding as different users) when exist same user in both domains with different passwords, logon to Jenkins as user of ddom domain: DDOM\user, ddom\user or u...@ddom.organization.com initiate in log ... hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider retrieveUser WARNING: Credential exception trying to authenticate against adom.organization.com domain org.acegisecurity.BadCredentialsException: Either no such user '...' or incorrect password and after some logons, adom\user account from another domain ADOM being locked due to multiple bad password attempts. I think it happens because authentication go though all list of configured domains(tcpdump show connects to all domains). It is possible to initiate authentification of ddom\user only in home domain ddom.organization.com?
[JIRA] (JENKINS-47337) More than one PrimaryOwner
Title: Message Title Alexander Ukhanov commented on JENKINS-47337 Re: More than one PrimaryOwner This case can be solved by setting a secondary owner with the same as PrimaryOwner rights. But for more flexibility it would be nice to implement item-specific security on folders (https://issues.jenkins-ci.org/browse/JENKINS-47595) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185766.1507494955000.3203.1574159280162%40Atlassian.JIRA.
[JIRA] (JENKINS-54346) tee keeps file open
Title: Message Title
Alexander Ukhanov commented on JENKINS-54346
Re: tee keeps file open
In our installation(2.176.4) tee on windows nodes works good with workflow-job plugin <=2.25. After upgrade workflow-job plugin to 2.26+ version job with
node('windows')
{
tee {bat ... }
cleanWs()
}
drops with ERROR: Cannot delete workspace: Unable to delete '...'. Tried 3 times...
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195001.1540906753000.9829.1571329140678%40Atlassian.JIRA.
[JIRA] (JENKINS-57712) Allow entering search path for git blame
Title: Message Title Alexander Ukhanov assigned an issue to Ulli Hafner Jenkins / JENKINS-57712 Allow entering search path for git blame Change By: Alexander Ukhanov Assignee: Alexander Ukhanov Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199653.1559042804000.13595.1559046660408%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57712) Allow entering search path for git blame
Title: Message Title Alexander Ukhanov assigned an issue to Alexander Ukhanov Jenkins / JENKINS-57712 Allow entering search path for git blame Change By: Alexander Ukhanov Assignee: Ulli Hafner Alexander Ukhanov Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199653.1559042804000.13590.1559046600324%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54609) Approve assuming permission check for parameters change actions
Title: Message Title
Alexander Ukhanov created an issue
Jenkins / JENKINS-54609
Approve assuming permission check for parameters change actions
Issue Type:
Bug
Assignee:
Andrew Bayer
Attachments:
methods.png
Components:
script-security-plugin
Created:
2018-11-13 16:18
Environment:
jenkins 2.138.2 script-security 1.48
Priority:
Minor
Reporter:
Alexander Ukhanov
Our users have an example of code for change build parameters. It uses "dangerous" method org.jenkinsci.plugins.workflow.support.steps.build.RunWrapper getRawBuild. We firstly approve method as "Approve assuming permission check", but error "Scripts not permitted" still appears. Code works only if methods "Approved" (not "Approved assuming permission check"). It is normal behaviour? code example (need to create in job parameter newparam):
import hudson.model.Actionable
import hudson.model.ParametersAction
import hudson.model.ParameterValue
import hudson.model.StringParameterValue
def paramName = 'newparam'
def paramValue = 'newvalue'
setParam(paramName, paramValue)
echo ("NEW ${paramName} = ${newparam}")
//==
void setParam(String paramName, String paramValue) {
def build = currentBuild.getRawBuild()
List newParams = new ArrayList<>()
newParams.add(new StringParameterValue(paramName,
[JIRA] (JENKINS-49744) Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API
Title: Message Title Alexander Ukhanov commented on JENKINS-49744 Re: Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API Same problem with copying job from web-interface Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
