# Does OIDC plugin require a public/internet facing installation of Jenkins?

**URL:** <https://community.jenkins.io/t/does-oidc-plugin-require-a-public-internet-facing-installation-of-jenkins/3123>\
**Category:** Using Jenkins\
**Created:** [July 21, 2022, 8:11pm UTC](https://community.jenkins.io/t/does-oidc-plugin-require-a-public-internet-facing-installation-of-jenkins/3123 "2022-07-21T20:11:08Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![foragerr](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/foragerr/32/1908_2.png) [@foragerr](https://community.jenkins.io/u/foragerr)\
**Post date:** [July 21, 2022, 8:11pm UTC](https://community.jenkins.io/t/does-oidc-plugin-require-a-public-internet-facing-installation-of-jenkins/3123/1 "2022-07-21T20:11:08Z")

</div>

I’m considering using the newly released [oidc-connect-provider](https://github.com/jenkinsci/oidc-provider-plugin) plugin to generate temporary AWS credentials instead of storing long lived AWS credentials in Jenkins’ credential store.

Is it required for the jenkins instance to be publicly accessible in order to use this plugin for AWS authentication?