"need to enable js" response from A12 App

Client
1

I am building an A12 app ontop of the fullstack-template.

According to my webpack dev server, I should be able to access my A12 app in my local network under

<i> [webpack-dev-server] On Your Network (IPv4): http://<my IPv4 address>:8081/

However, when I try to access my app under http://<my IPv4 adress>:8081/ in my browser I, the corresponding request GET http://<my IPv4 address>:8081/ answers with You need to enable JavaScript to run this app.

I do not quite understand this reponse, because JS is in fact enabled in my browser.

Does someone have an idea what could be the reason for this issue?

2

so in fact can you see the app in your browser?

the GET response showing that information is then only the entry point HTML file…so all fine from the response itself.

3

Thank you for your reply - I do infact see nothing ( all white ) in the browser.

According to my console, the webpack dev server starts, then my A12 app starts the Uaa process but the wepack disconnects after the Uaa process trigger and is endlessly trying to reconnect ( without an additional error ).

[webpack-dev-server] Server started: Hot Module Replacement enabled, Live Reloading enabled, Progress disabled, Overlay enabled. index.js:485
[HMR] Waiting for update signal from WDS... log.js:39
UAA/Serverrequest Request 
Object { method: "GET", relativeUrl: "uaa-authentication/selfconfigure", customHeaders: (1) […] }
ConsoleStrategies.js:126
UAA/Serverrequest Response 
Response { type: "basic", url: "http://<my IPv4>:8081/api/uaa-authentication/selfconfigure", redirected: false, status: 200, ok: true, statusText: "OK", headers: Headers(7), body: ReadableStream, bodyUsed: true }
ConsoleStrategies.js:126
Start trigger UAA process for login. integration.ts:23:16
[webpack-dev-server] Disconnected! index.js:485
[webpack-dev-server] Trying to reconnect...
4

Hi @maximilian-deep-pool,

I don’t know what changes you have made to the Project Template / if you are using Keyloak as is the default in the Template or not.

But if you do, my first guess would be that the Keycloak container is not running.
You can start it via gradle keycloakComposeUp and then you should be able to access the admin console for Keycloak on localhost:8089 as well as see the login page on localhost:8081.

5

Hi @denise-narrow-token,
thank you for your help!
My changes only target the client and the application-dev.properties where I changed "localhost2 to my IPv4 address ( because I plan to access my app via a honeywell device ).

Unfortunately the keycloak can not be the root of my problem - it was/is running like you suggested. Plus, there is no connection to any new service in its log files, therefor I suspect the progblem arises when I try to access my app at 8081 - even before the UAA process would trigger the keycloak.

6

There could be multiple issues which are causing that this is not working as expected. I’ve tried to reproduce and I’m redirected to the keycloack - and keycloak correctly complains about Invalid parameter: redirect_uri - because my IP is not allowed in default keycloak configuration.

Start trigger UAA process for login.

At this point the redirect should start. If keycloak is up and visible for client you should be redirected to the login page, if not message that keycloak is not available should appear. Goes the redirection to correct URL?

Could you please exactly describe what you did. Version of Project Template, code changes, browser, OS, WSL, … everything :slight_smile:

But if your config in the application-dev.properties is correct (for all entries) then you should be redirect to http://:8089/<some_keycloak_stuff>.

// this is URL where you will be redirected, but all othere localhost should also changed
mgmtp.a12.uaa.authentication.client-selfconfiguration.oauth2.public-client.idp-base.url=http://<MY_IP>:8089
7

Thank you very much for your help!
After re-checking my application-dev.properties, I realized I forgot to change the domains in all my urls from localhost to my Ipv4, unfortunately I was too focused on using the appropriate ports to check for the domains too. I still do not know why using the wrong domain made A12 ask me to enable JS in my Browser, but it stoped as soon as I updated my domains :slight_smile: