https://www.domain.com:8443 is a different uri than
http://www.domain.com. If you don't change the redirect uri pattern in
the admin console for the app, then the server will not recognize the
https uri as valid.
On 10/1/2014 3:10 PM, Rodrigo Sasaki wrote:
Hello,
We tried to deploy our server in production today, protected with
Keycloak but we had some issues.
When we tried to access one of our resources, the redirect_uri was
altered to one we didn't have registered.
Our original uri was something like this: *http://www.domain.com/resource*
and it got changed to: *https://www.domain.com:8443/resource*
changing the protocol to https and adding the 8443 port, and that
specific uri isn't registered for us, so the server returned saying it
was an invalid redirect_uri
Is this a normal behavior? Should we have configured something else?
Thanks!
--
Rodrigo Sasaki
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com