# \#security-issue

**URL:** https://community.auth0.com/tag/security-issue/1100.md

[Latest](https://community.auth0.com/latest.md) · [Categories](https://community.auth0.com/categories.md) · [Tags](https://community.auth0.com/tags.md)

---

## [Is the security breach at Okta impacting Auth0 or its customers in any way?](https://community.auth0.com/t/is-the-security-breach-at-okta-impacting-auth0-or-its-customers-in-any-way/82128)

<div class="topic-metadata">

**Author:** [@c.kapplmueller](https://community.auth0.com/u/c.kapplmueller)\
**Replies:** 2\
**Last updated:** [April 21, 2022, 12:11pm UTC](https://community.auth0.com/t/is-the-security-breach-at-okta-impacting-auth0-or-its-customers-in-any-way/82128 "2022-04-21T12:11:29Z")

</div>

As Auth0 is part of Okta: Is there even the slightest chance, that the security breach at Okta (Lapsus$ found a spreadsheet of accounts as they breached Okta, documents show • TechCrunch) was impacting or impacts Auth0 o…

---

## [React Rails Auto0 - Heroku Deployment issue (call back route)](https://community.auth0.com/t/react-rails-auto0-heroku-deployment-issue-call-back-route/9633)

<div class="topic-metadata">

**Author:** [@babylee2002](https://community.auth0.com/u/babylee2002)\
**Replies:** 1\
**Last updated:** [December 17, 2018, 4:53pm UTC](https://community.auth0.com/t/react-rails-auto0-heroku-deployment-issue-call-back-route/9633 "2018-12-17T16:53:08Z")

</div>

So, everything works perfect with my local host but I have an issue to go past /callback route. See the app below with the issue https://o-lingo.herokuapp.com The authentication with Auth0 for this app is set up with …

---

## [Insecure HTTP headers](https://community.auth0.com/t/insecure-http-headers/8926)

<div class="topic-metadata">

**Author:** [@carsten.mueller.lemb](https://community.auth0.com/u/carsten.mueller.lemb)\
**Replies:** 1\
**Last updated:** [December 11, 2017, 8:07pm UTC](https://community.auth0.com/t/insecure-http-headers/8926 "2017-12-11T20:07:15Z")

</div>

During our security review we figured out that. Response header is exposing technology used: server:nginx Strict transport layer security and other headers are missing: Strict-Transport-Security:max-age=15552000; inc…