Default admin/user accounts don't work on Monolithic app w/ H2 disk-based persistence about generator-jhipster HOT 6 CLOSED

Discovered that this is a token-relate issue. Repro case:

1. generate an app, start it, login as admin (and check the "remember me" box)
2. shutdown the app, delete it on disk
3. generate another app, start it, repeat the same login process
   Login fails due to leftover jhi-authenticationToken in browser local storage.
   Delete the token & try again...should be successful.

This happened to me because I ran the generator multiple times (testing different front-ends).
Might happen to others if they generate or use multiple jhipster apps on the same host/port.

This isn't strictly a defect, but has to do with token management.

from generator-jhipster.

Using h2 disk-based persistence worked fine for me when I tried it with 8.1.0 and Angular last week as part of my jhipster8-demo tutorial and screencast.

from generator-jhipster.

JHipster has completed the sample check
.yo-rc.json: valid
Entities JDL: blank
Application: successfully generated
Frontend check: success
Backend check: success
E2E check: success

This check uses jhipster info output from the issue description to generate the sample.
Bug report that does not contain this information will be marked as invalid.

from generator-jhipster.

I could not reproduce:

jhipster from-issue 24608
cd jhipster-samples/24608
./mvnw

user/user 👍
admin/admin 👍

from generator-jhipster.

Discovered that this is a token-relate issue. Repro case:

1. generate an app, start it, login as admin (and check the "remember me" box)
2. shutdown the app, delete it on disk
3. generate another app, start it, repeat the same login process
   Login fails due to leftover jhi-authenticationToken in browser local storage.
   Delete the token & try again...should be successful.

This happened to me because I ran the generator multiple times (testing different front-ends). Might happen to others if they generate or use multiple jhipster apps on the same host/port.

This isn't strictly a defect, but has to do with token management.

thanks @cfreyer. it works in private window

from generator-jhipster.

This is a bug. Probably happens with expired jwt token too.

from generator-jhipster.