Invalid parameter: redirect_uri
See original GitHub issueHi, I have cloned the master branch and trying to setup APIMan and DevPortal on VM by exposing the port of VM and accessing it from the browser of my local machine using VM-IP:PORT.
I have run the following commands so far:
mvn clean install -Pinstall-all-wildfly -DskipTests
cd tools/server-all/target/wildfly-dev-server
./bin/standalone.sh
After pointing to browser with VM-IP:Port/apimanui I am getting the following output:
Any leads will be helpful. Thanks
Issue Analytics
- State:
- Created 2 years ago
- Comments:28 (14 by maintainers)
Top Results From Across the Web
keycloak Invalid parameter: redirect_uri - Stack Overflow
Another way to solve the issue, is to view the Keycloak server console output, locate the line stating the request was refused, copy...
Read more >Invalid parameter: redirect_uri despite * Valid Redirect URIs ...
Area admin/cli Describe the bug Keycloak has been running fine until I believe a new update happened in the last few weeks.
Read more >Invalid redirect uri for "Valid Redirect URIs with https://*"
I am getting “Invalid redirect uri” on the keycloak sso page. What is the full URL of that 'keycloak sso page'. There is...
Read more >Invalid Parameter: redirect_uri - OpenID Authentication
Hello,. I have recently installed my new tableau Server and I'm trying to get external authentication working using the OpenID protocal and Keycloak...
Read more >RH-SSO shows "Invalid parameter: redirect_uri", despite the ...
Issue · RH-SSO shows Invalid parameter: redirect_uri , despite the Redirect URI has been already configured for the corresponding client.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Make sure you have a running elasticsearch somewhere, for example:
docker run -d --name elasticsearch -p 9200:9200 -e "discovery.type=single-node" elasticsearch:7.13.2
And use the following properties file: apiman.properties.txt
Please let us know if this is working 😃
Hi @volkflo , yes it is working properly now. Thank you so much @volkflo and @msavy for taking out time to resolve the issue. So what I have figured out the issue was related to both properties and elasticSearch.