If an authorized user opens a concrete entity(in entities) to the navbar and refreshes the page, the user will become unauthorized.

Overview of the issue

The user receives the status not authorized after the page is refresh on a particular entity. I found a similar question (https://github.com/jhipster/generator-jhipster/issues/6190) and saw the commit “decisive” problem. The commit was 20 days ago and I have the latest version of the jipper. I can safely say that the last fix did not solve the problem.

Motivation for or Use Case

Reproduce the error

Authorize user, open concrete entyti in navbar, refresh page.

Related issues

Suggest a Fix

JHipster Version(s)

4.8.2

JHipster configuration, a .yo-rc.json file generated in the root folder

{ “generator-jhipster”: { “promptValues”: { “packageName”: “ru.javablog.blog”, “nativeLanguage”: “en” }, “jhipsterVersion”: “4.8.2”, “baseName”: “javablog”, “packageName”: “ru.javablog.blog”, “packageFolder”: “ru/javablog/blog”, “serverPort”: “8080”, “authenticationType”: “jwt”, “hibernateCache”: “ehcache”, “clusteredHttpSession”: false, “websocket”: false, “databaseType”: “sql”, “devDatabaseType”: “postgresql”, “prodDatabaseType”: “postgresql”, “searchEngine”: false, “messageBroker”: false, “serviceDiscoveryType”: false, “buildTool”: “gradle”, “enableSocialSignIn”: false, “enableSwaggerCodegen”: false, “jwtSecretKey”: “eefdb2a631a1a1c21b563d59fa1ccb8908d4769e”, “clientFramework”: “angularX”, “useSass”: true, “clientPackageManager”: “yarn”, “applicationType”: “monolith”, “testFrameworks”: [], “jhiPrefix”: “jhi”, “enableTranslation”: true, “nativeLanguage”: “en”, “languages”: [ “en”, “ru” ] } }

Entity configuration(s) entityName.json files generated in the .jhipster directory

Browsers and Operating System

OS: Archlinux

openjdk version “1.8.0_144” OpenJDK Runtime Environment (build 1.8.0_144-b01) OpenJDK 64-Bit Server VM (build 25.144-b01, mixed mode)

git version 2.14.1

node: v8.5.0

npm: 5.3.0

yeoman: 1.8.5

yarn: 1.0.2

Docker version 17.07.0-ce, build 87847530f7

docker-compose version 1.16.1, build unknown

• Checking this box is mandatory (this is just to show you read everything)

[gzsombor]

Yes, it’s the same issue, I could reproduce it. The referred problem is not fixed, as I see.

I think, I have a solution for it.

[ghost]

@jdubois , my situation was described to you by @pelmegov . It’s similar problem.