Hi Everyone,
I have done with my background IDS configuration. Then try to integrate IDS with frond-end, for that I have set the isIDSEnabled is “true”. Once done with this changes, I have tried to run the UI at that time I have facing this issue in console once loading the UI.
1 Like
@Sam please help Geetha
Hello @GeethaNagarajan , Are you using the “Allow CORS: Access-Control-Allow-Origin” browser extension? Please confirm.
Hi @Sam, Yes Now using the CORS browser extension. That third-party Api access issue resolved. But still facing this issue. And I want to mention one note here - " In my backend I have changed the default port into 4500 instead of 8081. Because in my system, 8081 always engaged couldn’t use that port. So I changed, is this any chance to issues happened?
1 Like
Hello @GeethaNagarajan ,
Could you please go to the middleware section in your backend, click on CORS, and check if it is enabled? If it’s already enabled, there should be an option to edit. After clicking that, just add your localhost API there and try again.
Hope this helps!
1 Like
I added the localhost, which is working fine. Thanks
1 Like
Hi @Sam, still facing the same issue. while redirecting to Neutrinos login page, automatically it takes 8081 port.
See the below image login api url still localhost:8081->
1 Like
Hello @GeethaNagarajan , It looks like your frontend HTTP node is calling port 8081. Please try changing it to your backend port 4500 and let me know the result.
Hi @Sam, Please refer the screenshots here,
I have changed backend environment variable SSD_DEFAULT_PORT - 4500.
And I have changed the IDS login Redirect URI
from Front-end I have call this IDS login flow from the script node method, which is stick below,
When I call login Api I got this error on Browser:
Please check all the screenshot and let me know where I need to change the port number.
1 Like
Hello @GeethaNagarajan , on the client side, there’s an option in the sidebar called Environment. Inside, you’ll find a key–value pair for the SSD URL, which you can update from there. I hope this helps. Please let me know if the issue still persists.
1 Like
Yes, resolved once changed the SSD URL in frontend. Thanks @sam. Your suggestion is very useful to learn this platform.Thankyou.
1 Like