# How to monitor urls with sso authentication

**URL:** <https://discuss.elastic.co/t/how-to-monitor-urls-with-sso-authentication/304133>\
**Category:** Beats\
**Tags:** heartbeat\
**Created:** [May 6, 2022, 1:30pm UTC](https://discuss.elastic.co/t/how-to-monitor-urls-with-sso-authentication/304133 "2022-05-06T13:30:24Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![aviral\_srivastava](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aviral_srivastava/32/98018_2.png) [@aviral\_srivastava](https://discuss.elastic.co/u/aviral_srivastava)\
**Post date:** [May 6, 2022, 1:30pm UTC](https://discuss.elastic.co/t/how-to-monitor-urls-with-sso-authentication/304133/1 "2022-05-06T13:30:24Z")

</div>

Hi,

My setup  
Elasticsearch 6.4.0, kibana 6.4.0 and heartbeat 6.4.0

heartbeat configuration:

```auto
heartbeat.monitors:
- type: http

  # List or urls to query
  urls:
    - https://appname.in.company.com:8443/appname-6.4
    - http://10.74.161.100:29200

  # Configure task schedule
  schedule: '@every 10s'
  mode: any

```

In Kibana, I can see I am getting

```auto
monitor.status as down and 
error.message as Get https://sso.company.com:443/opensso/oauth2/authorize?scope=openid&response_type=id_token&redirect_uri=https%3A%2F%2Fappname.in.company.com%3A8443%2FAppName%2FsunwCDSSORedirectURI&nonce=YIfGfOu8hXYY2tlNCwbclWadJMccuN3iKWflrP4Mq_txSHHCvjOmZA&client_id=Tomcat7AppMon&agent_realm=%2F&response_mode=form_post: x509: certificate is valid for appname.in.capgemini.com, not sso.company.com

```

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 6, 2022, 1:30pm UTC](https://discuss.elastic.co/t/how-to-monitor-urls-with-sso-authentication/304133/2 "2022-05-06T13:30:25Z")

</div>

Elasticsearch 6.4.0 is [EOL](https://www.elastic.co/support/eol) and no longer supported. Please upgrade ASAP.

(This is an automated response from your friendly Elastic bot. Please report this post if you have any suggestions or concerns :elasticheart: )

---

<div class="post-metadata">

**Author:** ![aviral\_srivastava](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aviral_srivastava/32/98018_2.png) [@aviral\_srivastava](https://discuss.elastic.co/u/aviral_srivastava)\
**Post date:** [May 6, 2022, 2:33pm UTC](https://discuss.elastic.co/t/how-to-monitor-urls-with-sso-authentication/304133/3 "2022-05-06T14:33:41Z")

</div>

Although, it is EOL, is their solution possible for the above issue?

---

<div class="post-metadata">

**Author:** ![aviral\_srivastava](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aviral_srivastava/32/98018_2.png) [@aviral\_srivastava](https://discuss.elastic.co/u/aviral_srivastava)\
**Post date:** [May 6, 2022, 3:26pm UTC](https://discuss.elastic.co/t/how-to-monitor-urls-with-sso-authentication/304133/4 "2022-05-06T15:26:01Z")

</div>

Looks like I have to use verification\_mode to be set to none. Now it's working

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [May 10, 2022, 12:56am UTC](https://discuss.elastic.co/t/how-to-monitor-urls-with-sso-authentication/304133/5 "2022-05-10T00:56:02Z")

</div>

Thanks for sharing the solution.

You should definitely upgrade though 😉

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 7, 2022, 2:56am UTC](https://discuss.elastic.co/t/how-to-monitor-urls-with-sso-authentication/304133/6 "2022-06-07T02:56:39Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.