{"id":18,"date":"2019-09-17T11:00:00","date_gmt":"2019-09-17T05:30:00","guid":{"rendered":"https:\/\/opstree.com\/blog\/\/?p=18"},"modified":"2019-09-19T11:21:58","modified_gmt":"2019-09-19T05:51:58","slug":"still-using-jenkins-own-user-database-for-authentication-in-privately-hosted-jenkins-why-not-update-to-gmail-authentication","status":"publish","type":"post","link":"https:\/\/opstree.com\/blog\/2019\/09\/17\/still-using-jenkins-own-user-database-for-authentication-in-privately-hosted-jenkins-why-not-update-to-gmail-authentication\/","title":{"rendered":"Achieve SSO in Privately Hosted Jenkins"},"content":{"rendered":"
\n

Introduction<\/span><\/h1>\n
Providing OAuth 2.0 user authentication directly or using Google+ Sign-in reduces your CI overhead. It also provides a trusted and secure login system that’s familiar to users, consistent across devices, and removes the burden of users having to remember another username and password.\u00a0One of the hurdles in implementing a Gmail authentication is that\u00a0Google developer console and your\u00a0 Jenkins server should be in the same network or in simple terms they can talk to each other.<\/span><\/span><\/div>\n

Resources Used<\/h2>\n<\/div>\n
\n