Just a further note that following some further updating I can login via 
Facebook, Twitter, Google (using Mozilla Persona) and Microsoft accounts. 
 There is a test site at https://www.netdecisionmaking.com/w2ppsatest if 
anyone wants to take a look without setting up themselves.  I am not really 
planning to do much more with this unless there are issues or suggestions 
on what needs done next.

Regards
Donald

On Friday, June 10, 2016 at 9:49:05 PM UTC+1, Donald McClymont wrote:
>
> I have now forked and pruned w2p-social-auth at the following:  
> https://github.com/DonaldMcC/w2p-social-auth  basically only two changes 
> of substance:
>
> 1 It now uses appconfig to store the keys in so you will need to be on a 
> fairly recent web2py if you want to use this approach - alternatively just 
> put the keys directly into db.py but this obviously isn't a best practice 
> with github for sharing code.
> 2 I have removed the version of python social auth - I think 0.1.24 which 
> was included in previous file which means a lot less code - as far as I can 
> tell this was unmodified however it was not best if the plugin was 
> importing from their and internal imports within PSA were from the 
> installed version of that I had installed as a python package.
>
> Having done the above - I have successfully completed a basic login with 
> the revised plugin and PSA 0.2.19 which is the latest version use Mozilla 
> Persona as the provider - I will need to move it onto an actual site rather 
> than localhost to test a few other providers but that will be next week at 
> the earliest and I still have a very limited knowledge of Auth, PSA or the 
> actual code in the plug-in - so it would be good if people that do could 
> perhaps chip-in with suggestions on where this should be heading and how it 
> should be properly tested that would be appreciated.
>
> Donald
>
> On Monday, June 6, 2016 at 10:43:18 PM UTC+1, Donald McClymont wrote:
>>
>> Sounds good - possibly worth trying to contact someone on the psa team as 
>> well.  I think we need to decide whether an updated plug-in is the best way 
>> to go or whether this should be a core part of either PSA or web2py.  The 
>> plug-in may be the quickest way forward but it might well be better to go 
>> another route as it reduces the risk of being back in the same situation we 
>> have now where changes in PSA mean the plug-in doesn't work with latest 
>> versions.
>>
>> There was some previous dialogue on wihether python social auth or 
>> authomatic was the better approach and that did seem to come down in favour 
>> of PSA because authomatic was no longer being maintained. 
>>
>> Donald
>>
>> On Monday, June 6, 2016 at 12:30:29 AM UTC+1, Joe Barnhart wrote:
>>>
>>> Well I don't know about OAuth or auth-social, but I know web2py auth and 
>>> I know python pretty well.  I'll do a little reading on the whole concept 
>>> of social-auth and see if I can dig up more resources, like maybe the 
>>> author of w2p-social-auth.  If worse comes to worst, I can get some help 
>>> from Massimo.  I think a social auth plug-in that works really well would 
>>> be not only useful, but essential to web2py at this point.
>>>
>>> -- Joe
>>>
>>>
>>> On Sunday, June 5, 2016 at 3:08:23 PM UTC-7, Donald McClymont wrote:
>>>>
>>>> I would really like some progress on this - however I have extremely 
>>>> limited knowledge of both auth and Python Social Auth so was rather hoping 
>>>> someone that did might develop this in a better manner than I am likely to 
>>>> do..  I did briefly attempt to update what I have but quickly came to the 
>>>> conclusion it was not straightforward.  However I may have some time to 
>>>> look at in a bit more detail in the next few weeks.
>>>>
>>>> Regards
>>>> Donald
>>>>
>>>> On Sunday, June 5, 2016 at 1:20:38 AM UTC+1, Joe Barnhart wrote:
>>>>>
>>>>> Hi Donald --
>>>>>
>>>>> I find I need this too. The more recent version of social auth should 
>>>>> handle Google authentication in addition to Facebook and Twitter.  I need 
>>>>> these three in addition to web2py logon for my application. Have you seen 
>>>>> any progress on this front?  We may have to collaborate and do it 
>>>>> ourselves.
>>>>>
>>>>> -- Joe
>>>>>
>>>>> On Monday, March 7, 2016 at 3:26:34 PM UTC-8, Donald McClymont wrote:
>>>>>>
>>>>>> I am sharing  an example site http://www.netdecisionmaking.com that 
>>>>>> uses Python Social Auth for authentication, based on the following code 
>>>>>> and 
>>>>>>
>>>>>> https://github.com/omab/python-social-auth and the web2py 
>>>>>> integration developed at https://github.com/bnmnetp/w2p-social-auth 
>>>>>> <https://github.com/bnmnetp/w2p-social-auth>
>>>>>>
>>>>>> This works basically fine with the configured providers BUT it is 
>>>>>> using python social auth version 0.1.26 and I am keen to get it moved to 
>>>>>> the latest version.  Being keen but lazy I was looking to check if 
>>>>>> anyone 
>>>>>> has got a more up to date version that is currently working as it seems 
>>>>>> there are a few changes with the 0.2.x release that need to be worked 
>>>>>> through and w2p-social-auth that I am using has not been updated as far 
>>>>>> as 
>>>>>> I can find.
>>>>>>
>>>>>> The code for the site itself is at https://github.com/DonaldMcC/gdms 
>>>>>> and I am using the recently add config file to determine an overall 
>>>>>> authentication scheme for the site and pickup the keys etc which works 
>>>>>> fine.
>>>>>> Ideally I'd also like to also have the option to combine PSA and 
>>>>>> Web2py login methods however I haven't really looked into that yet.
>>>>>>
>>>>>> Regards
>>>>>> Donald
>>>>>>
>>>>>

-- 
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
--- 
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to