users lose some user rights daily

[arlem03]

I use Phraseanet 4.1.0 on a test environment where I have several users training on the system. For some reason, users lose functions when they sign out and sign back in, some times the "Edit" option disappear while they are signed in. The first obvious user right they lose is the "Edit" button. Even the Admin lose his user rights.

The only way to get the user rights back is to "Reset and apply template" for that user.

Any idea why this is occurring?

[nmaillat]

Hello, Do you use an external IDP for authenticate user on Phraseanet? regards

[arlem03]

Hello,

Thank you for asking.

We are not using an external IDP to authenticate user on Phraseanet. Know that our system is not connected to the internet. We do connect it to the internet when Support needs to remote in or when I need to update some package on the machines.

Best, Robert

From: "Nicolas Maillat" [email protected] To: "alchemy-fr/Phraseanet" [email protected] Cc: "arlem03" [email protected], "Author" [email protected] Sent: Friday, November 13, 2020 3:20:29 AM Subject: Re: [alchemy-fr/Phraseanet] users lose some user rights daily (#3584)

Hello, Do you use an external IDP for authenticate user on Phraseanet? regards

— You are receiving this because you authored the thread. Reply to this email directly, [ https://github.com/alchemy-fr/Phraseanet/issues/3584#issuecomment-726709504 | view it on GitHub ] , or [ https://github.com/notifications/unsubscribe-auth/AMOKUAKVEVV7C36MAMFI7Q3SPUI73ANCNFSM4PQ3PYBA | unsubscribe ] . [ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/alchemy-fr/Phraseanet/issues/3584#issuecomment-726709504", "url": "https://github.com/alchemy-fr/Phraseanet/issues/3584#issuecomment-726709504", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[gcon6543]

This was a memcached issue. We made some configuration changes and then eventually switched to redis and the issue went away... This issue is solved...