[JIRA] (JENKINS-58809) CLI and API call do not work with SAML Realm

[gdu...@gmail.com (JIRA)]

Title: Message Title

Guillaume Dupin commented on JENKINS-58809   Re: CLI and API call do not work with SAML Realm Ivan Fernandez Calvo FYI (and for people that might encounter the same issue and land on this page), the problem came from 2 points : the configuration of the nginx reverse-proxy in front of jenkins (this page helped me : https://wiki.jenkins.io/display/JENKINS/Jenkins+behind+an+NGinX+reverse+proxy) server {    listen 8080;    server_tokens off;   location / {         proxy_pass http://jenkins:8080;         proxy_set_header Host $host;         proxy_set_header X-Forwarded-Proto https;         proxy_set_header X-Forwarded-Host $host;         proxy_http_version 1.1;         proxy_request_buffering off;   } } the "Name ID Format" configured in my SAML IdP provider (Keycloak) that was set to "email" and not to "username" : this attribute is the one that will be referenced in Jenkins as the user login and you must use it in your API authentication (mine was set to "email" so I had to use the email as the user id) Thank you again for your time 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.201120.1565004290000.1631.1565688300130%40Atlassian.JIRA.