附加身份插件 - 如何配置？
我正在努力解决 Jenkins 中的重复用户和 不向未注册用户发送邮件... 问题。
我的詹金斯从Active Directory收集数据，一些用户有重复的条目，例如：
john.doe, [email protected] -> duplicated user which is detected by Jenkins
doej, [email protected] -> correct user which is used when logging in
詹金斯从git收集负责人后，工作变化以
结束 不向未注册用户发送邮件[电子邮件受保护]
我尝试为用户添加额外的身份doej 通过设置：
Identity: [email protected]
Realm: <empty>
但它不起作用。
我应该如何正确配置附加身份插件？
I'm struggling with duplicated users in my Jenkins and Not sending mail to unregistered user ... problem.
I installed the plugin as per this answer but cannot configure it properly by reading the plugin documentation.
My jenkins collects data from Active Directory and some users have duplicated entry, e.g.:
john.doe, [email protected] -> duplicated user which is detected by Jenkins
doej, [email protected] -> correct user which is used when logging in
Jenkins after collecting responsible people from git changes in job ends withNot sending mail to unregistered user [email protected]
I tried adding additional identity to user doej by setting:
Identity: [email protected]
Realm: <empty>
but it doesn't work.
How should I configure correctly the Additional Identities Plugin?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
似乎不可能在 Jenkins 中配置额外的身份插件来合并重复的用户，
因为 Jenkins 缺少一种确保用户唯一性（唯一）的方法，因为它们是从各种来源创建的：身份验证方法（在我的情况下是 LDAP）、代码提交（ Subversion、Mercurial、Git，...）。
根据 Jenkins 检索用户的方式（来自给定 SCM 上的提交或其身份验证），将为同一真实用户创建多个身份。
因此，某些功能无法完全或无法正常工作（登录、通知、用户构建、持续集成游戏等），并且用户配置非常痛苦，因为必须为每个真实用户进行多次配置。
所需的功能仍然是：
参考：< a href="https://issues.jenkins.io/browse/JENKINS-10258" rel="nofollow noreferrer">[JENKINS-10258] 允许用户唯一性 - Jenkins Jira
解决方案是 Jenkins 1.480，但这仍然位于 漏洞状态并具有错误 也是如此。
Jenkins 1.480 引入了一个扩展点，用于在按 ID 或全名在数据库中搜索用户时解析 jenkins 用户“规范”ID。该插件使用此扩展点让用户将外部身份配置为用户属性。
您可以联系Jenkins 社区 或支持团队了解状态或最终发布时间
Seems it's not possible to configure the additional identity plugin in Jenkins for merge the duplicate user
As Jenkins is missing a way to ensure users unicity(unique) since they are created from various sources: authentication method (LDAP in my case), code commits (Subversion, Mercurial, Git, ...).
Depending on the way the user is retrieved by Jenkins (from a commit on a given SCM or its authentication), multiple identities are created for the same real user.
As a consequence, some features are not fully or badly working (login, notifications, user's builds, continuous integration game, ...) and configuration of users is a pain as it must be done multiple times for each real user.
Still the required features are:
Reference: [JENKINS-10258] Allow users unicity - Jenkins Jira
Solution is Jenkins 1.480 but this is still in Vulnerabilities state and have bug as well.
Jenkins 1.480 introduces an extension point to resolve jenkins user "canonical" ID when searching for user in Database by id or full name. This plugin uses this extension point to let user configure external identities as user properties.
You can reach out to Jenkins community or Support team to know the status or when they will final release