Hey good people,
I got Bitcoin payment working up, but it will not let me use https, only http. Not sure what to do with that.
But Stripe is not working. It has been set up as a payment option for the course, yet not showing like Bitcoin does.
Any suggestions?
Sorry if this is the wrong category.
Also my Oauth crashed, not sure what is going on there.
Thanks for your help.
David
What? Three issues in one posting! Are they related? Could they be related?
Well ... about the Oath2 now busted ... do you mean upgrading it?
Please see:
https://moodle.org/plugins/auth_googleoauth2
where author says:
starting
from Moodle 3.3, Oauth2 should be implemented in Moodle core. It will
require you to upgrade to Moodle 3.3 and switch to the Oauth2 core
authentication (and probably do some migration), but it is a great news
as authentication is a really sensible matter and having Oauth2 plugins
in core will guarantee their maintenance. So starting from Moodle 3.3 I
highly recommend to use the new Oauth2 core plugins ((https://docs.moodle.org/dev/Better_Office_Integrations_3.3#Core_API_for_managing_Authorized_OAuth_Applications) )
. Missing core providers will likely be implemented by someone and
published in the Moodle.org plugin repository. There will probably be a
new Oauth2 category in the Moodle plugin repository. Wait and see...
I will try to mantain this plugin until Moodle 3.1 (LTS) runs out of security upport (13 May 2019).
There's also a warning on Facebook there.Ok, you are running 3.2.2 ... sooooooo ?????
Just comments about other ...
This payment thang you mentioned not allowing https but http only. Take it your site has a valid issued from CA certificate? And what of the issue reported earlier ... 'false positive'? Now am not saying your site is malicious ... so don't react!!! Wonder if this payment thing isn't also getting 'false positive' on being able to communicate via https.
Have you contacted them?
'spirit of sharing', Ken
Hi Ken,
They all seemed to happen at the same time, so I do not know if they are related.
I do not understand your post. I think I need to remove the upgrade of Oauth2 as I went to upgrade it, but just get this message now.
I now have a problem with coinbase (Bitcoin), I get this message:
You will be redirected to http://www.trainingjapan.org/enrol/bitcoin/oauth.php after the authorization.
Warning: this application is not using a secure connection to receive your access credentials. An attacker could compromise your account if you authorize this application. If you're the developer, use an HTTPS redirect URI to avoid this warning.
Any ideas on this? If it is the wrong forum, where should I ask?
Thanks
D
