plain.oauth 0.7.0__tar.gz → 0.7.2__tar.gz

{plain_oauth-0.7.0 → plain_oauth-0.7.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: plain.oauth
-Version: 0.7.0
+Version: 0.7.2
 Summary: OAuth login and API access for Plain.
 Home-page: https://plainframework.com
 License: BSD-3-Clause
@@ -21,6 +21,8 @@ Description-Content-Type: text/markdown
 
 <!-- This file is compiled from plain-oauth/plain/oauth/README.md. Do not edit this file directly. -->
 
+<!-- This file is compiled from plain-oauth/plain/oauth/README.md. Do not edit this file directly. -->
+
 # plain.oauth
 
 Let users log in with OAuth providers.
@@ -160,36 +162,6 @@ That's pretty much it!
 
 ## Advanced usage
 
-### Email addresses should be unique
-
-When you're integrating with an OAuth provider,
-we think that the user's email address is the best "primary key" when linking to your `User` model in your app.
-Unfortunately in Django, by default an email address is not required to be unique!
-**We strongly recommend you require email addresses to be unique in your app.**
-
-[As suggested by the Django docs](https://docs.djangoproject.com/en/4.0/topics/auth/customizing/#using-a-custom-user-model-when-starting-a-project),
-one way to do this is to have your own `User` model:
-
-```python
-# In an app named "users", for example
-from plain.auth.models import BaseUser
-
-class User(BaseUser):
-    email = models.EmailField(unique=True)
-
-
-# In settings.py
-AUTH_USER_MODEL = 'users.User'
-```
-
-You'll also notice that there are no "email confirmation" or "email verification" flows in this library.
-This is also intentional.
-You can implement something like that yourself if you need to,
-but the easier solution in our opinion is to use an OAuth provider you *trust to have done that already*.
-If you look at our [provider examples](https://github.com/forgepackages/plain-oauth/tree/master/provider_examples) you'll notice how we often use provider APIs to get the email address which is "primary" and "verified" already.
-If they've already done that work,
-then we can just use that information.
-
 ### Handling OAuth errors
 
 The most common error you'll run into is if an existing user clicks a login button,
@@ -298,7 +270,7 @@ python manage.py check --database default
 
 ## FAQs
 
-### How is this different from [other Django OAuth libraries](https://djangopackages.org/grids/g/oauth/)?
+### How is this different from [Django OAuth libraries](https://djangopackages.org/grids/g/oauth/)?
 
 The short answer is that *it does less*.
 

{plain_oauth-0.7.0 → plain_oauth-0.7.2}/README.md

@@ -1,5 +1,7 @@
 <!-- This file is compiled from plain-oauth/plain/oauth/README.md. Do not edit this file directly. -->
 
+<!-- This file is compiled from plain-oauth/plain/oauth/README.md. Do not edit this file directly. -->
+
 # plain.oauth
 
 Let users log in with OAuth providers.
@@ -139,36 +141,6 @@ That's pretty much it!
 
 ## Advanced usage
 
-### Email addresses should be unique
-
-When you're integrating with an OAuth provider,
-we think that the user's email address is the best "primary key" when linking to your `User` model in your app.
-Unfortunately in Django, by default an email address is not required to be unique!
-**We strongly recommend you require email addresses to be unique in your app.**
-
-[As suggested by the Django docs](https://docs.djangoproject.com/en/4.0/topics/auth/customizing/#using-a-custom-user-model-when-starting-a-project),
-one way to do this is to have your own `User` model:
-
-```python
-# In an app named "users", for example
-from plain.auth.models import BaseUser
-
-class User(BaseUser):
-    email = models.EmailField(unique=True)
-
-
-# In settings.py
-AUTH_USER_MODEL = 'users.User'
-```
-
-You'll also notice that there are no "email confirmation" or "email verification" flows in this library.
-This is also intentional.
-You can implement something like that yourself if you need to,
-but the easier solution in our opinion is to use an OAuth provider you *trust to have done that already*.
-If you look at our [provider examples](https://github.com/forgepackages/plain-oauth/tree/master/provider_examples) you'll notice how we often use provider APIs to get the email address which is "primary" and "verified" already.
-If they've already done that work,
-then we can just use that information.
-
 ### Handling OAuth errors
 
 The most common error you'll run into is if an existing user clicks a login button,
@@ -277,7 +249,7 @@ python manage.py check --database default
 
 ## FAQs
 
-### How is this different from [other Django OAuth libraries](https://djangopackages.org/grids/g/oauth/)?
+### How is this different from [Django OAuth libraries](https://djangopackages.org/grids/g/oauth/)?
 
 The short answer is that *it does less*.
 

{plain_oauth-0.7.0 → plain_oauth-0.7.2}/plain/oauth/README.md

@@ -1,3 +1,5 @@
+<!-- This file is compiled from plain-oauth/plain/oauth/README.md. Do not edit this file directly. -->
+
 # plain.oauth
 
 Let users log in with OAuth providers.
@@ -137,36 +139,6 @@ That's pretty much it!
 
 ## Advanced usage
 
-### Email addresses should be unique
-
-When you're integrating with an OAuth provider,
-we think that the user's email address is the best "primary key" when linking to your `User` model in your app.
-Unfortunately in Django, by default an email address is not required to be unique!
-**We strongly recommend you require email addresses to be unique in your app.**
-
-[As suggested by the Django docs](https://docs.djangoproject.com/en/4.0/topics/auth/customizing/#using-a-custom-user-model-when-starting-a-project),
-one way to do this is to have your own `User` model:
-
-```python
-# In an app named "users", for example
-from plain.auth.models import BaseUser
-
-class User(BaseUser):
-    email = models.EmailField(unique=True)
-
-
-# In settings.py
-AUTH_USER_MODEL = 'users.User'
-```
-
-You'll also notice that there are no "email confirmation" or "email verification" flows in this library.
-This is also intentional.
-You can implement something like that yourself if you need to,
-but the easier solution in our opinion is to use an OAuth provider you *trust to have done that already*.
-If you look at our [provider examples](https://github.com/forgepackages/plain-oauth/tree/master/provider_examples) you'll notice how we often use provider APIs to get the email address which is "primary" and "verified" already.
-If they've already done that work,
-then we can just use that information.
-
 ### Handling OAuth errors
 
 The most common error you'll run into is if an existing user clicks a login button,
@@ -275,7 +247,7 @@ python manage.py check --database default
 
 ## FAQs
 
-### How is this different from [other Django OAuth libraries](https://djangopackages.org/grids/g/oauth/)?
+### How is this different from [Django OAuth libraries](https://djangopackages.org/grids/g/oauth/)?
 
 The short answer is that *it does less*.
 

plain_oauth-0.7.2/plain/oauth/default_settings.py

@@ -0,0 +1 @@
+OAUTH_LOGIN_PROVIDERS: dict

{plain_oauth-0.7.0 → plain_oauth-0.7.2}/pyproject.toml

@@ -1,6 +1,6 @@
 [tool.poetry]
 name = "plain.oauth"
-version = "0.7.0"
+version = "0.7.2"
 description = "OAuth login and API access for Plain."
 authors = ["Dave Gaeddert <dave.gaeddert@dropseed.dev>"]
 license = "BSD-3-Clause"