Hi there,
am getting cors issue not sure where i can add this.Am uisng version 655. pls advice.
‘https://iam12.example.com:8443/am655/json/realms/root/realms/testAdv/authenticate?authIndexType=service&authIndexValue=testAdvAuthTree’ from origin ‘https://localhost:8443’ has been blocked by CORS policy
It’s worth noting that some browsers do not accept localhost as a valid CORS origin. I know Chrome has had this issue for a number of years.
1 Like
Try reviewing ForgeRock Access Management 6.5 > Installation Guide
It may be a good idea to upgrade to 7.x as it makes it so much simplier.
Or if you are using Kubernetes you can configure it in your ingress.
Nicholas
1 Like
I fixed the cors issue. Now am getting the below error regarding certs. Am refering the following sample Step 3. Configure the embedded login sample app :: SDKs
Error:
POST https://iam1391.example.com:8444/am750/json/realms/root/realms/testAdv/authenticate?authIndexType=service&authIndexValue=testAdvAuthTree net::ERR_CERT_AUTHORITY_INVALID
Note: I know its cert issue but how could i fix it, pls try the sample at your end using your local instance of forgerock openam 7.5.0(pingAM) am not using cloud i have installed forgerock on my laptop.
You could install a CA issued certificate, or turn off certificate validation (in Postman settings, or providing --insecure option with curl)?
Regards
Patrick
1 Like
Hi @ysharat,
I’m happy to hear the Cors issue is resolved.
We’re working to enhance the community experience. If any of the provided answers helped you resolve your query, please mark it as ‘Solved’. To do this, select the Best Answer and click the checkbox
located at the bottom of the post/answer.
This will assist other community members in finding solutions to similar questions and will also acknowledge the valuable contributions of our community members.
If you need any assistance with how to mark a response as ‘Solved’, please let me know—I’m happy to help.
Thank you for your contribution!
Sheila