Download as PDF, PPTX
![Decomposing the PingAccess / Jenkins scenario
Confidential — do not distribute Copyright © 2014 Ping Identity Corp.All rights reserved. 6
• HTTP Reverse Proxy deployment, therefore Jenkins is a Site.
• Jenkins is comprised of several URLs that will be defined as Resources within
an Application.
• Jenkins is equipped with a plugin[1] for authentication using HTTP Headers
via a Reverse Proxy. This is accomplished using Identity Mappings.
[1]https://wiki.jenkins-ci.org/display/JENKINS/Reverse+Proxy+Auth+Plugin](https://image.slidesharecdn.com/oyvalv0ztbypjdmrnuwn-signature-e77353a5531666e85fadeb0e4ebdcbd4e7522e2f525b50388570d11bd88051f3-poli-140804132128-phpapp02/85/CIS14-PingAccess-in-Action-6-320.jpg)
Uploaded byCloudIDSummit
CIS14: PingAccess in Action
The document outlines a deployment scenario for integrating PingAccess with Jenkins as an identity-enabled HTTP reverse proxy to enhance authentication processes for users. It details the components involved, including identity mappings, a virtual host, and the use of PingFederate. The objective is to streamline user sign-ins and improve security in the Jenkins environment.
More Related Content
CIS14: PingAccess in Action
- 2. PINGACCESS IN ACTION PeterMotykowski Sr. Product Engineering Manager Copyright © 2014 Ping Identity Corp.All rights reserved. 2
- 3. Web & APIAccess Management Confidential — do not distribute Copyright © 2014 Ping Identity Corp.All rights reserved. 3
- 4. The 5Ws Confidential —do not distribute • Who – users of Jenkins, the continuous integration server • What – Jenkins and PingAccess, PingFederate • When – live! • Where – localhost, because WiFi is unreliable • Why – because we’re tired of signing-in, again • How – using PingAccess as an identity-enabled HTTP reverse proxy Copyright © 2014 Ping Identity Corp.All rights reserved. 4
- 5. Overview of PingAccess/ Jenkins Deployment Confidential — do not distribute Copyright © 2014 Ping Identity Corp.All rights reserved. 5
- 6. Decomposing the PingAccess/ Jenkins scenario Confidential — do not distribute Copyright © 2014 Ping Identity Corp.All rights reserved. 6 • HTTP Reverse Proxy deployment, therefore Jenkins is a Site. • Jenkins is comprised of several URLs that will be defined as Resources within an Application. • Jenkins is equipped with a plugin[1] for authentication using HTTP Headers via a Reverse Proxy. This is accomplished using Identity Mappings. [1]https://wiki.jenkins-ci.org/display/JENKINS/Reverse+Proxy+Auth+Plugin
- 7. Jenkins Confidential — donot distribute Copyright © 2014 Ping Identity Corp.All rights reserved. 7
- 8. The PingAccess /Jenkins Deployment recipe Confidential — do not distribute Copyright © 2014 Ping Identity Corp.All rights reserved. 8 A Virtual Host, an Identity Mapping, an OpenID Connect Provider (PingFederate), a Web Session, a Site, and an Application. And a dash of PKI and Policy.
- 9. Securing the PingAccess/ Jenkins Deployment Confidential — do not distribute Copyright © 2014 Ping Identity Corp.All rights reserved. 9