Prashant,
The Unexpected token '<' is almost certainly an indication that the (HTML) login page is being returned when the application is expecting to receive some JavaScript or JSON object.
You should probably figure out the request that is returning the "bad" response and then try to access it directly from your browser. This will let you see what you are getting back. I bet it's a login page (or some other HTTP error page).
If unauthenticated access is allowed but you still get login page, I would first check that both "unauthenticated" and "any-other" groups have Tr permissions in your ACL.
It's also worth checking the junction. If you have your Basic Authentication config set to "Supply" or "GSO" then this will require login for all access to the junction unless you change:
allow-unauth-ba-supply = no
to
allow-unauth-ba-supply = yes
in the WebSEAL configuration.
Jon.
------------------------------
Jon Harry
Consulting IT Security Specialist
IBM
------------------------------
Original Message:
Sent: Wed April 21, 2021 06:43 AM
From: Prashant Narkhede
Subject: ISAM - Facing an issue while accessing SPA
Hi Team,
I am facing the same issue when integrated an angular front-end application with ISAM.
Even after applying the unauthenticated ACL, it doesn't work for me.
Getting below error in console logs:
Uncaught SyntaxError: Unexpected token '<'
Are there any configuration changes that need to be done for this in the WebSEAL configuration file?
Regards,
Prashant
------------------------------
Prashant Narkhede
Original Message:
Sent: Tue December 01, 2020 02:58 AM
From: Mukesh Bhati
Subject: ISAM - Facing an issue while accessing SPA
Hi Jon,
Thanks for the help!
Now it is working after applying unauthenticated ACL to JavaScript resources.
------------------------------
Mukesh
Original Message:
Sent: Mon November 30, 2020 08:29 AM
From: Jon Harry
Subject: ISAM - Facing an issue while accessing SPA
Mukesh,
Seems very likely that the JavaScript resources you're trying to access are not set up for public (unauthenticated) access in the Reverse Proxy policy. So, the Reverse Proxy is returning its login page when you try to access them.
Jon.
------------------------------
Jon Harry
Consulting IT Security Specialist
IBM
Original Message:
Sent: Mon November 30, 2020 08:20 AM
From: Mukesh Bhati
Subject: ISAM - Facing an issue while accessing SPA
Hello All,
Facing an issue while accessing the SPA(created in Angular).
if SPA is accessed directly(via LocalHost) then there is no errors/warning in the browser's console.
but if the SPA is accessed via reverse proxy through the junction. then there are errors/warnings in the browser's console.
Can anyone help me?
------------------------------
Mukesh
------------------------------