| Name | gdmty-drf-firebase-auth JSON |
| Version |
24.1.1
JSON |
| download |
| home_page | |
| Summary | Custom Django Rest Framework authentication backend than can be used with many firebase projects at same time, and storing as local users. |
| upload_time | 2024-01-28 01:44:12 |
| maintainer | |
| docs_url | None |
| author | |
| requires_python | >=3.10 |
| license | Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright 2023 Gobierno de Monterrey Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. |
| keywords |
django
firebase
jwt
authentication
|
| VCS |
 |
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
# gdmty-drf-firebase-auth
Firebase backend to receive a user idToken and authenticate via Django REST Framework
'authentication.BaseAuthentication'. Optionally, a new local user can be created in the process.
## Requirements
* Python 3
* Django 4
* Django Rest Framework 3
* Firebase Admin SDK
## Installation
```bash
$ pip install gdmty-drf-firebase-auth
```
## Configuration
Add the application to your project's `INSTALLED_APPS` in `settings.py`.
```python
INSTALLED_APPS = [
# ...
'gdmty_drf_firebase_auth',
...
]
```
### General settings
In your project's `settings.py`, add this to the `REST_FRAMEWORK` configuration. Note that if you want to retain access to the browsable API for locally created users, then you will probably want to keep `rest_framework.authentication.SessionAuthentication` too.
```python
REST_FRAMEWORK = {
# ...
'DEFAULT_AUTHENTICATION_CLASSES': [
# ...
'rest_framework.authentication.SessionAuthentication', # Optional, better to remove for production
'rest_framework.authentication.BasicAuthentication', # Optional, better to remove for production
'gdmty_drf_firebase_auth.authentication.FirebaseAuthentication',
]
}
```
The `gdmty_drf_firebase_auth` application comes with the following settings as default, which can be overridden in your project's `settings.py` file. For convenience, most of these can be conveniently set form environment variables also. Make sure to nest them within `DEFAULT_FIREBASE_AUTH_CONFIG` as below:
```python
DEFAULT_FIREBASE_AUTH_CONFIG = {
# allow creation of new local user in db
'FIREBASE_CREATE_LOCAL_USER': True,
# attempt to split firebase user.display_name and set local user, first_name and last_name
'FIREBASE_ATTEMPT_CREATE_WITH_DISPLAY_NAME': False,
# Authorization header prefix, commonly JWT or Bearer (e.g. Bearer <token>)
'FIREBASE_AUTH_HEADER_PREFIX': 'Bearer',
# verify that JWT has not been revoked
'FIREBASE_CHECK_JWT_REVOKED': True,
# require that firebase user.email_verified is True
'FIREBASE_AUTH_EMAIL_VERIFICATION': False,
# function should accept firebase_admin.auth.UserRecord as argument and return str
'FIREBASE_USERNAME_MAPPING_FUNC': map_firebase_uid_to_username
}
```
You can get away with leaving all the settings as default
### Firebase per-project settings
It is required to have GCP service accounts, the original project only supports one; the original code has been modified to allow more than one service account, To configure the service accounts, the following configuration must be added in the `settings.py` file of your project, where each element corresponds to a project and in turn, its respective service account.
`BASE_DIR` is the root of your project, where manage.py lives. We assume that you have a folder called `sa` in the root of your project, and that you have placed your service account keyfiles there. You can change this to wherever you like.
```python
import os
BASE_DIR = os.path.dirname(os.path.dirname(os.path.dirname(os.path.abspath(__file__))))
...
FIREBASE_AUTH_SA_KEYFILES = {
'project-1': os.path.join(BASE_DIR, 'sa', 'project-1-keyfile.json'),
'project-2': os.path.join(BASE_DIR, 'sa', 'project-2-keyfile.json')
}
FIREBASE_AUTH_PROJECTS = {
{'PROJECT_ID': 'project-1', 'SERVICE_ACCOUNT_KEY': FIREBASE_AUTH_SA_KEYFILES['project-1']},
{'PROJECT_ID': 'project-2', 'SERVICE_ACCOUNT_KEY': FIREBASE_AUTH_SA_KEYFILES['project-2']},
}
```
Now that you have configured the application, run the migrations so that the Firebase data can be stored.
```bash
(venv) $ ./manage.py migrate gdmty_drf_firebase_auth
```
All you need to do now is have your client code handle the Firebase popup/redirect authentication flow, retrieve the idToken from the currentUser (Firebase explains this flow well in their docs: `https://firebase.google.com/docs/auth/admin/verify-id-tokens`), and then use the idToken for the user in an `Authorization` header in requests to your API.
```javascript
Bearer <token>
```
Now, all is ready!
## Contributing
* Please raise an issue/feature and name your branch 'feature-n' or 'issue-n', where 'n' is the issue number.
* If you test this code with a Python version not listed above and all is well, please fork and update the README to include the Python version you used :)
## Additional Notes
* This project is a fork of drf-firebase-auth, which seems no longer maintained. The original project only supports one service account, the original code has been modified to allow more than one service account.
* The initial proposal of this project had the option of use Firebase Auth with email and password, but this option was removed to keep the project clean and simple, and focused on the use of Firebase Auth with idToken for Django REST Framework.
* If you are looking for a project that supports Firebase Auth with email and password, you can use our side project: `gdmty-django-firebase-auth-email-password` at https://github.com/SIGAMty/gdmty-django-firebase-auth-email-password
* I almost always setup Django with a custom user class inheriting from AbstractUser, where I switch the USERNAME_FIELD to be 'email'. This backend is set up to assign a username still anyway, but if there are any issues, please raise them and/or make a pull request to help the community!
Raw data
{
"_id": null,
"home_page": "",
"name": "gdmty-drf-firebase-auth",
"maintainer": "",
"docs_url": null,
"requires_python": ">=3.10",
"maintainer_email": "",
"keywords": "django,firebase,jwt,authentication",
"author": "",
"author_email": "Gobierno de Monterrey <cesar.benjamin@monterrey.gob.mx>",
"download_url": "https://files.pythonhosted.org/packages/b3/54/fc52c9cec28da77c91dd600055ebb6d40b975249b32793d671e7f0b25b18/gdmty-drf-firebase-auth-24.1.1.tar.gz",
"platform": null,
"description": "# gdmty-drf-firebase-auth\n\nFirebase backend to receive a user idToken and authenticate via Django REST Framework \n'authentication.BaseAuthentication'. Optionally, a new local user can be created in the process.\n\n## Requirements\n\n* Python 3\n* Django 4\n* Django Rest Framework 3 \n* Firebase Admin SDK\n\n## Installation\n\n```bash\n$ pip install gdmty-drf-firebase-auth\n```\n\n## Configuration\n\nAdd the application to your project's `INSTALLED_APPS` in `settings.py`.\n\n```python\nINSTALLED_APPS = [\n # ...\n 'gdmty_drf_firebase_auth',\n ...\n]\n```\n\n### General settings\n\nIn your project's `settings.py`, add this to the `REST_FRAMEWORK` configuration. Note that if you want to retain access to the browsable API for locally created users, then you will probably want to keep `rest_framework.authentication.SessionAuthentication` too.\n\n```python\nREST_FRAMEWORK = {\n # ...\n 'DEFAULT_AUTHENTICATION_CLASSES': [\n # ...\n 'rest_framework.authentication.SessionAuthentication', # Optional, better to remove for production\n 'rest_framework.authentication.BasicAuthentication', # Optional, better to remove for production\n 'gdmty_drf_firebase_auth.authentication.FirebaseAuthentication',\n ]\n}\n```\n\nThe `gdmty_drf_firebase_auth` application comes with the following settings as default, which can be overridden in your project's `settings.py` file. For convenience, most of these can be conveniently set form environment variables also. Make sure to nest them within `DEFAULT_FIREBASE_AUTH_CONFIG` as below:\n\n```python\nDEFAULT_FIREBASE_AUTH_CONFIG = {\n # allow creation of new local user in db\n 'FIREBASE_CREATE_LOCAL_USER': True,\n # attempt to split firebase user.display_name and set local user, first_name and last_name\n 'FIREBASE_ATTEMPT_CREATE_WITH_DISPLAY_NAME': False,\n # Authorization header prefix, commonly JWT or Bearer (e.g. Bearer <token>)\n 'FIREBASE_AUTH_HEADER_PREFIX': 'Bearer',\n # verify that JWT has not been revoked\n 'FIREBASE_CHECK_JWT_REVOKED': True,\n # require that firebase user.email_verified is True\n 'FIREBASE_AUTH_EMAIL_VERIFICATION': False,\n # function should accept firebase_admin.auth.UserRecord as argument and return str\n 'FIREBASE_USERNAME_MAPPING_FUNC': map_firebase_uid_to_username\n}\n```\n\nYou can get away with leaving all the settings as default\n\n### Firebase per-project settings\n\nIt is required to have GCP service accounts, the original project only supports one; the original code has been modified to allow more than one service account, To configure the service accounts, the following configuration must be added in the `settings.py` file of your project, where each element corresponds to a project and in turn, its respective service account.\n\n`BASE_DIR` is the root of your project, where manage.py lives. We assume that you have a folder called `sa` in the root of your project, and that you have placed your service account keyfiles there. You can change this to wherever you like.\n\n```python\nimport os\nBASE_DIR = os.path.dirname(os.path.dirname(os.path.dirname(os.path.abspath(__file__))))\n\n...\n\nFIREBASE_AUTH_SA_KEYFILES = {\n 'project-1': os.path.join(BASE_DIR, 'sa', 'project-1-keyfile.json'),\n 'project-2': os.path.join(BASE_DIR, 'sa', 'project-2-keyfile.json')\n}\n\nFIREBASE_AUTH_PROJECTS = {\n {'PROJECT_ID': 'project-1', 'SERVICE_ACCOUNT_KEY': FIREBASE_AUTH_SA_KEYFILES['project-1']},\n {'PROJECT_ID': 'project-2', 'SERVICE_ACCOUNT_KEY': FIREBASE_AUTH_SA_KEYFILES['project-2']},\n}\n```\n\nNow that you have configured the application, run the migrations so that the Firebase data can be stored.\n\n```bash\n(venv) $ ./manage.py migrate gdmty_drf_firebase_auth\n```\n\nAll you need to do now is have your client code handle the Firebase popup/redirect authentication flow, retrieve the idToken from the currentUser (Firebase explains this flow well in their docs: `https://firebase.google.com/docs/auth/admin/verify-id-tokens`), and then use the idToken for the user in an `Authorization` header in requests to your API.\n\n```javascript\nBearer <token>\n```\n\nNow, all is ready!\n\n## Contributing\n\n* Please raise an issue/feature and name your branch 'feature-n' or 'issue-n', where 'n' is the issue number.\n* If you test this code with a Python version not listed above and all is well, please fork and update the README to include the Python version you used :)\n\n## Additional Notes\n\n* This project is a fork of drf-firebase-auth, which seems no longer maintained. The original project only supports one service account, the original code has been modified to allow more than one service account.\n* The initial proposal of this project had the option of use Firebase Auth with email and password, but this option was removed to keep the project clean and simple, and focused on the use of Firebase Auth with idToken for Django REST Framework.\n* If you are looking for a project that supports Firebase Auth with email and password, you can use our side project: `gdmty-django-firebase-auth-email-password` at https://github.com/SIGAMty/gdmty-django-firebase-auth-email-password\n* I almost always setup Django with a custom user class inheriting from AbstractUser, where I switch the USERNAME_FIELD to be 'email'. This backend is set up to assign a username still anyway, but if there are any issues, please raise them and/or make a pull request to help the community!\n",
"bugtrack_url": null,
"license": "Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. \"License\" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. \"Licensor\" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. \"Legal Entity\" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, \"control\" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. \"You\" (or \"Your\") shall mean an individual or Legal Entity exercising permissions granted by this License. \"Source\" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. \"Object\" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. \"Work\" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). \"Derivative Works\" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. \"Contribution\" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, \"submitted\" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as \"Not a Contribution.\" \"Contributor\" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a \"NOTICE\" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets \"[]\" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same \"printed page\" as the copyright notice for easier identification within third-party archives. Copyright 2023 Gobierno de Monterrey Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. ",
"summary": "Custom Django Rest Framework authentication backend than can be used with many firebase projects at same time, and storing as local users.",
"version": "24.1.1",
"project_urls": {
"Bug Tracker": "https://github.com/SIGAMty/gdmty-drf-firebase-auth/issues",
"Homepage": "https://github.com/SIGAMty/gdmty-drf-firebase-auth"
},
"split_keywords": [
"django",
"firebase",
"jwt",
"authentication"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "664315478ca3dd49db0f7080270699558fb2e5d8daa104ae8097e714bcd42bad",
"md5": "81207c01c766c7512d8600efd43bb393",
"sha256": "293f031f0ebca6df69cb6cd1c0500872a40ca045eaee0c66639b35ea16231154"
},
"downloads": -1,
"filename": "gdmty_drf_firebase_auth-24.1.1-py3-none-any.whl",
"has_sig": false,
"md5_digest": "81207c01c766c7512d8600efd43bb393",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.10",
"size": 22463,
"upload_time": "2024-01-28T01:44:10",
"upload_time_iso_8601": "2024-01-28T01:44:10.442383Z",
"url": "https://files.pythonhosted.org/packages/66/43/15478ca3dd49db0f7080270699558fb2e5d8daa104ae8097e714bcd42bad/gdmty_drf_firebase_auth-24.1.1-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "b354fc52c9cec28da77c91dd600055ebb6d40b975249b32793d671e7f0b25b18",
"md5": "63298a27efa005d25d580724ffd949e4",
"sha256": "9c25f2c27d63509014def2d42b46cb2c3a746ce8f5fcde2ec8781ca7031b3502"
},
"downloads": -1,
"filename": "gdmty-drf-firebase-auth-24.1.1.tar.gz",
"has_sig": false,
"md5_digest": "63298a27efa005d25d580724ffd949e4",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.10",
"size": 19438,
"upload_time": "2024-01-28T01:44:12",
"upload_time_iso_8601": "2024-01-28T01:44:12.251445Z",
"url": "https://files.pythonhosted.org/packages/b3/54/fc52c9cec28da77c91dd600055ebb6d40b975249b32793d671e7f0b25b18/gdmty-drf-firebase-auth-24.1.1.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-01-28 01:44:12",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "SIGAMty",
"github_project": "gdmty-drf-firebase-auth",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"requirements": [],
"lcname": "gdmty-drf-firebase-auth"
}
