Hello Ahmed,

 

Thank you for the personal note asking how to overcome CSRF block by
OpenMeetings in your installation.  The Web link below points you to the
solution.  

 

To assist you in getting benefits from the experience of the members of the
community, you may want to subscribe to the user list of OpenMeetings.
Please feel free to ask questions in the forum, and many may volunteer to
share their solutions with you.

 

Possible solution:
https://openmeetings.markmail.org/message/mft3m5bdjeqxwicw?q=csrf 

 

How to subscribe to mailing list:
https://openmeetings.apache.org/mail-lists.html

 

Thank you.

 

Sincerely,

 

Hemant K. Sabat

 

Coscend Communications Solutions

www.Coscend.com <http://www.coscend.com/>  

------------------------------------------------------------------

Real-time, Interactive Video Collaboration, Tele-healthcare, Tele-education,
Telepresence Services, on the fly.

------------------------------------------------------------------

CONFIDENTIALITY NOTICE: See 'Confidentiality Notice Regarding E-mail
Messages from Coscend Communications Solutions' posted at:
<http://www.Coscend.com/Anchor/Common/Terms_and_Conditions.html>
http://www.Coscend.com/Anchor/Common/Terms_and_Conditions.html

 

 

 

From: Intellix Fact Consulting GmbH <[email protected]> 
Sent: Monday, May 7, 2018 12:59 PM
To: [email protected]
Subject: OpenMeetings over the Internet is not working
Importance: High

 

Dear Hemant,

I came across your profile over the Apache OpenMeetings page while searching
to fix a problem I have actually after installing Apache OpenMeetings to
ease the work of our remote teams over the internet.

The local installation on CentOS works at
http://localhost:5080/openmeetings.

But when I want to access it over SSL (https) I get :

 

Possible CSRF attack, 

request URL: http
<http://IP:ADDRESS/openmeetings/wicket/bookmarkable/org.apache.openmeetings.
web.pages.auth.SignInPage>
://IP:ADDRESS/openmeetings/wicket/bookmarkable/org.apache.openmeetings.web.p
ages.auth.SignInPage, 

Origin: https:// IP:ADDRESS, action: aborted with error 400 Origin does not
correspond to request

 

Any help to fix this would be very appreciated.

Cheers,

Ahmed 

 

 



---
This email has been checked for viruses by AVG.
http://www.avg.com

Reply via email to