# Forest UI Authentication - V7
**URL:** https://community.forestadmin.com/t/forest-ui-authentication-v7/2743
**Category:** Help me!
**Created:** [June 21, 2021, 1:15pm UTC](https://community.forestadmin.com/t/forest-ui-authentication-v7/2743 "2021-06-21T13:15:54Z")
**Posts on this page:** 11
**Page:** 1
### Author:  [@Guiguijo](https://community.forestadmin.com/u/Guiguijo)
#### Post date: [June 21, 2021, 1:15pm UTC](https://community.forestadmin.com/t/forest-ui-authentication-v7/2743/1 "2021-06-21T13:15:54Z")
Hi Forest,
I have implemented the V7 authentication config. When I load Forest UI, it sometimes authenticated me automatically and sometimes does not.
When it does not, I displays
But I have nothing in the log saying something is wrong.
Can you help me?
---
### Author:  [@Guiguijo](https://community.forestadmin.com/u/Guiguijo)
#### Post date: [June 21, 2021, 1:37pm UTC](https://community.forestadmin.com/t/forest-ui-authentication-v7/2743/2 "2021-06-21T13:37:07Z")
I can see this error in console:
---
### Author:  [@Guiguijo](https://community.forestadmin.com/u/Guiguijo)
#### Post date: [June 21, 2021, 1:43pm UTC](https://community.forestadmin.com/t/forest-ui-authentication-v7/2743/3 "2021-06-21T13:43:06Z")
@louis I regenerated the `FOREST_CLIENT_ID` and it worked again.
How often should we regenerate it? Why don’t we have a clearer message telling us to regenerate it?
Is’n it a problem in prod if we have to regenerate the environment variable regularly ?
---
### Author:  [@morganperre](https://community.forestadmin.com/u/morganperre)
#### Post date: [June 21, 2021, 1:52pm UTC](https://community.forestadmin.com/t/forest-ui-authentication-v7/2743/4 "2021-06-21T13:52:59Z")
Hello @Guiguijo,
You don’t need to configure `FOREST_CLIENT_ID` if you only have one instance running.
> **[Upgrade to v7](https://docs.forestadmin.com/documentation/how-tos/maintain/upgrade-notes-sql-mongodb/upgrade-to-v7#authentication)**
>
> The purpose of this note is to help developers to upgrade their liana from v6 to v7. Please read carefully and integrate the following breaking changes to ensure a smooth upgrade.
Kind regards,
Morgan
---
### Author:  [@Guiguijo](https://community.forestadmin.com/u/Guiguijo)
#### Post date: [June 21, 2021, 2:07pm UTC](https://community.forestadmin.com/t/forest-ui-authentication-v7/2743/5 "2021-06-21T14:07:33Z")
Hi @morganperre ,
I have several instance running in prod.
But anyway, it should work with a FOREST\_CLIENT\_ID even with only one instance in dev, shouldn’ it ?
---
### Author:  [@anon16419211](https://community.forestadmin.com/u/anon16419211)
#### Post date: [June 21, 2021, 2:34pm UTC](https://community.forestadmin.com/t/forest-ui-authentication-v7/2743/6 "2021-06-21T14:34:18Z")
Hello @Guiguijo,
I’m happy to hear that it works again on your production server. You are not supposed to change your FOREST\_CLIENT\_ID once set as an environment variable so it should work great. 🙂
If you want me to investigate a bit more on your issue can you try to see the logs from the route _/forest/authentication_ on your server side and share it to me?
Kind regards,
Louis
---
### Author:  [@Guiguijo](https://community.forestadmin.com/u/Guiguijo)
#### Post date: [June 21, 2021, 2:53pm UTC](https://community.forestadmin.com/t/forest-ui-authentication-v7/2743/7 "2021-06-21T14:53:33Z")
Hi @anon16419211 ,
I had the issue on my dev environment. I was just answering to @morganperre that I we have multiple instances on prod. That’s why we use FOREST\_CLIENT\_ID.
Anyway, the thing is that I had no log on server side. Forest was enable to reach any `/forest/authentication` root … but did not either raise a 404 or something. The logs were juste saying that Forest was available on port …
---
### Author:  [@anon16419211](https://community.forestadmin.com/u/anon16419211)
#### Post date: [June 21, 2021, 2:57pm UTC](https://community.forestadmin.com/t/forest-ui-authentication-v7/2743/8 "2021-06-21T14:57:29Z")
According to your console logs it looks like the issue came from your certificate. Did you modify anything on it? Can you connect to ForestAdmin as expected?
---
### Author:  [@Guiguijo](https://community.forestadmin.com/u/Guiguijo)
#### Post date: [June 21, 2021, 3:00pm UTC](https://community.forestadmin.com/t/forest-ui-authentication-v7/2743/9 "2021-06-21T15:00:04Z")
I did not change anything on the certificate. I was just working as usual.
After regenerating the FOREST\_CLIENT\_ID for my dev environment I could connect to ForestAdmin.
---
### Author:  [@anon16419211](https://community.forestadmin.com/u/anon16419211)
#### Post date: [June 22, 2021, 8:07am UTC](https://community.forestadmin.com/t/forest-ui-authentication-v7/2743/10 "2021-06-22T08:07:32Z")
After investigation I was able to identify the origin of the problem and it comes from the setup of a development environment under HTTPS which requires the acceptance of the certificate (hence the error in console). To solve this problem you just have to open the url and accept the conditions issued by chrome.
---
### Author:  [@Guiguijo](https://community.forestadmin.com/u/Guiguijo)
#### Post date: [June 22, 2021, 11:42am UTC](https://community.forestadmin.com/t/forest-ui-authentication-v7/2743/11 "2021-06-22T11:42:51Z")
Thanks @anon16419211 . I will do that