June 7, 2016 at 10:44 pm #11064mariaculmanParticipant
Hi all, I am working with an OpenAM server running on amazon EC2 virtual machine. I have configured the Social Authentication Modules for Facebook and Google, and I am getting the same “Request not valid !”. The problem appears with http://54.xxx.xxx.xxx:8080/openam/oauth2c/OAuthProxy.jsp.
I am using a public IP and I am not using DNS CNAME.
I would appreciate greatly your guidance on this problem.June 8, 2016 at 10:22 pm #11086Scott HegerParticipant
Did you add your OAuthProxy.jsp URL into your Facebook and Google developer accounts as a valid URL? Also, are you saying that you have OpenAM configured to answer up via an IP address and not a FQDN? Or are you just specifying the OAuthProxy.jsp URL using the IP? In both cases you really should use an FQDN.June 16, 2016 at 9:56 pm #11337mariaculmanParticipant
Hi Scott. First of all, I configured the OpenAM server using the IP address of the amazon EC2 virtual machine (a public IP address). I do not have a domain (DNS) to use on my site so I decided to use the IP Address.
I did add the OAuthProxy.jsp URL into Facebook and Google apps:
For Facebook I used the exact URL that the social module on OpenAM showed me as: http://54.xxx.xxx.xxx:8080/openam/oauth2c/OAuthProxy.jsp (with the IP address)
But for Google I used the FQDN version of the URL as:
If the IP Address is the source of the error, how can I change the configuration on the OpenAM to work with the FQDN that Amazon AWS also provides?
Thanks a lot for your help.June 17, 2016 at 3:49 pm #11367Peter MajorModerator
Your issues are coming from cookies and cookie domains. You should have a look at the cookie domain setting (Configuration > System > Platform) and make sure that whatever is you have set is going to match the cookie domain of ec2-54-xxx-xxx-xxx.compute-1.amazonaws.com (which would be *exactly* ec2-54-xxx-xxx-xxx.compute-1.amazonaws.com, since anything less would be a TLD).
After that you just need to access the login interface on the ec2-54-xxx-xxx-xxx.compute-1.amazonaws.com domain and you should be good to go.
You must be logged in to reply to this topic.