# Candid UI could not be authenticated

**URL:** <https://forum.dfinity.org/t/candid-ui-could-not-be-authenticated/7538>\
**Category:** Developers\
**Created:** [September 25, 2021, 3:12am UTC](https://forum.dfinity.org/t/candid-ui-could-not-be-authenticated/7538 "2021-09-25T03:12:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jddllwqa](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/jddllwqa/32/16673_2.png) [@jddllwqa](https://forum.dfinity.org/u/jddllwqa)\
**Post date:** [September 25, 2021, 3:12am UTC](https://forum.dfinity.org/t/candid-ui-could-not-be-authenticated/7538/1 "2021-09-25T03:12:06Z")

</div>

In the process of using the candid UI, ‘could not be authenticated’ is often prompted. When we use the candid UI API, is there a more convenient way to authorize?

---

<div class="post-metadata">

**Author:** ![chenyan](https://avatars.discourse-cdn.com/v4/letter/c/35a633/32.png) [@chenyan](https://forum.dfinity.org/u/chenyan)\
**Post date:** [September 25, 2021, 4:43pm UTC](https://forum.dfinity.org/t/candid-ui-could-not-be-authenticated/7538/2 "2021-09-25T16:43:08Z")

</div>

Where does this error come from, in your dapp or from the IC? We haven’t implemented the integration with II yet. But if you want to get the same identity as your real application, it can be difficult. Because for II, it’s a different URL, thus you will get a different identity.

If you want to write some test based on identity, you can try [ic-repl](https://github.com/chenyan2002/ic-repl). It has an `identity` command, which can either generate random identities or import from an existing pem file.