Re: Jenkins SAML + nginx + ELB

It is already registred, so why I do not know what's going on W dniu piątek, 7 kwietnia 2017 19:09:19 UTC+2 użytkownik Ivan Fernandez Calvo napisał: > > You have a different issue, in your case your Sp, Jenkins, it is not > register on your IdP so it reject your request for authentication, the

Re: Jenkins SAML + nginx + ELB

The URL with an example https://github.com/kuisathaverat/docker-simplesamlphp/blob/master/etc/simplesamlphp/metadata/saml20-sp-remote.php -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails

Re: Jenkins SAML + nginx + ELB

You have a different issue, in your case your Sp, Jenkins, it is not register on your IdP so it reject your request for authentication, the method to register a new SP depends of your IdP, here you have an example of configuration with simplesamlphp, it identifies the SP with the response URL

Re: Jenkins SAML + nginx + ELB

Hi . As prakhar said I also have the similar problem, because durring log in I get message in respons that"we get incorrect request" here is some additional information which accompany above message: " Dodatkowe informacje techniczne: Correlation ID: 985a69d5-d30e-4e4f-8ed6-96788d7d6dda

Re: Jenkins SAML + nginx + ELB

Hey, I am getting similar type of error while integrating SAML-2 plugin + Azure Active Directory. Can you help me -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email

Re: Jenkins SAML + nginx + ELB

Are you setting the " X-Forwarded-Proto" header? This guide might be useful. You could also try and make the "Postback URL" be "http" since that is what the request will arrive as on the Jenkins server itself.

Jenkins SAML + nginx + ELB

I have my Jenkins server running with an nginx reverse proxy sitting in front of it. In front of that i have an AWS ELB that is terminating the SSL. So the problem is that Okta posts to https://myjenkins.mycompany.com, but on the jenkins side it sees http. so it fails. Any tips? WARNING: