# \#hash

**URL:** https://community.auth0.com/tag/hash/351.md

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

---

## [Access token is missing after redirect](https://community.auth0.com/t/access-token-is-missing-after-redirect/7976)

<div class="topic-metadata">

**Author:** [@tagir.sharipov](https://community.auth0.com/u/tagir.sharipov)\
**Replies:** 2\
**Last updated:** [December 5, 2017, 12:18am UTC](https://community.auth0.com/t/access-token-is-missing-after-redirect/7976 "2017-12-05T00:18:10Z")

</div>

I have implemented Auth0 Lock within React application according to the example https://github.com/auth0-samples/auth0-react-samples/tree/embedded-login/01-Embedded-Login My application works with Chrome, however when I…

---

## [Does the lock widget validate the at\_hash claim for us from the Browser?](https://community.auth0.com/t/does-the-lock-widget-validate-the-at-hash-claim-for-us-from-the-browser/8063)

<div class="topic-metadata">

**Author:** [@tal](https://community.auth0.com/u/tal)\
**Replies:** 0\
**Last updated:** [September 2, 2017, 1:37am UTC](https://community.auth0.com/t/does-the-lock-widget-validate-the-at-hash-claim-for-us-from-the-browser/8063 "2017-09-02T01:37:04Z")

</div>

I am setting up Identity-Provider initiated SAML Login for a Single Page App using the Auth0 Lock widget. I had some trouble because the tokens we’re getting have the “at\_hash” claim that our other tokens do not. The tok…

---

## [SAMLP and parseHash not working on some browsers](https://community.auth0.com/t/samlp-and-parsehash-not-working-on-some-browsers/6987)

<div class="topic-metadata">

**Author:** [@encirca](https://community.auth0.com/u/encirca)\
**Replies:** 2\
**Last updated:** [June 23, 2017, 7:59pm UTC](https://community.auth0.com/t/samlp-and-parsehash-not-working-on-some-browsers/6987 "2017-06-23T19:59:48Z")

</div>

From my header logs, I can see auth0 as the initiator of the redirect back after the SAML authentication success at the IDP. BUT, auth0 is doing a 301 redirect which can cause Safari and some other browsers to drop the h…

---

## [User\_id hash on Custom DB](https://community.auth0.com/t/user-id-hash-on-custom-db/6333)

<div class="topic-metadata">

**Author:** [@maziar](https://community.auth0.com/u/maziar)\
**Replies:** 5\
**Last updated:** [April 24, 2017, 3:02pm UTC](https://community.auth0.com/t/user-id-hash-on-custom-db/6333 "2017-04-24T15:02:52Z")

</div>

I am moving my users on-premises and was wondering which type of hashing auth0 is using when running on the local DB?