web2py 1.81.4 is OUT

[mdipierro]

Changelog compared to 1.80.*

- Usual bug-fixes.

- curd forms work with .load now.

- New welcome app with better look, superfish menu and jQuery 1.4.2

- Increased security. It means you can place {{=....}} inside tag
attributes without worry about injections. Thanks Craig Youkins

- Last but not least we have incorporate code from Mr Freeze RPX slice
into web2py core.

You now find these lines in welcome/models/db.py

# from gluon.contrib.login_methods.rpx_account import
RPXAccount
#
auth.settings.actions_disabled=['register','change_password','request_reset_password']
# auth.settings.login_form = RPXAccount(request,
api_key='...',domain='...', url = '...')

uncomment them, register (for free) with janrain.com (rpxow.com) and
fill-in api_key, domain, and url (your complete exposed login url).

You can add those 3 lines to any existing app.

They allow your users to login in your web2py app with any of the
janrain supported backends: facebook google, myscape, twitter,
linkedin, etc. They require no hacking, and no additional modules.

It should work on GAE too but I did not try. If you try please report
here.

Please report any issue with 1.81.4

Massimo

[mdipierro]

Let me add that RPX is integrated with the web2py Role Based Access
Control. You can still create groups and permissions locally using the
web2py appadmin. Works on GAE.

[Chris S]

Is there a better explanation of how RPX integrates with the native
web2py now that it's included in trunk? I would very much like to
read a little more on how this works.

For example:
*Can you use RPX in combination with local user registration?
*If we use a custom auth_user table can we use this or do we need to
update anything?
*How are 'unique' values in auth_user handled since usually username
or e-mail must be unique.
*What happens when the same user logs in from several different RPX
accounts? IE does a single users Facebook+Google+etc log-ins all
count as separate users?
*Can users still be put in a 'pending' state for admin approval? Or
how do you limit who can access the application if you want to allow
RPX accounts but only for certain users?


I'm sure there's more information on this somewhere I'm just not clear
where.

[mdipierro]

On Jul 18, 2:21 pm, Chris S <sanders.ch...@gmail.com> wrote:
> Is there a better explanation of how RPX integrates with the native
> web2py now that it's included in trunk?  I would very much like to
> read a little more on how this works.
>
> For example:
> *Can you use RPX in combination with local user registration?

Mr Freeze plugins allows it. The version I included in trunk does not.
This is because there may be workflow issues that I have not worked
out. You can create two actions (one that uses PRX and one that uses
normal login).

> *If we use a custom auth_user table can we use this or do we need to
> update anything?

You can use a custom table. It just need a new hidden string field
'registration_id'

> *How are 'unique' values in auth_user handled since usually username
> or e-mail must be unique.

If you login with facebook or yahoo or other RPX, it is not guaranteed
that there is a username or an email but there is a guaranteed
registration_id. That is why in the way I implement it, you have to
choose whether you use normal registration/login (using username or
password) or RPX (using registration_id as unique id).

> *What happens when the same user logs in from several different RPX
> accounts?  IE does a single users Facebook+Google+etc log-ins all
> count as separate users?

I do not know. I think they are treated as separate users. If you find
out more let us know.

> *Can users still be put in a 'pending' state for admin approval?  Or
> how do you limit who can access the application if you want to allow
> RPX accounts but only for certain users?

This works as before.