# Local environments set up with self-signed certificates causing issues when used in OAuth 2 requests

**URL:** <https://community.postman.com/t/local-environments-set-up-with-self-signed-certificates-causing-issues-when-used-in-oauth-2-requests/209>\
**Category:** Help Hub\
**Tags:** authentication, slack, ssl, oauth\
**Created:** [November 13, 2017, 5:12pm UTC](https://community.postman.com/t/local-environments-set-up-with-self-signed-certificates-causing-issues-when-used-in-oauth-2-requests/209 "2017-11-13T17:12:10Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![musaid](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/musaid/32/79_2.png) [@musaid](https://community.postman.com/u/musaid)\
**Post date:** [November 13, 2017, 5:12pm UTC](https://community.postman.com/t/local-environments-set-up-with-self-signed-certificates-causing-issues-when-used-in-oauth-2-requests/209/1 "2017-11-13T17:12:10Z")

</div>

I have a team of developers working on a medium sized application. We have live, staging and development environments set up. Live and staging uses public domains with purchased certificates, and dev instances use self-signed certificates.

Our application consists of an API, App and an OAuth 2.0 server. While using Postman Chrome Plugin, we are able to perform OAuth 2.0 requests once we accept the certificate through the browser. Recently, after we noticed the deprecation messages of chrome plugin, we have switched to the native application.

However, we are unable to perform OAuth 2.0 token requests on dev environments now. The dialog shows a blank page. The Dev Tools and Console does not show any kind of responses. Switching to live environments works though.

Is there any way to find out what’s happening? We have tried importing the certificates to no avail. Also, disabling SSL verification in settings doesn’t seem to fix it either.

---

<div class="post-metadata">

**Author:** ![kamalaknn](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/kamalaknn/32/93_2.png) [@kamalaknn](https://community.postman.com/u/kamalaknn)\
**Post date:** [November 15, 2017, 3:03pm UTC](https://community.postman.com/t/local-environments-set-up-with-self-signed-certificates-causing-issues-when-used-in-oauth-2-requests/209/2 "2017-11-15T15:03:33Z")

</div>

Postman allows you to configure client certificates for your self-signed certificates. Could you try adding certificates for your internal URLs to Postman and retry this.

You can find more information about using client certificates here - [https://www.getpostman.com/docs/postman/sending\_api\_requests/certificates](https://www.getpostman.com/docs/postman/sending_api_requests/certificates)

If that doesn’t help, you should be able to find the token request and errors in the `Postman Console`(View -\> Show Postman Console).

---

<div class="post-metadata">

**Author:** ![musaid](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/musaid/32/79_2.png) [@musaid](https://community.postman.com/u/musaid)\
**Post date:** [December 10, 2017, 10:20am UTC](https://community.postman.com/t/local-environments-set-up-with-self-signed-certificates-causing-issues-when-used-in-oauth-2-requests/209/3 "2017-12-10T10:20:47Z")

</div>

Hi. I have tried adding the certificates as you suggested. It’s failing to work though. I have also tried checking it on v5.5.0. No luck.

Also, Authorize request of the OAuth 2.0 process is not captured by the Dev Console. The Access Token request does show up.