Hi Guys,

it is really annoying. 

Every time when i log in e.g to my router or raspberry the assistant starts and asks for authentication. What for? 

Even when i mark the ip address to be ignored for automatic saving or disabling the automatic saving for new entries, this dialogue comes up.

Am i missing something? How can i disable this?

 

thx

 

Edited May 25, 20205 yr by Ulmisch

Hi @Ulmisch,

Sorry for the inconvenience caused to you.

Please share the following details so that we can investigate where the problem could be.

• On which device (along with OS version) are you using Enpass?
• Which Enpass version are you using?
• If possible share the screenshot of the issue.

Hi Pratyush,

thx for your support.

Here are my informations:

Macbook Pro Mac Os 10.15.4 (same happens with 10.14.x)

Enpass Version 6.4.2

Procedure:

1. Browsing to the IP of my Fritzbox

2. type in my password (not stored in enpass) and confirm (enter) - screenshot 1

3. enpass assistant comes up - screenshot 2

 

 

Edited May 26, 20205 yr by Ulmisch

Hi @Ulmisch,

Thanks for sharing the details.

I have noted down this issue and notified the QA team to look into it.

Hey @Ulmisch

Thanks for the patience.

Unfortunately, our QA team is not able to reproduce it. Please share the URL/IP address with which you are facing the issue so that they can test the issue again.

Thanks for the understanding.

Hello Garima,

thx, for coming back.

It happens to the internal IPs 192.168.178.1 , 192.168.178.1 etc.

I have made a small clip. If you would like to see it, let me know how I can send it to you.

cu

Hi @Ulmisch

Thanks for writing back.

Please share the name of URL on which you are having this issue along with the clip you have made at support@enpass.io. Also, please link this forum post url so that we can easily identify.

Thanks for the co-operation.

Hello guys,

 

any news on this?

The annoyance is still there...

In addition: during homeoffice i used a windows computer as well. The effect ONLY takes place un der Mac Os.

cu

Edited July 23, 20205 yr by Ulmisch

Hey @Ulmisch

Thanks for the patience.

We would like to share that the issue has been reproduced by the QA team. Now our Dev team is looking into this issue to resolve and hopefully, a fix will be available in the future update.

Thanks for your co-operation.

Hi Garima,

i was happy to see the new update today.

Unfortunately the issue above seems not to be solved.

i am looking forward to a solution

cu

Edited September 14, 20205 yr by Ulmisch

@Ulmisch,

We appreciate your feedback on the latest version, however, the fix for this is planned for in the next version update.