[JIRA] [ldap-plugin] (JENKINS-29162) Jenkins internal user in order to be able to log-in under an authentication failure with LDAP AD, ...

2015-11-30 Thread fbelz...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Félix Belzunce Arcos commented on  JENKINS-29162 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins internal user in order to be able to log-in under an authentication failure with LDAP AD, ...  
 
 
 
 
 
 
 
 
 
 
I think the best solution here might be to support multiple security realms with failover. 
https://issues.jenkins-ci.org/browse/JENKINS-15063 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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.


[JIRA] [ldap-plugin] (JENKINS-29162) Jenkins internal user in order to be able to log-in under an authentication failure with LDAP AD, ...

2015-11-20 Thread te...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 James Nord commented on  JENKINS-29162 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins internal user in order to be able to log-in under an authentication failure with LDAP AD, ...  
 
 
 
 
 
 
 
 
 
 
You can configure the plugin with multiple LDAP servers so to failover to a backup if the primary goes down. If you only have one LDAP server then I would recommend getting another one - (Steven - your company is not short of LDAP servers). 
There are current non Jenkins workarounds like using a service like MS AD LDS  - solutions from other vendors apply also - but this does indeed add to the complexity of getting something like this working adds to support and are less than ideal. An API token should still work for script based access in order to reset some configuration - but there appears to be no API for Configure System or Configure Global Security that I could find that would allow you to change this. 
As for the 1 hour maximum (worth a different JIRA - but 3 days sounds a little excessive to me from a security perspective) - PRs welcome to this code  
Daniel Beck LDAP plugin should already cache this data (assuming you have already authenticated) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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.


[JIRA] [ldap-plugin] (JENKINS-29162) Jenkins internal user in order to be able to log-in under an authentication failure with LDAP AD, ...

2015-11-19 Thread s...@cisco.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steven Christenson commented on  JENKINS-29162 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins internal user in order to be able to log-in under an authentication failure with LDAP AD, ...  
 
 
 
 
 
 
 
 
 
 
Good points. We were burned by this issue just recently when our corporate LDAP server experienced issues. Our build and deploy pipeline became invisible since no log in is possible. The maximum cache currently allowed by the LDAP plugin is 1 hour. We need something like 3 days, or a way to have a local login in addition to the LDAP authenticated login. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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.


[JIRA] [ldap-plugin] (JENKINS-29162) Jenkins internal user in order to be able to log-in under an authentication failure with LDAP AD, ...

2015-09-02 Thread akostadi...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 akostadinov commented on  JENKINS-29162 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins internal user in order to be able to log-in under an authentication failure with LDAP AD, ...  
 
 
 
 
 
 
 
 
 
 
I'd advocate for support of non-LDAP users. Sometimes one needs a machine account to just access jenkins. Setting up an LDAP account might be an issue with IT. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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.


[JIRA] [ldap-plugin] (JENKINS-29162) Jenkins internal user in order to be able to log-in under an authentication failure with LDAP AD, ...

2015-07-01 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-29162 
 
 
 
  Jenkins internal user in order to be able to log-in under an authentication failure with LDAP AD, ...  
 
 
 
 
 
 
 
 
 
 
Not a core issue as authentication is completely done in plugins. 
Adding LDAP plugin component as the issue description specifically refers to that. 
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Component/s:
 
 ldap-plugin 
 
 
 

Component/s:
 
 core 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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.